EskanderPlus Studio

ESKANDERPLUS SOCIAL

Privacy policy

Effective date: 17 November 2026

This policy covers EskanderPlus Social, the studio's internal social-media workspace at social.eskanderplus.com. It covers connected social-account data, not the studio's separate client or architectural-project records.

Who operates the workspace

EskanderPlus Studio operates the workspace for authorized members of its team to manage the studio's own accounts. It is not a public service for unrelated businesses. Contact the studio about privacy at media@eskanderplus.com.

What information we process

Depending on the platform and permissions granted, we process account names, profile images, email addresses, account and channel identifiers, authorization tokens, studio-uploaded media, captions, schedules, publication identifiers and status, and performance information such as views and engagement. Operational records may include timestamps, errors and technical request information. Login sessions use cookies or similar storage.

Social accounts are connected through the platform's authorization process. The workspace does not ask users to supply their social-platform passwords.

Why we use information

We use information to identify connected studio accounts, prepare and schedule approved content, publish to selected destinations, check publication status, review performance and resolve technical problems. Our AI-assisted publishing workflow requires team approval of the content and destination before publication.

We do not sell connected-account data, supply it to advertisers for targeting, or use it for data brokerage or surveillance. The studio does not use data obtained through platform APIs to train general-purpose AI models.

Storage and providers

Postiz and its operational database run on the studio's Synology server. Connection credentials are held in private storage on authorized workstations and on the server where needed. They are excluded from shared installation packages.

Cloudflare provides HTTPS delivery and may process connection information for delivery and security. Social platforms receive the content and requests needed to perform authorized actions and return account data. Their privacy policies govern their own processing.

Authorized team members may use an OpenAI assistant to prepare content, operate the workflow and interpret selected information. Information included in those interactions is processed under the applicable assistant account settings and terms. Processing is therefore not limited to the studio's server. Tokens and client secrets must not be intentionally included in ordinary prompts or public documents.

We share information with providers as needed for these functions or where disclosure is legally required. We restrict access to authorized team members and service operations.

Google and YouTube

The YouTube integration uses YouTube API Services. Google's processing is described in the Google Privacy Policy. By using the YouTube integration, authorized users agree to the YouTube Terms of Service. Use and transfer of Google API data must follow the Google API Services User Data Policy, including Limited Use requirements where applicable.

You can revoke Google access through Google account permissions. Revocation does not remove videos already published on YouTube. To request removal of data held by the studio, use the deletion instructions below.

Other platforms

Facebook and Instagram integrations support authorized studio-account publishing and performance review. X, LinkedIn, Pinterest and other integrations are used only when connected and permitted by the platform. Planned Pinterest functions are studio Pin creation, scheduling and reporting. Inclusion in this policy does not mean a platform has approved the application or that all functions are available.

How long we keep information

We keep authorization tokens only while needed for an authorized connection. Studio-uploaded content and publishing records are retained while needed for active publishing, troubleshooting and the studio's content archive; authorized administrators review ongoing need and remove information no longer required. Operational logs rotate according to storage limits rather than a guaranteed number of days.

Platform-specific rules override our general retention practices. For YouTube, stored API data subject to a 30-day refresh or deletion requirement must be refreshed or deleted within that period; retained authorized analytics must be checked against continuing authorization. On a valid deletion request, or revocation communicated to the studio, we will delete associated platform data as soon as possible and within seven calendar days. This process is handled by authorized administrators, not an assurance that disconnecting a channel automatically erases every copy.

Deletion covers affected application records, credentials, caches, operational copies and backups under our control. Administrators must prevent deleted data from being restored. Any legally required retention is limited to the relevant data and purpose and will be explained to the requester where permitted.

Your choices and deletion requests

To request access, correction or deletion, contact media@eskanderplus.com. We may ask for proportionate evidence of authority over the account. Do not send passwords, access tokens or login codes. See our data deletion instructions for the request process.

Removing stored workspace data and deleting a public social post are separate actions. A request to delete workspace data does not by itself authorize deletion of published posts from the platform.

Security and updates

The workspace requires an authorized team account and uses HTTPS for its public connection. No system can guarantee absolute security. We update this policy when our processing changes and seek further authorization when a new purpose or permission requires it. The effective date appears at the top of this page.