Privacy Policy

Last updated: 10 August 2026

Elele Social Studio is the internal content workspace of the small team behind Elele, a free real-chat app. We use it to plan, review and publish our own social posts. It is not a product we sell and it is not open to the public: only invited members of our team can sign in, and accounts are created by an administrator.

This policy covers the workspace at studio.elele.app and every social platform it connects to. The Elele chat app has its own policy at elele.me/privacy.

What we store

Team accounts: Email address, display name and role. There is no public sign-up, and no tracking or advertising identifiers anywhere in the panel.
Content our team creates: Campaign briefs, captions, hashtags, schedules and the images and videos we upload. Held in Google Cloud (Firestore and Cloud Storage) in the europe-west1 region.
Connections to social accounts: Access and refresh tokens for the accounts we connect, plus the account, page or channel name so the owner can see which account is linked. Tokens are kept in Google Secret Manager, one secret per connection, and are never sent to the browser.
Results of our own publications: For each published post, the id and public URL returned by the platform, whether it succeeded or failed, and — where the platform offers it — the reach, impressions and engagement counts of that post.

Connected platforms

We connect one account per platform, always our own, always through the platform's official authorization screen. In every case the account holder chooses what to grant, and we ask for the narrowest set of permissions that lets us publish. We never read other people's accounts, we do not search or index any platform, and we do not buy, sell or exchange data with anyone.

YouTube

Elele Social Studio uses YouTube API Services. By connecting a channel, you also agree to the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy.

youtube.upload — uploading an approved video, with its title, description and tags, to the connected channel (videos.insert). This is our only write call.
youtube.readonly — read once, immediately after authorization, to fetch the name of the connected channel (channels.list), which the panel displays so the owner can confirm the right channel was linked.

We do not read, store or display statistics, comments or playlists from YouTube. Of an upload we keep only the video id and watch URL. Access can be withdrawn at any time from myaccount.google.com/permissions, or with "Bağlantıyı kaldır" (Remove connection) in the panel, which deletes the stored tokens.

Facebook, Instagram and Threads

These run on Meta's APIs and are authorized through Facebook Login.

Facebook Page — pages_show_list to let the owner pick which of our Pages to link, pages_manage_posts to publish the approved post, and pages_read_engagement to read the reach and engagement of the posts we published.
Instagram — instagram_basic for the business account name and the insights of our own posts, and instagram_content_publish to publish them.
Threads — threads_basic for the profile name, threads_content_publish to publish.

We do not read messages, comment threads, follower lists or anyone else's content. Access can be withdrawn from Facebook settings or by removing the connection in the panel.

TikTok

user.info.basic — the display name and avatar of the connected account, shown in the panel so the owner can confirm the right account.
video.upload — sending an approved video to the account's TikTok inbox as a draft. The caption and the decision to post are completed by a person inside the TikTok app; we cannot publish anything on TikTok on our own.

Access can be withdrawn in the TikTok app under Settings → Security → Manage app permissions, or by removing the connection in the panel.

user_accounts:read — the username of the connected account, shown in the panel.
boards:read and boards:write — picking the board our pins go to when the account is connected, and creating one if the account has none.
pins:write — creating a pin on that board from an approved draft, and pins:read to read the statistics of our own pins.

We do not read other people's pins, boards or profiles. Access can be withdrawn on Pinterest under Settings → Security → Connected apps, or by removing the connection in the panel.

X (Twitter)

users.read (with tweet.read, which X requires alongside it) — the name and handle of the connected account, read once when it is connected.
tweet.write and media.write — publishing an approved post, with its image and the image's alt text, to our own account.
offline.access — keeping the connection alive without asking the owner to log in again every two hours.

We do not read timelines, search, direct messages or anyone else's posts. Access can be withdrawn on X under Settings → Security and account access → Apps and sessions → Connected apps, or by removing the connection in the panel.

AI providers

Draft copy and images are generated with third-party AI models. What we send is the brief and the draft text of the post we are writing. We do not send platform tokens, data read from connected accounts, or personal data about anyone outside our team.

Deleting your data

Everything we hold about a connected account can be removed by you, at any time, in two ways:

In the panel — "Bağlantıyı kaldır" (Remove connection) on the Connections screen. The stored tokens are destroyed together with the secret that held them, and the connection record is deleted.
At the platform — revoke our app's access in your YouTube/Google, Meta, TikTok, Pinterest or X account settings, using the links in the sections above. Access stops immediately.

To have the rest deleted — the campaign content, media files, published post records or a team account — write to cenkledigital@gmail.com and we will delete it within 30 days and confirm by email.

How long we keep things

Tokens: until the connection is removed, then deleted with their secret.
Campaign content and media: while the campaign is in use, and deleted on request.
Post records and their metrics: kept as our own publishing history, deleted on request.
Team accounts: until the person leaves the team or asks to be removed.

Who else sees the data

Nobody outside the team. We do not sell or share anything. The data sits with our infrastructure providers — Google Cloud and Firebase — and, for the drafting step described above, with our AI providers. Publishing sends the post to the platform you connected, which is the point of the tool.

Security

Sign-in goes through Firebase Authentication, and every call from the panel is verified with Firebase App Check. Tokens are stored in Secret Manager rather than the database so that they never appear in backups, exports or logs, and they are read server-side only, inside a Cloud Function.

Changes

When we add a platform or ask for a new permission, we update this page before the change goes live, and the date at the top changes with it.

Contact

Questions, or a request to delete something: cenkledigital@gmail.com.