Privacy policy
Last updated
This policy explains what personal data Postrush collects, why, who it is shared with, how long it is kept, and the rights you have. Postrush is a social media scheduler: you write posts, choose when they go out, and Postrush publishes them to the social accounts you connect.
Who we are
Postrush is run by Hussein Jarrah (“we”, “us”), Gunnekær 4, 2610 Rødovre, Denmark. We are the data controller for your account, billing, support and usage data. The developer apps that connect Postrush to Facebook, Instagram and TikTok are held by Avenholm Living ApS (CVR 46742230) at the same address, which is the data controller for the data Postrush receives from those platforms (see Connected social accounts). Contact: support@postrush.app.
Data we collect
- Account data: your name, email address and a hash of your password, if you set one (we never store the password itself), whether your email is verified, and your display preferences such as theme, week start and time format.
- Google sign-in: if you use Continue with Google, Google shares your name, email address and Google account id with us. We use them only to create your account, sign you in and show which Google account is connected in Settings. We do not keep your Google profile picture or any Google access token, and we never see your Google password.
- Sign-in sessions: for each session we store the IP address and browser type (user agent) it was created from, so you can see and end your sessions in Settings and so we can protect accounts.
- Security records: to slow down password guessing and abuse, we count requests per IP address and per account for a short time.
- Workspaces and teams: workspace name, address and timezone, the members and their roles, invites (the invited email address and role), and a log of membership changes that contains ids, not names or emails.
- Your content: posts, drafts, schedules, the per-channel versions of each post, follow-up replies or comments, revision history with who edited what, signatures, and the settings you choose per channel.
- Media: the images and videos you upload, their original file names, sizes, dimensions and a checksum. Files are kept in private storage and are only shown to members of your workspace.
- Postrush AI: if you use Postrush AI (the assistant and AI images), we keep your chats, the images it makes (in your Media, like your uploads) and how much you use it. To answer you, we send your messages and the parts of your workspace the assistant reads (for example your posts, designs, channel names and the photos you point it to, as links or small previews) to our AI providers. For AI images we send your description of the image.
- Notifications and email: your email notification choices per workspace, in-app notifications, and records of the emails we sent you (type and delivery status).
- Payments and plan: when you subscribe, you pay on Stripe's secure page. Stripe, our payment processor, handles your card and billing details. We never see or store your full card number. We store the Stripe customer and subscription ids, your plan, billing period, trial dates and subscription status for each workspace.
- Sign-up source: the campaign tags (UTM) of your first and your last visit before you signed up, the website that sent you there (its address only, without the page), the first page you landed on, and your answer to "How did you hear about us?" if you give one. We also store how far you got with setup and the product tour.
- Affiliate program: if you apply to be an affiliate, your name, email address, profile links and your answers, which reach us as an email. We keep payout details (PayPal or Wise) outside Postrush, in our own records. If someone signs up through an affiliate's link, we record which affiliate brought them (the code in the link) with their sign-up source, and we store the affiliate's code on the subscription at Stripe. Affiliates see only counts and amounts, never the names or email addresses of the people they referred.
- Launch list: if you join our launch list on our website, your email address, when you joined and the wording you agreed to.
- Usage data: how you and other visitors use our website and app, collected with PostHog. See Cookies and browser storage.
- Ad measurement: when you sign up we store the IP address and browser type (user agent) of your sign-up request, together with the Meta or TikTok ad-click id and browser ids if you have them (for example because you came from one of our ads). See Cookies and browser storage.
- Error reports: when something in Postrush breaks, a short technical report of the error, sent to Sentry. See Who we share data with.
- Connected social accounts: described in the next section.
We do not receive your card number or bank details.
YouTube
Postrush uses YouTube API Services to upload videos you schedule to the YouTube channel you connect. By connecting YouTube you agree to the YouTube Terms of Service. Google's Privacy Policy applies to YouTube.
With your permission Postrush reads your channel's name, handle, avatar, subscriber count and verification status, the names of your playlists (so you can pick one), and the processing status of the videos it uploads for you; it uploads your videos with the title, description, tags and settings you chose and, when you pick a playlist, adds the video to it. Postrush stores your access tokens encrypted and your channel's name and avatar (refreshed at least every 30 days). It does not download or store YouTube videos. Postrush does not sell YouTube data and shares it only with the service providers listed under Who we share data with, to run Postrush.
When you disconnect YouTube, Postrush deletes its access tokens and, at once, the YouTube data it stored about the channel: its handle, avatar, subscriber count and channel details. Only the channel's name stays, so your posting history still shows where each post went. You can also remove Postrush's access at any time in your Google security settings; Postrush then deletes the same data within 30 days. When you delete your account, Postrush deletes all of it, the channel's name included. Questions: support@postrush.app.
Postrush's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Threads
Postrush uses Meta's Threads API to publish the posts and replies you schedule to the Threads profile you connect, with the settings you chose (who can reply, the topic and the AI label). Meta's Privacy Policy applies to Threads.
With your permission Postrush reads your Threads profile's id, username, name and profile picture, how many posts Threads still lets you publish today, and the id, time and link of each post it publishes for you. For your Analytics page it reads your recent posts (their text, type, link and picture) and the numbers Threads reports about them and your profile, such as views, profile views, likes, replies, reposts, quotes and followers. Postrush stores your access token encrypted.
When you disconnect Threads, Postrush deletes its access token. You can also remove Postrush in the Threads app under Settings, Account, Website permissions; Postrush then disconnects the profile. When you delete your account, Postrush deletes all of it. Questions: support@postrush.app.
How and why we use data
- To provide Postrush (account, workspaces, scheduling, publishing, notifications, support). Legal basis: performance of our contract with you (GDPR Art. 6(1)(b)).
- To take payment and manage your plan (checkout, renewals, receipts, failed-payment handling, fraud and dispute handling, tax and accounting records). Legal basis: performance of our contract with you (Art. 6(1)(b)) and our legal obligations under bookkeeping and tax law (Art. 6(1)(c)).
- To run Postrush AI when you use it (the assistant and AI images). Legal basis: performance of our contract with you, the service you asked for (Art. 6(1)(b)).
- To keep Postrush secure (sessions, rate limits, the email suppression list, preventing abuse). Legal basis: our legitimate interest in protecting the service and its users (Art. 6(1)(f)).
- To find and fix errors (error reports with Sentry), so Postrush keeps working. Legal basis: our legitimate interest in running a reliable service (Art. 6(1)(f)).
- To send service emails: email verification, password reset and change notices, invites, ownership changes, and post alerts (a post failed, needs your attention, or was published). You can turn post alerts off per workspace in Settings or with the one-click unsubscribe link in each alert. Account and security emails can't be turned off while you have an account.
- To run the affiliate program (review applications, tell affiliates how many people they brought, work out and pay commission). Legal basis: performance of our contract with you (Art. 6(1)(b)).
- To email you about Postrush's launch, if you joined our launch list. Legal basis: your consent (Art. 6(1)(a)). You can withdraw it at any time with the unsubscribe link in each email or by emailing support@postrush.app.
- To measure and improve our ads (the Meta and TikTok pixels on our marketing pages, and the sign-up, trial and payment events we send them). Legal basis: our legitimate interest in measuring and improving our advertising (Art. 6(1)(f)). You can object to this at any time by emailing support@postrush.app. After that we stop sending Meta and TikTok events about your account. We cannot take back events already sent, and the pixels on our marketing pages are controlled by your browser or a content blocker. If you only joined the launch list, you can unsubscribe; we sent a single event when you joined and nothing more follows.
- To understand how people find and use Postrush (product analytics with PostHog, and the sign-up source stored with your account), so we can see which channels bring people to us and improve the product. Legal basis: our legitimate interest in improving Postrush and its marketing (Art. 6(1)(f)). You can object to this at any time by emailing support@postrush.app.
We do not send marketing emails, apart from the launch news you signed up for. We use the Meta and TikTok advertising pixels on our marketing pages and send them a few sign-up and payment events, as described under Who we share data with and Cookies and browser storage. We use PostHog for product analytics as described under Cookies and browser storage.
Who we share data with
We use these service providers (processors), who handle data only on our instructions:
- Cloudflare, Inc.: hosting, the database (located in Western Europe), private file storage, and forwarding of emails sent to support@postrush.app.
- Resend, Inc.: sending our emails, from its EU region (Ireland). Resend receives your email address and the email content.
- Stripe Payments Europe, Ltd. and Stripe, Inc.: processing payments and subscriptions. Stripe receives your email address, name, billing details and card details when you subscribe, and it sends you receipts and payment emails. For a customer who came through an affiliate's link, Stripe also stores the affiliate's code on the subscription. For card data and fraud prevention Stripe also acts under its own privacy policy.
- PostHog, Inc.: product analytics, hosted in its EU region (Frankfurt, Germany). PostHog receives the usage data described under Cookies and browser storage, your IP address (which it uses to estimate your location and does not store), and, once you are signed in, your internal user id and workspace id. It does not receive your name or email address.
- Functional Software, Inc. (Sentry): error reports, hosted in its EU region (Frankfurt, Germany). When something in Postrush breaks, Sentry receives the type of error, where in our code it happened, which page or background job it was in, your browser and operating system names and, once you are signed in, your internal user id and workspace id. It does not receive your name, email address, IP address, the text of your posts or anything you type.
- Anthropic, PBC: runs the Postrush AI assistant. Anthropic receives your messages and the workspace content the assistant reads to answer them and, when you use Draft with AI in Engage, the comment and the post it is on.
- OpenAI: makes AI images. OpenAI receives your descriptions of the images and a scrambled form of your user id (never your name or email), which it uses only to detect misuse.
Anthropic and OpenAI do not use this data to train their models, and they keep it only for a limited time to detect misuse.
Meta and TikTok (advertising):
- Meta Platforms Ireland Limited and TikTok (the entity named in our TikTok For Business terms) receive information about visits to our marketing pages through their pixels, and the events below through their server interfaces (Meta Conversions API, TikTok Events API).
- The pixels load only on our home, pricing, privacy, terms and data-deletion pages, never inside the app. They send the page view, your IP address and browser type, and the ad-click and browser ids described under Cookies and browser storage.
- When you join our launch list, complete sign-up, start a trial or make your first payment, we send Meta and TikTok the event, a hashed (SHA-256) form of your email address, your IP address and browser type, and the ad-click and browser ids. For sign-up, trials and payments we also send a hashed form of your account id, and for trials and payments the amount and currency where we know them. We do not send your name, your content or anything about your connected accounts.
- Meta uses this data to match you to its users and to measure and optimise ads; TikTok does the same. Meta is joint controller with us for the data its pixel collects on our website, under Meta's Controller Addendum; Meta and TikTok process the event data we send under their business terms.
- We keep the click data we store for this (click ids, IP address and browser type) for at most 90 days. You can object by emailing support@postrush.app.
The social platforms you connect (X, Meta for Facebook, Instagram and Threads, TikTok, the Mastodon server you choose, Bluesky and the server that hosts your Bluesky account, Telegram and Google (YouTube)) receive the content you publish and the requests needed to publish it. They act under their own privacy policies.
Google: if you use Continue with Google, you sign in on Google's own page, so Google knows you signed in to Postrush. Google acts under its own privacy policy.
When you view connected accounts in Postrush, your browser loads their profile pictures directly from the platform's image servers, which can see your IP address. A Telegram chat's picture is loaded from our own copy instead.
Other members of a workspace can see your name, role and which content you edited in that workspace. We may disclose data if the law requires it.
Transfers outside the EU
Cloudflare, Resend, Stripe, PostHog, Sentry, Anthropic and OpenAI are US companies (Stripe also has an EU entity). Your data is stored and sent from the EU where they offer it, but they may access it from outside the EU. Meta and TikTok may process the advertising data described above in the US or other countries outside the EU. Where that happens, the transfer is covered by the EU Standard Contractual Clauses in their data processing agreements (for Meta and TikTok, in their business terms) and, where the provider is certified, the EU–US Data Privacy Framework.
Cookies and browser storage
We use PostHog, a product analytics service hosted in the EU, to understand where visitors come from and how Postrush is used. Our own cookies keep Postrush working:
__Secure-better-auth.session_token: keeps you signed in. Expires after 24 hours.scheduler_media_preview: lets your browser show a private media file for 2 minutes.
PostHog sets its own cookies and local storage entries (their names start with ph_) so it can recognise your browser when you come back. On our website and in the app it records the pages you visit, the website and campaign tags (UTM) that brought you, what you click, and your device and browser. It does not record your screen: there are no session recordings. In usage events, page titles and the part of each web address after the "?" are removed, and the text of what you click is hidden. The data goes to PostHog through our own domain, together with your IP address, which PostHog uses to estimate your approximate location (country and city) and then discards: the IP address is not stored. After you sign in, PostHog links this data to your internal user id and workspace id, never to your name or email. When you delete your account, we ask PostHog to delete the usage data linked to your account.
The Meta and TikTok pixels use these cookies on our marketing pages (home, pricing, privacy, terms and data-deletion):
_fbc: set by us, only when you arrive from a Meta ad link, in Meta's format; it holds that ad-click id, for 90 days._fbp: a random browser id in Meta's format, set by us or by Meta's pixel, for 90 days. Meta's pixel reads both.postrush_ttclid: set by us, the TikTok ad-click id, for 90 days._ttp: TikTok's own pixel sets its own cookies, such as_ttp, to recognise your browser.
We do not ask for consent before these pixels load. If you do not want them, block them in your browser or with a content blocker, or object by emailing support@postrush.app.
Your browser's local storage remembers small layout choices, such as whether the sidebar is collapsed. It also keeps postrush_attribution: the campaign tags (UTM) of your first and last visit, the website that sent you and the first page you landed on. It keeps them for 90 days from your last visit through a tagged link (if no visit was tagged, 90 days from your first visit); after that they are no longer used, and they are removed on your next visit to our website. If you sign up within that time, we store them with your account at the first step of setting up your account and remove them from your browser once they are saved. If an affiliate's link brought you, the affiliate's tag is kept through later visits that carry no tags (for example from a search or another website), until a newer tagged link replaces it or the 90 days run out.
When you pay or manage billing you leave Postrush for a page hosted by Stripe, which sets its own cookies under its own policy.
How long we keep data
| Data | How long |
|---|---|
| Your account (name, email, password hash if you have one, the id of a connected Google account, preferences) | Until you delete your account. If you disconnect Google in Settings, its id is removed straight away. |
| Workspaces, posts, drafts, schedules, revision history and media | Until you delete them or your account. Media you remove from the library is deleted from storage once no post uses it. |
| Postrush AI chats (your messages, the answers and the cards in them) | Until you delete the chat, the workspace or your account. |
| Postrush AI usage (how much you used it each day) | 90 days. |
| Records of what was published (post ids and times on each platform) | Until you delete your account. |
| Connected-account access tokens | Until you disconnect the channel, the platform withdraws access, or you delete your account. |
| Sign-in sessions (with IP address and browser type) | A session lasts 24 hours. The record is removed when it is cleaned up, when you sign out of it, or when you delete your account. |
| Security rate-limit records (IP address or account id) | Deleted after 24 hours without activity. |
| Email delivery records | The email content is cleared as soon as the email is sent or fails. The record itself is deleted after 90 days. |
| In-app notifications | 90 days. |
| Engage comments (the commenter's public name or handle, profile picture and comment), the replies and direct messages we sent for you, your posts' captions, the Auto-DM activity and when each DM's link was first opened | 90 days after the comment's last activity. |
| Workspace invites | 90 days after the invite is accepted, cancelled or expires. |
| Subscription records (Stripe customer and subscription ids, plan, status, billing dates) | Until you delete the workspace or your account. Deleting cancels the subscription immediately and nothing is charged afterwards. Stripe keeps the customer record and any saved card, together with invoices and payment records as long as the law requires for bookkeeping (Danish law: 5 years). |
| Credit records (monthly and bought credits, and what they were spent on, including Postrush AI) | Until the workspace is deleted. Deleting your account deletes the workspaces you own; in a workspace you only joined, the records keep your internal user id, never your name or email. |
| Sign-up source (campaign tags, referring website, landing page, "How did you hear about us?" answer) and setup progress | Until you delete your account. |
| Product analytics in PostHog (usage events) | Kept by PostHog for 1 year. When you delete your account, we ask PostHog to delete the usage data linked to your account. Usage data that was never linked to an account is deleted when it is 1 year old. |
| Error reports in Sentry | Kept by Sentry for the retention period of our Sentry plan. They hold only internal ids, which no longer point to anyone once your account is deleted. |
| Ad-click data for Meta and TikTok (click ids, IP address, browser type) | Deleted once your first payment has been reported, after 90 days at most, or when you delete your account, whichever comes first. If you object, we keep a record that you objected (without any click data) until you delete your account. What Meta and TikTok keep is governed by their own policies. |
| Email suppression list (an address that bounced or marked our email as spam) | Kept so we never email that address again, even after the account is deleted. Ask us to remove it. |
| Affiliate applications and payout records (name, email address, profile links, answers, payout details) | The application email is kept in our mailbox, and the payout details and payments in our own records. We delete them when you ask, except payment records we must keep for bookkeeping and tax law (Danish law: 5 years). The email record in Postrush loses its content as soon as the email is sent, and the record itself is deleted after 90 days. |
| Launch list (email address, when you joined, the wording you agreed to) | Until you unsubscribe or ask us to delete it, and no longer than 12 months after Postrush launches. |
| Backups of our database | Up to 30 days. Deleted data disappears from backups within that window. |
Posts you published stay on the platform after you delete them in Postrush. See how to delete your data.
Security
- All traffic uses HTTPS.
- Social account access tokens are encrypted at rest with AES-256-GCM, using keys kept separate from the database, and they never leave our servers.
- Passwords are stored as hashes. Uploaded media is in private storage. It is shown only to signed-in workspace members, and handed to the platform you publish to, through short-lived links.
- Access to workspace data is checked on every request.
No system is perfectly secure. If a breach affects your personal data, we will tell you and the authorities as the law requires.
Your rights
Under the GDPR you can ask to access, correct, delete or receive a copy of your personal data, and to restrict or object to how we use it. You can change your name and email and delete your account yourself in Settings. For anything else, email support@postrush.app from the address on your account. We answer within one month.
You can also complain to the Danish Data Protection Agency (Datatilsynet) or the authority where you live.
Age limit
Postrush is for people aged 18 or over. We don't knowingly collect data from anyone younger. If you believe a child has an account, contact us and we will delete it.
Changes to this policy
We update this policy before we change how we handle personal data, for example before adding a new service provider. We change the date at the top and, for important changes, tell you by email or in the app.
Connected social accounts
When you connect an account on X, Instagram, Facebook, TikTok, Mastodon or Bluesky, you sign in on that platform (for Mastodon, on your own server) and approve what Postrush may do. We then store:
We use this access only to do what you ask:
Telegram works differently: there is no sign-in. You start a chat with Postrush's bot (@postrushapp_bot) and pick a channel or group you run, and Telegram adds the bot to it as an admin that can post. We then store the chat's id, title, @username (if it has one), type, member count and whether it has topics, a copy of its picture, and the Telegram user id of the person who connected it. The bot posts with Postrush's own bot key, so we hold no Telegram access token of yours. Telegram tells the bot about messages sent to it, some messages in the chats it was added to, and changes to its own membership. Postrush uses only the connect messages you send the bot, a chat's new title, and whether the bot was removed or lost its right to post, and stores nothing else from them. When you disconnect, the bot stays in the chat until you remove it in Telegram.
We do not read your direct message conversations; we keep only the text of the direct messages Postrush sends for you. The only data of other people we read is the comments on your own posts, and we do not use platform data for advertising. We do not sell your data, and we do not use your content or platform data to train AI models.
Postrush is not affiliated with or endorsed by X, Meta, TikTok, Mastodon, Bluesky, Google (YouTube) or Telegram. What you publish becomes subject to the platform's own terms and privacy policy.