Privacy Policy

Who we are

Preflight is a social media scheduling tool operated by ADMI ENTERPRISES s.r.o., Nové sady 988/2, 602 00 Brno, Czech Republic, company number 29581010 ("we", "us"). We are the data controller for the personal data described in this policy.

For any question about this policy or your data, write to info@preflight.social.

What Preflight does

Preflight lets you write a post once, attach a photo or a video, and publish or schedule it to the social media accounts you have connected. To do that we hold your account details, the content you create, and the access tokens the platforms issue when you connect an account.

What we collect

Account information

• Your email address and display name.
• A cryptographic hash of your password. We never store the password itself and cannot recover it.
• Session records: a session token, the IP address and browser user agent of the device you signed in from, used to keep you signed in and to rate-limit abuse.
• Where your visit came from when you signed up: the campaign tag in the address that brought you (such as utm_source or ref), the site that linked to us, and the first page you opened — nothing else. Your browser sends it with the sign-up itself, whether or not you accept statistics cookies, and nothing is stored in your browser for it. It lets us see which of our announcements bring people who sign up and pay, and it is deleted with the account.

Connected social accounts

• Your identifier, username, display name and profile picture on each platform you connect.
• The OAuth access and refresh tokens that platform issued, together with the permissions you granted. These tokens are encrypted at rest using AES-256-GCM with a key held only in our server environment, never in the database.

We request the narrowest permissions each platform offers for publishing. We do not read your existing posts, your private messages, or the list of who follows you. Comments people leave on posts you published through Preflight are read only while you have the comment inbox open, so you can answer them, and are not stored. Where a platform reports it, we do store how many followers each connected account has, once a day, so the analytics screen can show whether that number is going up — it is a total, never the people behind it. Those daily totals are kept for as long as your plan keeps figures and are deleted with the account. The profile details we store from a platform are refreshed, or deleted if no longer available, at least every 30 days.

Content you create

• Post text, links, scheduling times and per-platform options.
• Images and videos you upload, or that we fetch on your behalf from a URL you supply.
• After publishing: the identifier and public link of the resulting post on each platform, plus any error the platform returned.

API keys

If you create an API key we store its name, a non-secret prefix and a hash of the key. The key itself is shown once at creation and is never stored, so we cannot recover it for you.

Preventing misuse of the free trial

The Pro trial is once per person and once per card. To tell when a trial is being taken again under a new account, we keep fingerprints of what a second trial tends to reuse: the connected social accounts, your email address (normalised, so different spellings of the same mailbox match), the address you signed up from, a random id this browser keeps in a cookie (no fingerprinting of the browser itself), and the card used for the trial. A fingerprint is a keyed one-way hash — it can be compared with another fingerprint but not turned back into the address, account or card — and for the card it is made from the fingerprint Stripe gives us, never from the card number, which we do not receive. From these we work out a score with the reasons behind it; a high score means a trial is not offered, and the free plan and paid plans stay open. A person reviews flagged cases, and you can write to us if you think a decision was wrong. The fingerprints are kept after an account is deleted — otherwise deleting one would be the way to a new trial — and are deleted after 12 months in which they have not been seen again.

What we do not collect

• No advertising cookies. We set two, and only once you sign up, sign in or ask for a trial — never just for reading the site: one keeps you signed in, the other holds a random id of this browser, used only to keep the free trial to one per person (see above) and never shared. A third kind, for visit statistics, is set only if you accept it (see "Visit statistics, only if you accept").
• No advertising networks. For page views and load speed we use Cloudflare Web Analytics, which sets no cookies and does not fingerprint or track individuals across sites; it counts visits and performance per page.
• No payment card details — Stripe holds them. We receive only Stripe's card fingerprint, and keep a hash of it (see above).

Visit statistics, only if you accept

On the public pages (the front page, pricing, the guides and tools, and the sign-in) we ask whether we may count visits. If you reject, or do not answer, nothing is loaded from Google, no analytics cookie is set and nothing about your visit is kept in your browser. The signed-in app and the admin are never measured. (If you make an account, its first source is kept with it either way — see "Account information".)

If you accept:

• Google Analytics 4 (Google Ireland Limited; Google may process the data in the United States) sets cookies named _ga and _ga_…, valid for up to two years, and receives the pages you view, the site you came from, the campaign tag in the address if there is one, your approximate location, and your device and browser type. Advertising features and personalised advertising are switched off, and Google does not use this data for its own advertising through us. Reports keep event data for up to 14 months.
• Your browser remembers where this first visit came from, so that an account you make on a later visit gets that source rather than the later one.

You can change your mind at any time with "Cookie settings" at the bottom of the page. Rejecting costs you nothing: the service works the same.

Why we use it, and on what legal basis

• To provide the service — creating your account, storing your posts, publishing them to the platforms you chose. Legal basis: performance of a contract with you.
• To keep the service working and secure — retrying failed publications, diagnosing errors, limiting abusive traffic. Legal basis: our legitimate interest in a reliable and secure service.
• To keep the free trial to one per person — the fingerprints and score described under "Preventing misuse of the free trial". Legal basis: our legitimate interest in preventing fraud and abuse of a free offer.
• To take payment for a paid plan and keep the records that go with it. Legal basis: performance of a contract with you, and compliance with a legal obligation for the accounting and tax records.
• To rewrite or review a post when you ask the assistant to. Legal basis: performance of a contract with you — it happens only on the post you are working on, when you ask.
• To understand which pages are read and where visitors come from — only if you accept statistics cookies. Legal basis: your consent, which you can withdraw at any time.
• To know which of our announcements bring the people who sign up — the first source kept with a new account (see "Account information"). Legal basis: our legitimate interest in knowing where our customers come from. It is a campaign tag and a page, never your activity elsewhere; you can object by writing to us, and we delete it.
• To meet legal obligations where applicable. Legal basis: compliance with a legal obligation.

We do not sell your personal data, we do not share it with anyone except the processors and platforms described below, and we do not use your content or data to train machine learning models or for advertising.

YouTube API Services

Preflight uses YouTube API Services to connect your YouTube channel, upload the videos you schedule, and show you how they performed. Through those services we access and store your channel's identifier, name and profile picture; the OAuth tokens Google issues when you connect the channel; the identifier and title of each video you published through us; and that video's view, like and comment counts together with its watch time, average view duration, average percentage viewed, audience retention and traffic sources.

On your instruction we also list your playlists so you can pick or create one, add the video to it, set its thumbnail, and upload, replace or remove its subtitles. The comment inbox reads the comments on those videos while you have it open, and lets you reply, edit or delete your own replies, hide a comment, and post a first comment of your own; comment text is not stored. When you ask the assistant to review a video, we read its caption track so the review can refer to what is said in it (see "The assistant").

We do not read videos you did not publish through Preflight, and we do not access anyone else's channel. Google's handling of your data is described in the Google Privacy Policy.

You can revoke Preflight's access to your Google account data at any time via the Google security settings page. In addition to our own deletion process described below, disconnecting YouTube in Settings deletes the stored tokens and channel details immediately.

Preflight's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

LinkedIn Company Pages

When you connect a LinkedIn Company Page, we store the Page's identifier, name and public handle, your role on the Page, and the OAuth tokens LinkedIn issues. We publish the posts you schedule to that Page, and only when you or a schedule you set asks us to.

The comment inbox reads the comments on the Page's posts published through Preflight while you have it open. For each comment it shows the commenter's name and public profile handle, the comment text and when it was written, and lets you reply as the Page or delete the comment. Comment text and commenter details are not stored; names are kept in memory for up to 24 hours so the same person is not looked up again on every visit. For those posts we store aggregate figures: impressions, unique impressions, likes, comments and reshares.

We use this data only to provide these features to you. We never message LinkedIn members and never use their data for advertising, profiling or any other purpose. Disconnecting the Page in Settings deletes its tokens immediately; everything else is deleted with your account. You can also revoke Preflight's access at any time in LinkedIn's permitted services settings.

Who else processes your data

We use a small number of service providers as processors. They act on our instructions and are bound by contract.

• Railway (United States, servers in the EU) — application hosting and the PostgreSQL database.
• Google (Google Ireland Limited; the United States) — Google Analytics 4, only for visitors who accept statistics cookies.
• Cloudflare (United States, storage in the EU) — R2 object storage for the images and videos you upload, and the network the site is served through.
• Stripe (Ireland and United States) — subscriptions and payment. Stripe is the seller of record for a paid plan and holds your billing details; we never receive your card number.
• Resend (United States) — the email we send you: confirming your address, resetting a password, inviting you to a workspace.
• Anthropic (United States) — only when you ask the assistant to rewrite or review a post. See "The assistant" below.
• Sentry (servers in the EU) — reports of software faults, so we can fix them. Sent without the request body, headers, cookies or any account identifier; in practice an error message and the place in our code it came from.
• GitHub (United States) — runs the nightly database backup, which is encrypted before it leaves and stored in the EU. See "How long we keep it".

Separately, when you publish a post we transmit that post — its text and media — to the social platform you selected (for example YouTube, TikTok, Instagram, Facebook, Threads, Bluesky, Mastodon, Pinterest, Telegram, Discord or LinkedIn). Those platforms are independent controllers of what happens on their own services, and their own privacy policies apply to the published content.

Some of these providers are established outside the European Economic Area. Where personal data is transferred outside the EEA, that transfer is covered by the European Commission's Standard Contractual Clauses or an adequacy decision. Your uploaded files, the database and its backups are stored in the EU.

If you use Preflight to publish on behalf of your own clients, you are the controller of their data and we act as your processor. Write to info@preflight.social for a data processing agreement and an up-to-date list of the sub-processors above.

The assistant

Preflight can rewrite a caption for a particular network, or look at a published post and suggest what to change. Both happen only when you ask for them, on the post you are working on.

When you do, the text of that post — and, for a review, the figures it has collected and, for a YouTube video, the text of its caption track — is sent to Anthropic, which returns the suggestion. The caption track is read for that review only and is not stored; the review we keep may quote a few words from it. Your email address, your account and your connected channels are not sent. Anthropic does not use what is sent through its API to train its models, and we do not use it to train anything either. If you would rather nothing left our servers, do not use these two features; everything else in Preflight works without them.

How long we keep it

• Account and connected accounts — until you delete the account or disconnect the platform. Disconnecting deletes the stored tokens immediately.
• Uploaded images and video — the file itself is deleted from our storage after every selected platform has finished with it, and how long after depends on your plan: 7 days on Free, 14 on Starter, 30 on Pro, 90 on Studio. The published post continues to exist on the platform. We keep a thumbnail and basic details so your history still makes sense.
• Posts and publication results — until you delete them or close your account.
• Figures collected from the platforms — how far back they go depends on your plan: 30 days on Free, 90 on Starter, a year on Pro, two years on Studio.
• Trial-misuse fingerprints — 12 months after they were last seen, including after the account they came from is deleted.
• Server logs — a rolling window of 30 days, used only for diagnosing faults and investigating abuse.
• Backups — the database is backed up nightly, encrypted, and each backup is deleted after 30 days. This is the one place where deleted data lingers: when you delete something, or close your account, it goes from the live service at once, and from the backups as those expire. We do not restore a backup to recover data somebody asked us to delete.

Security

• All traffic is encrypted in transit with TLS.
• Social media tokens are encrypted at rest and never sent to your browser.
• Passwords are stored only as salted hashes.
• Uploaded media is stored in a private bucket. Where a platform needs to fetch a file itself, we issue a short-lived signed link rather than making the file public.
• Every request is scoped to your workspace before any data is read or written.

No system is perfectly secure. If a breach affects your personal data and presents a risk to you, we will notify you and the supervisory authority as required by law.

Your rights

Under the GDPR you have the right to:

• access the personal data we hold about you;
• have inaccurate data corrected;
• have your data erased;
• restrict or object to how we process it;
• receive your data in a portable, machine-readable format;
• withdraw consent where processing is based on consent.

To exercise any of these, email info@preflight.social. We respond within one month.

You can also revoke Preflight's access at any time from each platform's own settings — for example the Google security settings page for YouTube, Settings → Apps and websites (Business integrations) on Facebook and Instagram, or Settings and privacy → Security → Apps on TikTok. Doing so stops us publishing on your behalf immediately.

If you believe we have handled your data improperly you may complain to your local supervisory authority. In the Czech Republic this is the Office for Personal Data Protection (Úřad pro ochranu osobních údajů), uoou.cz.

Deleting your account

You can delete your account from Settings, or by emailing info@preflight.social. Either way we delete your account, your connected account tokens (including data obtained from platform APIs such as YouTube API Services), your posts and your stored media. Content already published to a social platform is not affected — you control that through the platform itself.

Deletion takes effect in the live service straight away. The nightly backups described above still hold a copy until each one expires, within 30 days, and a backup is never used to bring back data somebody asked us to delete.

Children

Preflight is not intended for anyone under 16, and we do not knowingly collect data from children.

Changes to this policy

If we change this policy we will update the date at the top of this page. Material changes affecting how we use your data will be notified to you by email before they take effect.