LAST UPDATED · 26 October 2026

Privacy notice

Who we are

Unisenda is operated by OR PxlSafe Živinice, Stari Djurdjevik bb, 75270 Živinice, Bosnia and Herzegovina. Questions about your information or requests to access or delete it can be sent to hello@unisenda.com.

What we store and why

Unisenda stores account identifiers and email addresses used for sign-in, workspace identifiers, drafts and captions, uploaded media, selected social account identifiers and names, scheduling information, and publishing results. When you connect a social account, the platform provides authorization tokens that let Unisenda perform the actions you permit. Unisenda does not ask for your social network password. Social authorization tokens are encrypted in the application database.

This information is used to authenticate you, save your content, display your connections, perform publishing actions you request, run scheduled jobs, and investigate errors. Selecting a schedule authorizes Unisenda to attempt publishing that content at or after the selected time. Your browser also stores preferences and unfinished composer copies; signing out does not necessarily erase those local copies.

Service providers and payments

Vercel hosts the application, and Neon provides its database, sign-in services and media storage. Resend delivers the emails Unisenda sends, such as team invites, review links and codes for client reviewers, welcome and tip emails, and alerts when a scheduled post fails; it receives the recipient's address and the email's content. These service providers process information needed to run the service. Content and account data needed for publishing are sent to the social networks you select. Media is stored privately, but a time-limited media link is shared with a selected network when that network must retrieve the file. Published posts are governed by the destination network's audience settings and privacy policy.

Dodo Payments processes checkout, subscriptions, invoices, refunds and payment disputes as merchant of record. Dodo receives the billing identity and payment details you provide at checkout. Unisenda stores provider customer/subscription identifiers, plan and billing status to manage access and support; Unisenda does not store full payment-card numbers. Dodo handles payment data under its own privacy notice at https://dodopayments.com/privacy-policy.

Notifications, feedback and emails

If you turn on notifications on a device, we store that device's push subscription (the delivery address and encryption keys your browser provides) and a short device label, and use them only to send the alerts you chose, such as a post going live or failing. They are deleted when you turn notifications off on that device or delete your account. When a scheduled post fails, we also email the account owner. If you send feedback from the app, we keep your message, optional rating, the page you were on and your browser type with your account, and email it with your address to our support inbox so we can reply. It is deleted with your account.

If you ask to be notified at launch, we keep your account email on our waitlist to tell you when subscriptions open; after you sign up we also send a welcome email and at most two getting-started tips (turn them off in Settings → Notifications), recording which were sent; all of this is deleted with your account. We email you about offers, ideas and plan discounts only if you turn on “Emails about offers and tips” in Settings → Notifications; we keep the date, the wording you saw and your address as the record of your choice, every such email has an unsubscribe link, and you can turn it off at any time. Emails about your account, payments and posts, such as a trial ending or a payment that did not go through, are service emails and are sent either way.

Teams

Teams (Studio plan): when an account owner or admin invites someone, we store the invited email address, the role and workspaces chosen, the inviter's name, and when the invite was sent and answered, and we email the invite to that address. Only a scrambled form of the invite link is stored. Invites that are declined, withdrawn or expired are deleted 30 days after they close. When someone joins, the team's owner and admins can see that teammate's name, email address, role and join date, and teammates can see and change the posts, media and schedules in the workspaces they are given. Billing details are only ever visible to the account owner. Removing a teammate, or a teammate leaving, ends their access at once; the posts they made stay in the team's workspaces. If you delete your account, your team memberships and any team you own are deleted with it.

Client reviewers

Client approvals (Studio plan): when an account owner or admin adds a reviewer, we store the reviewer's name and email address, who added them and when, and email them a private review link. When a reviewer opens the link, we email a one-time 8-digit code to that address. Review links, codes and review sessions are stored only as scrambled hashes. A code works for 10 minutes and a review session for 12 hours, and we keep the times they were issued and used. Reviewers don't get a Unisenda account or a team seat, and a reviewer sees only the posts sent to them for review, never your accounts, billing, media library, teammates or other workspaces.

We keep what a reviewer does on a post: their approval or request for changes, any comment they write and when it happened. Your team sees these in the post's history, and we email the person who sent the post, and the owner, when a reviewer decides. Removing a reviewer ends their link and sessions at once and erases their name, email address and link; their past comments stay in the post's history under the name they used. Deleting a post, a workspace or your account: a deleted post keeps its review history without the post itself, and a deleted workspace or account removes its reviewers and review history. We also keep a record of the review emails we send, with the address only in scrambled form, for two days to limit repeated emails.

AI assistants

You can connect an AI assistant you use, such as ChatGPT or Claude, to one Unisenda workspace. You start this from the assistant. Unisenda then asks you to sign in and shows which workspace it may open and whether it may only read or also save drafts. Nothing is shared until you choose Allow.

When you ask the assistant to, it reads information from that workspace through Unisenda: the names and handles of your connected social accounts, your posts and captions, planned and scheduled times, whether each post went out, and your plan and usage. It can save and edit drafts and add photos and videos to them if you allowed that. It cannot publish, schedule or delete posts, delete or change your files, change settings, or see your social-network sign-ins, your Unisenda sign-in or your payment details.

Photos and videos an assistant adds are stored like the files you upload yourself, at their original quality, and count toward your storage. If the assistant sends a link, Unisenda's servers download the file from it (only public https links are fetched). If it gives you an upload link, anyone who opens that link in the next 30 minutes can add files to that one draft, so share it with no one; the link works for one visit, shows only the workspace name and the start of the draft's caption, and we keep only a scrambled form of it. The assistant itself does not receive your files' contents.

What the assistant reads is sent to the company that runs it, for example OpenAI for ChatGPT or Anthropic for Claude, and is handled under your agreement with that company and its privacy policy. Unisenda sends it only when your assistant asks for it on your behalf.

For each connection we store the name the assistant gave, the address it returns to, the workspace and access you chose, when it was connected and last used, and only scrambled forms of its access codes. We also keep a log of what it did (which action, when, whether it worked, and which post) for 90 days; the log holds no captions. Access codes stop working after one hour and are renewed while the assistant is in use; a connection not used for 30 days has to be approved again.

You can disconnect an assistant at any time in Settings → AI access, and it stops working at once; drafts it saved stay in your workspace. The owner of a workspace can also disconnect assistants their teammates connected to it, and leaving a team or deleting a workspace ends the assistants connected there. Ended connections and their logs are deleted after 90 days. Deleting your account deletes your connections and their logs. Assistant connections are not kept in our backup copies, so after a restore you may need to connect an assistant again.

Your choices

Unisenda does not sell your content or use connected social data to train AI models. An AI assistant you connect only gets the access you approve on Unisenda's consent screen (see AI assistants). Connecting one does not let its provider use your content to train models through Unisenda.

You can remove drafts and eligible unused media within the app. Removing a local draft or media file does not delete an already published social post. You can revoke provider access in the social network's connected-app settings. Contact hello@unisenda.com to request removal of your account and associated cloud data. We retain cloud content while your account is active unless you delete it or request its removal. Deletion requests are handled manually after verifying account ownership. Deleted media may be retained privately for up to seven days for recovery. Encrypted recovery copies of application data and media are stored with Vercel separately from Neon, with a seven-day retention target. Cleanup can be delayed during service outages. Account deletion also removes retained media from active storage; backup copies expire under the recovery schedule and are not used for publishing.

Google and YouTube

Google and YouTube data sharing: when you connect YouTube, Unisenda accesses your channel ID, channel name and handle, authorization scopes and OAuth access/refresh tokens. It also receives video IDs, channel ownership, privacy settings and processing/publication status for uploads made through Unisenda. We use this information to show your connection, upload your selected videos, and confirm delivery.

Vercel is our application hosting and server-processing provider. Google/YouTube authorization responses, channel information, tokens and upload results are processed on Vercel so Unisenda can complete sign-in to YouTube, renew your authorization, send uploads and check their status. Neon is our database provider: it stores channel identifiers, names and handles, encrypted OAuth tokens, and publishing records such as video IDs and delivery status. Neon also stores the media you upload to Unisenda. These providers process this information to operate Unisenda's connection, storage and publishing features.

Google/YouTube receives authorization and token-renewal requests and the tokens and video identifiers needed to upload or check a video. When you choose to publish or schedule a YouTube video, we send Google/YouTube the video you selected, its title and description, your visibility choice, and the audience and altered-content settings you selected. Google/YouTube processes these requests under its own policies.

We do not share Google/YouTube authorization tokens, channel information or API-derived video records with other connected social networks, AI providers, advertisers, data brokers or information resellers. Content you independently upload or write in Unisenda may be sent to other networks only when you select those destinations. We do not sell Google user data or use it for advertising or AI model training. Human access to Google user data is limited to your affirmative consent for specific data, necessary security investigations, or legal requirements, in accordance with Google's Limited Use requirements.

Unisenda uses YouTube API Services to identify the authorized channel and upload videos you select. Unisenda’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. See https://developers.google.com/terms/api-services-user-data-policy. Google's privacy policy is available at https://policies.google.com/privacy. You may revoke access through https://security.google.com/settings/security/permissions. Disconnecting a channel removes its usable authorization tokens from Unisenda immediately, and its remaining identifiers (channel ID, name and handle) are deleted within 7 days. The same applies to every other connected network. You can request deletion of stored channel information and publishing records through the contact address above.

Other networks

Facebook, Instagram and Threads (Meta): when you connect, Unisenda receives the Facebook Pages you choose to manage with Unisenda, their names and IDs, Page access tokens and the linked Instagram professional account's ID and username, or your Threads profile ID and username. Tokens are encrypted. Unisenda uses this information only to show your connections and to publish the posts, images and videos you select or schedule to those accounts. Unisenda does not read your messages, comments, followers or insights and does not use Meta data for advertising. Disconnecting removes the usable tokens; you can also remove Unisenda in your Facebook, Instagram or Threads settings and request deletion at https://unisenda.com/data-deletion.

Pinterest and Bluesky: a Pinterest connection reads your profile name and your boards so you can choose where to save a Pin, and stores encrypted authorization tokens. A Bluesky connection stores your handle and an encrypted session so Unisenda can post what you select. These connections are used only to publish content you choose.

TikTok, LinkedIn and X connections identify the profile you authorize and store encrypted authorization tokens. Unisenda uses these connections to publish content you explicitly select or schedule, subject to the available integration, audience settings and platform permissions. TikTok posting is limited to private (“Only me”) posts until TikTok approves Unisenda's integration. LinkedIn supports personal-profile text, image and video posts; X supports text and image posts and charges for API usage. We do not serve third-party advertising. Essential cookies maintain sign-in and protect connection requests; browser storage saves appearance preferences and unfinished drafts.