Privacy policy

Last updated 2 October 2026

PaperFlight (“the console”, “we”), at paperflight.app, is an AI marketing service for founders and small businesses. It helps the people who use it write, review and publish social posts and short videos, and see how the posts did. This page says what the console stores, why, who can see it, and how it is protected. Contact: the contact page.

What we store, and why

  • Your account — your email address and, if you set one, a salted password hash, so you can sign in. Sign-ins are recorded (when, from which account) in the console’s activity ledger.
  • Your workspace — the brand profile and guidelines you write, the posts and drafts made in it, notes saved to its memory, the agents you set up, your conversations with the Assistant, and the activity ledger of what was done. A workspace is visible only to its members.
  • Connected accounts — when you connect a social account (through PostForMe), a YouTube channel or Google Analytics, we keep only what is needed to act on your behalf: account identifiers, the account’s email address, and access tokens or keys, stored encrypted. We never store your passwords for those services.
  • Post performance — the numbers the social platforms report for your posts (views, likes, comments, shares) and, if you connect Google Analytics, the visits your posts sent to your site.
  • Run logs — when an agent or the Assistant works for you, the console keeps a log of the steps it took, with a short excerpt of what each step read or returned, so you can audit what was done. If a step read an email, an excerpt of that email is in the log.
  • Model keys — API keys for the AI providers you or we add, stored encrypted and used only to run the writing and image tools you ask for.
  • Contact and account requests — what you type into the contact form or the sign-up request (name, email, company, site, message), kept until we have replied and delete it.

Google user data

Nothing from Google is accessed unless you choose to connect a Google account. When you do, the console asks only for the scopes the feature you are turning on needs, and uses the data only for that feature. Google Analytics and YouTube are separate integrations: connecting one does not grant the others. Google’s own handling of your data is described in the Google Privacy Policy.

What is accessed

  • Your Google account email address (scopes openid, email) — stored so the console can show which Google account is connected.
  • Google Analytics, read-only (scope analytics.readonly) — the list of Analytics properties your account can read, so you can pick one; then reports for that property: sessions, engaged sessions, key events, page views, users, sources and landing pages. Nothing is written to your Analytics property.

YouTube

PaperFlight uses the YouTube API Services to publish your videos to a YouTube channel you connect. By connecting a channel you agree to be bound by the YouTube Terms of Service, and Google’s handling of the data is covered by the Google Privacy Policy. A channel connected through PostForMe instead is handled under PostForMe’s own authorization and terms.

  • What we access (scopes youtube.upload, youtube.readonly, yt-analytics.readonly) — the channel’s id and name, so you can see which channel is connected; the ability to upload a video with its title, description and visibility; for the videos PaperFlight uploaded, their public statistics (views, likes, comments); and, through the YouTube Analytics API, those videos’ and the channel’s performance reports (watch time, average view duration, audience retention, subscribers gained or lost, traffic sources), which are aggregated and never identify a viewer. We do not read revenue or monetary reports, your subscribers’ identities, your comments or your watch history, and we never delete or edit anything on your channel.
  • When a video is uploaded — only when you approve it, unless you explicitly choose otherwise. By default a post with YouTube ticked waits on Review until you press Approve, in every mode. Automatic uploads happen only if you yourself tick the “Auto-publish” box for that YouTube channel on Channels — a separate, per-channel setting that is off when a channel is connected and is never switched on for you, by us or by any automation — and only while your workspace runs “Autonomous”. Unticking the box, switching the workspace out of Autonomous, or pressing Stop everything ends automatic uploads at once; nothing already waiting is uploaded until you approve it.
  • What we store — the access token (encrypted), the channel id and name, for each video we uploaded its id, link, statistics and analytics figures, kept with the post it belongs to, and the channel’s analytics totals for the periods shown.
  • How long, and deletion — statistics and analytics figures are refreshed from YouTube at least every 30 days and deleted if they cannot be refreshed. When you disconnect the channel, or revoke access at Google, the token is deleted at once and the other YouTube data we stored is deleted within 7 days. The videos stay on your channel; only you can remove them there.

How it is used

  • Analytics numbers are used only to show, on your Performance and Your site pages, what your posts brought to your website, and to let the console recommend where to post next.
  • YouTube data is used only to upload the videos you approved to your channel, and to show you how they and your channel did — and to let the console recommend what to post next.
  • Google user data is used only to provide and improve these user-facing features. It is never used for advertising, never sold, never given to data brokers or resellers, and never used to build profiles of you.
  • Google Workspace APIs are not used to develop, improve, or train non-personalized AI and/or ML models. The AI models the console uses are the providers’ models as they are; your data is sent to them only to produce the specific reply, draft or report you asked for and is not used to train them.

Who receives it

  • The people in your workspace — a draft, reply or report made from Google data is visible to the members of the workspace it was made in, and to no one else.
  • The AI provider configured for your workspace (OpenAI, Anthropic or Google, whichever key is set) — when an agent or the Assistant works on your Analytics numbers, that content is sent to the provider to produce the result you asked for, under the provider’s API terms.
  • Our hosting providers — Cloudflare (application, encrypted tokens, files) and Neon (database) store the data on our behalf and do not use it.

We do not transfer or disclose Google user data to anyone else, and never for a purpose other than the ones above — except where the law requires it, or to investigate abuse or a security problem.

The console’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How long it is kept

  • Access tokens are kept, encrypted, until you disconnect the account or the workspace is deleted; disconnecting deletes the token at once and revokes the console’s access at Google.
  • Analytics numbers are kept alongside the posts they belong to, for as long as those posts are in your workspace. A site overview is held in memory for ten minutes and not stored.

You can disconnect at any time inside the console (Brand › Channels for YouTube, Settings › Analytics for Google Analytics). You can also revoke PaperFlight’s access to YouTube and Google Analytics from Google’s security settings at security.google.com/settings/security/permissions; we then delete the data as described above.

How we protect it

  • All traffic to and from the console, and between the console and Google, PostForMe, the AI providers and the database, is encrypted in transit (TLS).
  • Google refresh tokens, Analytics keys, model keys and platform secrets are encrypted at rest with a key held outside the database. Passwords are stored only as salted hashes.
  • Access is limited to the members of a workspace; every request is authenticated, and any account can be suspended at once. Agents get only the tools you grant them, and outward actions can be held for your approval.
  • Every outward action and every sign-in is recorded in an append-only ledger.

Who processes the data

The console runs on Cloudflare (application and file storage) and Neon (database). Publishing goes through PostForMe, or directly to YouTube and LinkedIn for channels you connect that way. Writing and image generation go to the AI provider whose key is configured for you (for example OpenAI, Anthropic or Google), and only the text and images you ask it to work on are sent. Each of these providers processes data under its own terms.

Analytics on this website

The public pages of this website (the landing page, About, Contact, Privacy, Terms and the sign-in page) use two counters: Google Analytics, which sets Google’s analytics cookies and sends page views to Google under Google’s own privacy terms, and Umami, a self-hosted, cookie-free page counter. Nothing behind the sign-in — the console and your workspace — is measured either way.

Retention

Your workspace data stays until you delete it or the workspace is deleted. Rendered graphics, videos and uploads are kept while a post or draft points at them and deleted with it. The activity ledger is append-only and may be pruned after a retention period. Google and YouTube data are kept as described in the section above.

Your choices

  • Edit or delete your brand, drafts, notes, agents, runs and conversations yourself, at any time.
  • Disconnect any connected account inside the console.
  • Ask us to delete your account and workspace from the contact page; deletion removes every row the workspace owns, including tokens, logs, Google and YouTube data.

Changes

If this page changes, the date above changes with it. If we change how the console accesses or uses Google or YouTube data, signed-in users are told in the console before the change takes effect.