Privacy Policy

Last updated: October 15, 2026

1. What We Collect

We collect the minimum data needed to provide the service:

2. How We Use Your Data

We only send marketing emails to users who have explicitly opted in by checking the consent box during signup. You can unsubscribe at any time by emailing us.

3. Third-Party Services

We use the following third-party services:

Each service has its own privacy policy. Some providers may process data outside the EU/EEA using their GDPR transfer safeguards. We do not sell your data to any third party.

4. Data Retention

Your files are stored until you delete them, they expire under an auto-delete setting you configured, or your account is terminated. A first upload made before email verification is provisional for up to 24 hours unless verification promotes it to normal account retention. Account data is retained for as long as your account is active. After account deletion, we target removal from active systems within 30 days where reasonably possible.

For ChatGPT connections, authorization codes expire after five minutes, access tokens after one hour, and rotating refresh tokens after 30 days. FilePost stores hashes of these credentials rather than their raw values. Revoked access-token records are eligible for pruning after 90 days; cleanup runs when a new OAuth client is registered, so records may remain longer. Expired authorization-code and token rows are also pruned during that cleanup. OAuth client registration details, including client name and redirect URLs, do not currently have automatic deletion. To request help revoking a FilePost connection or removing its registration, email support@filepost.dev; do not send access or refresh tokens by email.

Encrypted database backups are retained separately for recovery and automatic archives age out within 180 days. A deleted record may remain in a protected backup until that backup rotates out. Support, security, billing, and takedown records may be retained for longer when needed to resolve disputes, prevent abuse, comply with legal obligations, or protect the service.

5. Your Rights

You can:

6. Security

All data is transmitted over HTTPS. Uploaded files are primarily stored in Backblaze B2 and delivered through Cloudflare; file URLs are public and must not be used for confidential material. Database backup archives are encrypted before leaving the application server and copied to two storage providers. API keys are generated using cryptographically secure methods. See Security and Data Handling for the current controls and limitations.

7. Cookies and Local Storage

The API uses API key authentication and does not require browser cookies. The dashboard uses cookies for login sessions: fp_session is an HttpOnly signed session cookie, and fp_li is a non-sensitive login indicator used by the navigation UI. We also use browser localStorage to remember basic dashboard display information such as email, name, and avatar URL after sign-in. The ChatGPT integration uses OAuth authorization codes with PKCE and scoped bearer tokens rather than FilePost API keys. The consent page lists the requested file and account operations. When you use the integration, prompts, files you choose to upload, and tool results may be processed by OpenAI/ChatGPT; FilePost file links are public to anyone who has the link.

Google Analytics and PostHog are optional analytics tools. They only load after you accept analytics cookies in the cookie banner. Your analytics choice is stored in localStorage as fp_analytics_consent, and you can change it from the Cookie Settings link in the footer.

To attribute a sign-up to the page or campaign link that brought you here, FilePost reads the campaign tags in the link (utm_ source, medium, campaign and content), the first FilePost page you opened and the referring site, and sends them to us when you create an account, but only if you have accepted analytics. If you accept, this attribution (fp_first_touch) is stored as a tab-only sessionStorage copy and a 7-day localStorage copy, both deleted when you reject or withdraw consent. Without consent it is not read, stored or sent. It contains no personal identifier.

Optional in-app surveys: if you choose to answer a survey in your dashboard, we store your answers with your account, plan and usage segment to improve FilePost. Survey answers are never sent to analytics tools. Written answers are deleted after 18 months.

We count campaign-tagged page requests in aggregate without storing visitor identifiers, IP addresses, or raw browser details in those counters. These counts are separate from optional analytics cookies.

Google Sign-In may load cookies or similar technologies from Google when you use that sign-in option.

8. Content Reports and Legal Requests

If content is reported as illegal, abusive, harmful, or infringing, we may review the report, remove or disable access to files, suspend accounts or API keys, preserve relevant records, and cooperate with valid legal requests or law enforcement where required or appropriate.

9. Changes

We may update this policy. Changes will be posted on this page with an updated date.

10. Contact

FilePost is based in Sweden. Privacy questions? Email support@filepost.dev.