Overview
This policy applies to the Primsy mobile app, the Primsy API that the app talks to, and this website. It is operated by Primsy ("we", "us"). In short:
- You sign in with an email address. A one-time code is sent to it. We do not use passwords.
- You connect your own Threads and Instagram accounts. You can connect more than one of each and group them into profiles. For each account we read its profile, its recent posts, and the performance numbers the platform reports for them. We publish only the posts you schedule.
- Everything you see comes from your own accounts. We do not compare you to other users, build audiences, sell data, or show ads.
- We measure how the app is used. The app and our servers send a small set of usage events to our product analytics provider, PostHog. They are tied to your account identifier and never used for advertising.
- You can delete your account and its data from inside the app. Deletion takes effect immediately, uploaded media files included.
What we collect
Account information
- Email address. Used to sign you in with a one-time code and, if you contact us, to reply. Your email is held by our sign-in provider, Clerk, and is also sent to RevenueCat (see Subscription status). Our own database keys your data to an opaque account identifier that Clerk assigns to you.
- Time zone. The IANA time zone your device reports, so that scheduled posts and the weekly recap go out at the local hour you chose.
- Language. The language your device uses, so that notifications are written in it.
- Notification preferences. Whether you want a push when a post is published and whether you want the weekly recap.
- How you organize your accounts. The names you give your profiles and posting groups, which accounts belong to each, the photo each profile uses, and any weekly posting goal you set.
Data from your connected accounts
When you connect a Threads or Instagram account, and on every sync afterwards, our servers call that platform's API on your behalf and store the following for each account:
- Profile. The platform's user ID for you, your username, and your profile picture URL. For Instagram we also read the account type, because publishing requires a professional account. These are refreshed on every sync.
- Recent posts. The text or caption, timestamp, and media type of your 25 most recent posts. For Threads we also store whether a link is attached, but not the link URL itself, and reposts are skipped.
- Per-post metrics. Views, likes, replies or comments, reposts or shares, and Threads quotes for each of those posts. Each sync stores a new snapshot rather than overwriting the last one, which is how the app shows how a post performed over time. One adjustment is made to Threads numbers before storing: replies you posted yourself as later parts of a chain are subtracted from that post's reply count, so the number reflects other people.
- Account metrics. Your follower count and, for Threads, your daily profile views for the past 90 days.
- Audience demographics. The aggregate breakdown of your followers by country, city, age range, and gender, exactly as the platform reports it. This is summary data about your audience as a whole. It never identifies an individual follower, and we never collect data about your followers as people.
Syncs run on our servers roughly every six hours, hourly for posts published in the last 24 hours, and when you open the app (at most once every five minutes per account).
Content you create in Primsy
- Scheduled posts. The text of each post and of each reply in a chain, the account or group you chose, the time you chose, the status of the post, and, after publishing, the IDs the platform assigned to it. If publishing fails, the error message the platform returned is stored with the post.
- Drafts. Posts you save as drafts are stored on our servers, with their text, attached media, and settings, so you can finish them later on any device.
- Media. Photos and videos you attach to a post. Each file is uploaded from your device to our storage the moment you attach it, even if you never schedule the post, and it is served from a public URL with an unguessable random name, because Threads and Instagram fetch media from a URL when they publish. See Retention for how long we keep these files.
- Link previews. When you type a URL into the composer, our servers fetch that web page to show a preview card. We cache the page's title, description, image URL, and site name for up to seven days. The cache is keyed by the URL only and is not linked to your account.
- Link clicks. Link tracking is off unless you turn it on. If you turn it on for a URL in a scheduled post, we replace that URL with a short Primsy link. If you create a bio link, we give you a short link to place in your profile. When someone opens either kind of link, we record the time and the country the request came from. We do not record the IP address, device, or identity of the person who clicked, and clicks from known crawlers and link-preview bots are not counted.
Device, usage, and diagnostic information
- Push notification token. If you allow notifications, the Expo push token for your device, whether it is iOS or Android, and its language, so our servers can notify you when a post publishes, fails, or a connection needs attention. The "post published" notification names the account and quotes the first 60 characters of the post, so that text passes through Expo's push service and Apple's or Google's push service.
- Product analytics. The production app and our servers send usage events to PostHog, tagged with your account identifier and the app version. Today these events are: an account was connected, a post was scheduled (which channels, and how many replies and media files), a post was published or failed (the channel and the reason), and the app asked you for an App Store review. The events never include the text or media of your posts. PostHog's app library also records basic device details, such as the device model and OS version, and PostHog derives an approximate location from the network address of each request. Session recording is off. Nothing is sent from development builds.
- Crash and error reports. The production app sends crashes and errors to Sentry with your account identifier, the app version, device model and OS version, and the screen the error happened on. App sessions also send performance timing to Sentry. Our API reports its own errors to Sentry too, with the request path. Sentry is configured not to collect personal information by default, and it does not record your screen or replay sessions. Nothing is sent from development builds.
- Feedback service. The app uses Mite for in-app feedback. Each time the app launches it registers with Mite using an anonymous identifier and a description of your device: the device name as set in your phone's settings (which is often your own name), model, manufacturer, OS version and build, memory, and CPU architecture. Once you are signed in it also sends your account identifier and the app version. If you use "Report an issue", the text you write is sent with the same details. Bug reports do not include screenshots or a record of the screens you visited.
- Job history. Our database keeps a record of each sync, publish, and recap attempt for your account, with its status and any error message.
- Server logs. Our API runs on Cloudflare Workers. Its logs can contain your account identifier, post identifiers, and the error message a platform returned when something fails. We use them to find and fix problems.
Subscription status
If you subscribe to Primsy Pro, the purchase is made through Apple or Google and managed by RevenueCat. The app gives RevenueCat your account identifier, your email address, and your display name, so that a purchase can be matched to you if you contact us about it. RevenueCat sends our servers a notice for each subscription event, saying whether your subscription is active, the product you bought, and when it expires. We store that notice in full, along with your account identifier. A notice can include the email address and display name the app gave RevenueCat. We never see your card number or your Apple or Google account details.
Your Threads and Instagram connections
Connecting an account authorizes Primsy through Meta's OAuth flow. Instagram connections need an Instagram professional (business or creator) account. We ask for the following permissions, and here is what each one is for.
Threads
| Permission | Why we need it |
|---|---|
| threads_basic | Read your profile and your own posts. |
| threads_manage_insights | Read views, likes, replies, reposts, quotes, follower count, and audience demographics. |
| threads_content_publish | Publish the posts you schedule, at the time you chose. |
| threads_manage_replies | Publish the later parts of a multi-post chain as replies to the first part. |
| threads_read_replies | Requested alongside reply publishing. The app does not currently read replies, and we do not store any. |
| Permission | Why we need it |
|---|---|
| instagram_business_basic | Read your profile, account type, follower count, and your own posts. |
| instagram_business_manage_insights | Read views, likes, comments, shares, and audience demographics. |
| instagram_business_content_publish | Publish the posts you schedule, at the time you chose. |
Connecting runs through Clerk, which holds the short-lived token from the OAuth handshake as part of your sign-in identity. Our servers exchange it for the long-lived access token that the service actually uses, and store that token in an isolated per-account store on Cloudflare. It is never stored in our main database and never sent to your device. The app itself never talks to Threads or Instagram; every request goes through our API. Long-lived tokens expire after 60 days. Our servers refresh yours automatically before then, retrying if that fails, and send you a push notification when a connection is about to expire or has expired so you can reconnect.
Your use of Threads and Instagram is also governed by Meta's own terms and privacy policy. You can revoke Primsy's access at any time from your Threads or Instagram settings, or remove the account in Primsy. Either way, syncs and scheduled publishing for that account stop until you reconnect.
How we use your data
- To show you your insights. Best posting hour, per-post performance, follower growth, link clicks, and audience breakdowns are computed from your own snapshots on our servers, using ordinary arithmetic. No machine learning models, and no data from other users, are involved.
- To publish what you scheduled. At the scheduled minute our servers create the post on each account you chose, using that account's token and the text and media you provided.
- To notify you. Push notifications when a post publishes or fails, a weekly recap on Sunday evening in your time zone if you keep it on, and a warning when a connection needs to be renewed. Failure alerts cannot be turned off, because a silently failed post is the one thing the app must never do.
- To run subscriptions and plan limits. To unlock Pro features when RevenueCat tells us your subscription is active, and to count your scheduled posts and profiles against the limits of your plan.
- To improve the app. Product analytics tell us which features people use and where publishing fails, so we can fix and improve them.
- To keep the app working. Crash reports, feedback, and server logs are used to find and fix bugs.
What we do not do
- We do not sell, rent, or share your data with anyone for their own purposes.
- We do not show ads or use advertising SDKs, and we do not track you across apps or websites owned by other companies. Our product analytics are used only to improve Primsy.
- We do not compare your accounts to other users' accounts, and there are no benchmarks, cohorts, or aggregate statistics built across users. Every number in the app comes from your own accounts.
- We do not send your posts, metrics, or any other content to AI or language-model services.
- We do not collect your contacts, precise location, photos you did not attach to a post, or any data about your followers as individuals.
- We do not publish anything that you did not schedule yourself.
- We do not use cookies or analytics on this website.
Service providers
These are the companies that process data on our behalf. Each receives only what is needed for its job, and each is bound by its own privacy terms.
| Provider | Role | What it receives |
|---|---|---|
| Meta Platforms (Threads API and Instagram API) | Source of your insights and the destination for your posts | Your access tokens, the posts and media you publish, and API requests for your own data |
| Clerk | Sign-in and account identity | Your email address, one-time sign-in codes, and the OAuth links to your Threads and Instagram accounts |
| Cloudflare | Hosting for the API, background jobs, token storage, media storage, short links, and logs | Everything the API processes, and uploaded media files |
| PlanetScale | Hosted Postgres database | Your account record, synced account data, scheduled posts, drafts, metrics, link clicks, and preferences |
| Expo | Push notification delivery and over-the-air app updates | Your push token and the notification text, which can include an account name and the first 60 characters of a post |
| PostHog | Product analytics | Your account identifier, app version, the usage events listed above, basic device details, and the network address it derives an approximate location from |
| Sentry | Crash and error reporting | Error details, device and OS version, app version, and your account identifier |
| Mite | In-app feedback and bug reports | Device details including the device name, an anonymous identifier, your account identifier, app version, and any report text |
| RevenueCat | Subscription management | Your account identifier, email address, display name, and purchase events from Apple or Google; we keep each event notice it sends us |
| Apple and Google | App distribution, push delivery, and payment processing | Handled under your Apple or Google account; we do not receive payment details |
We may also disclose data if the law requires it, or to protect the rights and safety of Primsy and its users. If Primsy is ever acquired, your data would transfer with it under this policy, and we would tell you first.
Data on your device
The app keeps very little on the phone itself:
- Your sign-in session token, in the device's secure keychain.
- Your time zone preference, in the secure keychain.
- Onboarding progress, the profile you last viewed, and the account you last posted to, in local app storage.
- Anonymous identifiers for the feedback and analytics services, and analytics events waiting to be sent, in local app storage.
Insights and posts are fetched from our API each time you use the app and are held in memory only. Photos and videos you attach are read from where you picked them and uploaded; the app does not keep its own copies. Logging out or deleting your account clears the in-memory data and the session token.
Retention
- Account, synced account data, posts, drafts, and link clicks are kept for as long as your account exists, unless you delete them sooner.
- Metric snapshots are kept in full for 14 days. After that, a daily job keeps one snapshot per post per day and deletes the rest. The history that remains is what the trends are built from.
- Access tokens are destroyed the moment you delete your account or remove the account from Primsy.
- Removed accounts. When you remove a Threads or Instagram account, the data already synced for it stays in your Primsy account until you delete your Primsy account, so the history is there if you reconnect.
- Uploaded media files are stored under an unguessable random name and kept only as long as a post or draft still needs them. Canceling a post deletes its files at once, unless a requeued copy of the same post still points at them. Deleting your account deletes every file you uploaded. Files that no scheduled post or draft references, including ones you attached but never scheduled and ones belonging to posts that already published, are deleted by a daily sweep once they are 30 days old. If you want a file removed sooner, email us at support@getprimsy.com.
- Link previews are refreshed after seven days.
- Analytics events, crash reports, feedback, and server logs are kept by PostHog, Sentry, Mite, and Cloudflare for the retention periods those services apply.
- Subscription records are kept by RevenueCat and by Apple or Google according to their policies.
Disconnecting and deleting
Delete your account from Account → Delete account in the app. This runs immediately and cannot be undone. In order, it:
- destroys the access tokens of every connected account on our servers;
- deletes your account record, which removes your push tokens, connected account data, profiles and groups, all scheduled and published post records, drafts, every metric snapshot, audience data, tracked links and their click records, notification preferences, and subscription notices;
- deletes every media file you uploaded from our storage;
- deletes your identity, including your email address, at Clerk;
- signs you out on the device.
Posts already published stay on Threads and Instagram, including any media those platforms copied when they published them. Deleting your account does not cancel a store subscription; cancel it in your Apple or Google settings. Analytics events, crash reports, feedback, and subscription records held by PostHog, Sentry, Mite, and RevenueCat are not erased by this step; email us and we will ask those providers to delete them. If you prefer, email us and we will delete your account for you.
Removing one account without deleting yours is possible from your profiles in the app, or by revoking Primsy in your Threads or Instagram settings. That stops syncing and publishing for that account. Data already synced stays in your Primsy account until you delete it. Scheduled posts for that account that come due while it is disconnected fail and you are notified; they are never published later without your say-so.
Logging out keeps your data and your schedule. Scheduled posts still publish while you are logged out.
Security
- All traffic between the app, our API, and our providers uses HTTPS.
- Every request for your data is authenticated with a short-lived session token issued by Clerk. The only unauthenticated routes are the public media URLs and short links described above, a health check, and the RevenueCat webhook, which is protected by a shared secret.
- Access tokens live in an isolated Cloudflare Durable Object per connected account, separate from the main database, and are never sent to the device.
- Media files are served from URLs that contain a random identifier. Anyone with the exact URL can open the file; that is what allows Threads and Instagram to fetch it. Do not attach media you would not want to be public, since the post it belongs to is public too.
- Crash reporting is configured not to send personal information by default.
No system is perfectly secure. If you believe you have found a vulnerability, please email support@getprimsy.com.
Your rights
Wherever you live, you can access, correct, export, or delete your data, and object to or restrict how we use it. Deletion is built into the app. For anything else, email support@getprimsy.com from the address you signed up with and we will respond within 30 days. We will not treat you differently for exercising these rights.
If you are in the European Economic Area or the United Kingdom, we process your data to provide the service you asked for (performance of a contract), to keep the service working, secure, and improving (our legitimate interests, which covers crash reporting and product analytics), and for anything else with your consent, which you can withdraw at any time. You can object to product analytics by emailing us. You also have the right to lodge a complaint with your local data protection authority.
If you are in California, we do not sell or share personal information as those terms are defined in the CCPA, and we have not done so in the preceding twelve months.
Where your data lives
Our database is hosted by PlanetScale in the United States (AWS us-east-1). The API, token storage, and media storage run on Cloudflare's global network. Our product analytics are hosted by PostHog in the United States. Our other providers operate primarily in the United States. If you use Primsy from elsewhere, your data is transferred to and processed in the United States under this policy and under the safeguards our providers offer, such as standard contractual clauses.
Children
Primsy is not directed to children under 13, and Threads and Instagram themselves require users to be at least 13. We do not knowingly collect data from anyone under 13. If you believe a child has created an account, email us and we will delete it.
This website
This site is static. It sets no cookies, loads no analytics or third-party scripts, and stores nothing in your browser. Our hosting provider, Cloudflare, may keep standard server logs to serve and protect the site.
Changes to this policy
When the app changes what it collects, this page changes with it, and the effective date at the top is updated. For a material change we will also tell you in the app or by email before it takes effect.
Contact
Questions, requests, and complaints go to support@getprimsy.com. You can also use "Report an issue" inside the app.