Membership and product use
When you open the product with your verified account, your user ID, your usage interval by time zone and the time you were last seen are added to service records. These records let the authorized administrator follow daily, monthly and yearly active members. The admin panel can show your email, sign-up/verification and last sign-in dates, the number of connected accounts, the file space used and private administrator notes added for support. Admin rights are assigned on the server; members cannot see other members’ information or private administrator notes. The time, type and related record ID of admin actions are kept in the activity history.
Only for the authorized administrator account, before the admin page is served, a short-lived access token is sent from our own Cloudflare server to the same Supabase project to verify it. Admin access uses a Secure, HttpOnly, SameSite=Strict cookie sent only on the /admin path. The cookie contains no refresh token and never outlives the access token. No admin cookie is created for non-admin accounts.
The demo and your account are separate
Text, publishing destinations and plan dates in the demo are stored only in this browser’s local storage. Comments in the demo are samples; replies stay in session memory only. Demo drafts are never uploaded to your account. The delete button on a demo card, or clearing browser data for this site, removes local drafts.
What is stored in your account?
Studio sign-ins are verified by Supabase Auth. Your email, user ID and session details, your workspace, membership and the text drafts you create are processed in Postborne’s Supabase project. A change history of the text is kept. Adding a plan date does not start a real social post. The session is stored in this tab’s session storage; you can sign out. To complete the sign-in return securely, a short-lived PKCE verifier is kept in the browser’s local storage and expires within an hour.
Sign-in, sign-up and password reset forms use Cloudflare Turnstile to check that the request comes from a person. For this check Cloudflare processes technical signals from your browser and device; the check result is verified by Supabase Auth. We do not use Turnstile for advertising or tracking.
Data access and deletion
Access to a workspace is limited in the database by membership and role. Other customers cannot access your content; the authorized project administrator may have technical access. Deleting in Studio removes the draft and its change history; a draft linked to a publishing job may not be deletable. This does not mean the provider deletes its backups and security logs at the same time. To close your account and ask for your personal data to be deleted, follow the steps on the data deletion request page.
Uploaded files
The file itself, its name, type, size, SHA-256 fingerprint, image/video dimensions and, where available, duration are processed. Uploading a file in the browser does not publish it; attaching it to a draft is saved separately. Studio previews are shown through short-lived signed links. During an approved post, the relevant provider may get time-limited access to the file as described below. A file attached to a draft or a pending post cannot be deleted. Deleting a file removes the stored file; metadata and references in old revisions may remain for technical checks. This does not mean provider backups or logs are deleted at the same time.
Which services receive data?
Sign-in and account data operations go over HTTPS to Postborne’s Supabase project; the project region is Europe (Ireland). Verification, magic-link and password reset emails are sent through Brevo. Brevo processes the recipient email address, the message content and the one-time account link; the provider may keep delivery and security logs. Requesting an account email does not create a marketing subscription. Images and videos are kept in private storage: new uploads in Postborne’s Cloudflare R2 storage and earlier uploads in Supabase’s private storage. Neither is publicly accessible; workspace members read files with their session through short-lived signed links. Stored objects older than 45 days are deleted automatically. The server checks file format, size and quota. Data scope for social connections and the API is described below.
To be able to restore the service after an incident, an encrypted copy of the database is made once a day and kept in private Cloudflare R2 storage for 45 days. The encryption key is held only by the server and the project owner.
Sign in with Google
When you choose to continue with Google, Google passes your account ID, verified email address and basic profile information to Supabase Auth to verify your Postborne account. This information is used for sign-in and account matching. YouTube access for publishing is granted in a separate permission step.
YouTube channel connection
When you start the connection, the Google screen asks for permission to read your channel and upload videos. Your Google password is never given to Postborne. The ID and name of the channel you choose are saved to the workspace; the refresh token that lets it work without asking again is stored encrypted on the server. The temporary access token is used only in server requests to Google. Connecting does not upload a video; publishing needs a separate content approval. Google data is not used for advertising, sale or model training. You can remove the permission in your Google account connections; this does not by itself delete the record in Postborne or old backups. To remove connection records from Postborne, use the data deletion request section.
Private upload and scheduling
For a YouTube upload, once the file, title, description and content declarations are approved, the video is sent to Google as private; subscriber notifications are off. If you choose a date and time, the UTC time and the chosen time zone are stored with the record. The Supabase server checks approved scheduled jobs every minute. Other jobs, quota, connection and provider delays can postpone the start. Changing the date removes the previous approval. Cancelling a job that has not started stops the file from being sent to Google; for an upload that has started, the result must be checked first. The file transfer and YouTube’s processing result are tracked separately; the most recently verified visibility and processing time are shown on the record. Background calls are verified only with a short-lived, single-use permission tied to one job. Used or invalid temporary job permissions are cleaned up after about a day. Job records and content approvals are kept in the publishing history.
Instagram and Facebook
Connection permission is granted on Meta’s own screen (Facebook Login for Business); your social account password is never given to Postborne. The IDs, names and publishing-related task information of the Pages you manage and the Instagram professional accounts linked to them are read only so you can choose the account to connect. The ID, name, connection status, permissions and access expiry of the account you choose are stored. The Page access token is kept encrypted on Postborne’s Supabase server; it is never given to your browser or an AI client. The temporary connection record used for account selection is valid for 10 minutes.
When you approve the preview for the chosen draft, supported images or video and caption, the post is published publicly on the Page or Instagram account you chose. If you choose a date, the server publishes the approved job at that time. The file is passed to Meta only while publishing: for Facebook Reels, Meta receives a short-lived private signed link to the file; in other cases Meta gets a short-lived (10 minutes for images, 1 hour for video) private signed link to download it. The post’s Meta ID, link, approval time and job status are recorded. If comment access is enabled, Postborne lists the comments on your own posts and sends the reply or hide action you choose to Meta. Meta data is used for this account, publishing and permitted comment actions.
You can remove the permission you gave Postborne at any time in Meta’s settings; to have records in Postborne deleted, see the data deletion request section. To remove a post published on Meta, you need to delete it on Facebook or Instagram.
Threads
The Threads connection uses Meta’s own Threads authorization screen; your password stays there. Postborne stores your Threads user ID, username, granted permissions and the access expiry, and keeps the access token encrypted on the server. When you approve a post, the text and any media you chose are published publicly on your Threads profile; for media, Meta gets a short-lived private signed link to the file. Removing the connection in Studio deletes the stored token and profile details from Postborne. Published posts must be deleted on Threads.
Bluesky
When you connect Bluesky, you approve access on the sign-in screen of your Bluesky account’s server (PDS); your password is never given to Postborne. Postborne stores your account identifier (DID), handle, the address of your server and the granted scope, and keeps the access and refresh tokens encrypted on the server. When you approve a post, the text and up to four images or one video are published publicly on your Bluesky account. Removing the connection in Studio deletes the stored tokens and profile details from Postborne. Published posts must be deleted on Bluesky.
Your API and AI connections
API and MCP connections use your workspace’s draft, media and publishing records with the permissions you choose. You can revoke an API key or AI connection from the Connection Center. An API key is shown only once when it is created and stays valid until revoked; the server keeps a digest instead of the plain value. OAuth access is short-lived and the refresh token changes on every use. Revoking stops future access. You can send a data deletion request for past records.
The AI client receives the texts, file names/IDs, calendar and job results queried by the tools you allowed; the data terms of that AI service also apply. Admin keys and social account refresh tokens are never given to the AI client. The web file transfer page requires a Postborne session; knowing the link address does not give access to a file. API/MCP traffic goes through Cloudflare to our own Supabase project; large files uploaded through the API are sent in parts straight to private storage.
External resources and measurement
Fonts and promotional images are served from the application’s own files. Files uploaded by users come from the private storage described above. No advertising trackers, app analytics or paid AI calls of our own have been added. The site server, Cloudflare and Supabase may process their own operational security logs. During sign-in, only the publishable key designed for browser use is present; the admin key and database password are never given to the browser.
LinkedIn personal profile connection
When you connect or renew the permission, after your approval we read your LinkedIn profile name and ID. This information is used so you can pick the right profile in Studio. Your LinkedIn password stays on the LinkedIn screen. The permission expiry and connection status are saved to the workspace; the access token is kept encrypted on the server and used only to send requests to LinkedIn. Connecting a profile does not post anything on its own. When you remove the connection in Studio, the profile name, LinkedIn ID and access token are deleted from Postborne. For other records you can use the data deletion steps below.
When LinkedIn publishing is enabled, we send the post text you separately approve and, if any, the article link to LinkedIn to be shared publicly on the personal profile you chose. A scheduled post starts at the time you choose. The job status and the link of the published post are kept in the workspace. Removing the profile cancels pending posts. You can delete published posts on LinkedIn.
TikTok account connection
When you start the connection, TikTok’s own screen asks for permission to read your basic profile and to publish content you approve later. We use your profile name and app-specific account ID to show and verify the connection. Access and refresh tokens are stored encrypted on the server. Connecting only verifies the profile information. When you remove the connection in Studio, the profile details and access tokens in Postborne are deleted and a permission revocation request is sent to TikTok. You can also remove the permission in the app’s security settings on TikTok.
When video publishing is enabled, your account’s current visibility and interaction options are fetched from TikTok. When you separately approve the video and the publishing settings, TikTok receives an expiring link that can reach only that file. The approved caption, visibility and content declarations are sent to TikTok. The publishing status is shown in Studio. You can remove a published video on TikTok.
X account connection
When the connection is enabled, you use X’s own permission screen. Postborne reads your X username and account ID to verify the destination. Access and refresh tokens are stored encrypted on the server. When you remove the connection, the account details and tokens in Postborne are deleted. You can revoke the permission on X in your X connected apps settings.
Trial protection and file retention
To prevent repeated free trials with the same social account, a digest made with a secret key from the ID of every social account you connect during a trial is kept; the raw account ID is not stored in this record. This security record is kept even after your account is deleted, to enforce the trial limit. Uploaded files are kept only until publishing: they are deleted 1 hour after a successful post to every destination, and 24 hours after the last action for files that failed, were cancelled or were never scheduled. When a membership ends, remaining files are deleted after 7 days for a trial and 30 days for a paid membership. The post text, date and post link stay in your account.
Data deletion request
The steps are also on the data deletion page. To stop Postborne’s access to your social accounts: on Facebook, remove Postborne under Settings & privacy / Settings / Business Integrations; for Google, remove Postborne from your account’s third-party connections. This stops new access immediately.
To have the data stored in Postborne deleted, email postborne53@gmail.com from the email address registered to your account with the subject “Data deletion request”; name your Postborne account and, if any, which connected accounts you want removed. Never send passwords, codes or access tokens. After the requester’s account is verified, connection records, encrypted access tokens, drafts, uploaded files and publication job records are deleted and the result is sent to the same address. Security/activity logs and service provider backups are deleted on their own retention cycles; content already published on Meta, YouTube or other networks must be deleted on those platforms.
Privacy contact
For questions about your data and your account, write to postborne53@gmail.com.