Legal · Last updated 13 November 2026
Privacy Policy
What personal data FlareLog collects, why, where it goes and how long we keep it. We wrote it from what the product actually does.
1. Who we are
FlareLog (flarelog.dev) is operated by Remote Skills Ltd, a company registered in England and Wales, with its registered office at 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. For your account, billing and website data, Remote Skills Ltd is the controller under the UK GDPR and the EU GDPR.
For the logs and traces you send to FlareLog from your own apps, you are the controller and we are your processor. Our Data Processing Agreement covers that data.
Questions or requests about your data: hello@flarelog.dev.
2. What we collect
Your account
- Email address, name and sign-in provider ID from Google or GitHub, through Firebase Authentication.
- Your projects, API key names and settings. API keys are stored hashed.
- Alert settings, including email addresses and the Slack, Discord or webhook URLs you add.
- Usage counts, such as how many logs you sent this month.
Billing
- If you upgrade, Stripe processes your payment. We store your Stripe customer and subscription IDs and your plan. We never see or store your card details.
Logs and traces you send
- Log messages, errors, traces and metadata your apps send through the SDK or OpenTelemetry. This can include personal data about your own users if your code logs it. You control what you send; see section 10.
Cost calculator
- If you email yourself an estimate, we keep your email address, the estimate and a one-way hash of your IP address for 30 days, to send the email and stop abuse.
Website visits
- Our hosting provider, Cloudflare, processes your IP address and request details to serve and protect the site. Our own short-lived operational logs can include request details.
- We don't use advertising trackers or third-party analytics. Fonts and icons are served from our own domain.
3. Why we use it, and our legal basis
- To provide FlareLog (accounts, storing and searching logs, alerts, billing): performance of our contract with you.
- To keep FlareLog secure and prevent abuse (rate limits, fraud checks, debugging): our legitimate interests.
- To send product emails, such as a welcome email and a reminder if you haven't finished setup: our legitimate interests. Every product email has an unsubscribe link, or you can email hello@flarelog.dev. Alert and account emails are part of the service.
- To keep billing and tax records: legal obligation.
We don't sell your data, and we don't use your logs to train AI models.
4. AI features
FlareLog can summarise your logs with AI. To do that, we send log content to Cloudflare Workers AI, which runs the model on Cloudflare's own infrastructure. This only happens when you ask for an explanation of an error. Cloudflare doesn't keep the log content after it returns the summary, and doesn't use it to train models. We save the summary with your project so you don't have to ask again. If you connect an AI assistant (such as Claude or Cursor) to FlareLog over MCP, your assistant reads your logs with your API key, and that assistant's provider handles the data under its own terms.
When you resolve an issue, you or your AI assistant can add a note on what fixed it. We store the note with the issue. If the error stays away for 7 days, we send the note and the error message to Cloudflare Workers AI, on the same terms as above, to draft a short lesson. A lesson is only served to AI assistants after you approve it. Notes and lessons are deleted when you delete the project's logs or the project.
To check that a fix held, FlareLog counts the requests each route of your app receives, per day, from the request logs your platform sends (for example POST /api/checkout, with IDs, numbers, emails and tokens removed from the path). Only the counts are kept, never the requests themselves, and they are deleted after 35 days, or earlier when you delete the project's logs or the project.
5. Vercel, Cloudflare and Supabase integrations
If you install FlareLog from the Vercel Marketplace, Vercel gives us an access token for your Vercel account or team, limited to the permissions you approve there: reading the list of projects you share with FlareLog, and creating and managing log drains. We use it once, while you install, to add a log drain that sends those projects' logs to FlareLog. We don't store the token.
The drain sends us log entries from your Vercel functions, edge middleware and builds. We keep entries that contain a log message and requests that failed, and drop routine request logs. We don't store the visitor IP addresses, user agents, referrers or TLS fingerprints that Vercel includes. What we keep is stored and deleted like any other logs you send us (see sections 7 and 8). To stop, remove FlareLog from your Vercel integrations and Vercel stops sending logs; Disconnect in your project's settings shows how and deletes the drain's API key. You can delete logs we already have from your project's settings.
If you connect Cloudflare, Cloudflare gives us an access token for the accounts you choose on its consent screen, limited to the permissions you approve there: seeing those accounts and their Workers, reading and updating Workers settings, and managing observability destinations. We use it while you connect, to add a logs destination that sends to FlareLog and to turn on log export for the Workers you pick. We don't store the token, and we revoke it when the connection is done.
Cloudflare then sends us your Workers' log output, exceptions and invocation details. We keep log lines, exceptions and failed requests, and drop the routine log Cloudflare writes for each successful request. We don't store the visitor IP addresses, locations, request headers or TLS details that Cloudflare includes. What we keep is stored and deleted like any other logs you send us (see sections 7 and 8). To stop, use Disconnect in your project's settings: you sign in to Cloudflare again, and we use that access only to take our destination off your Workers and delete it, then delete its API key and revoke the access. You can also remove the destination yourself under Observability in your Cloudflare dashboard.
If you connect Supabase, Supabase gives us access tokens for the organization you choose on its consent screen, limited to the permissions you approve there: seeing that organization's projects and managing their log drains. We use them while you connect, to add a log drain that sends the projects you pick to FlareLog. We don't store the tokens, and we revoke our access when the connection is done.
Supabase then sends us those projects' logs. We keep database errors and warnings, Edge Function output, failed requests and auth errors, and drop routine logs. We don't store the visitor IP addresses, locations, request headers, user agents or email addresses that Supabase includes. What we keep is stored and deleted like any other logs you send us (see sections 7 and 8). To stop, use Disconnect in your project's settings: you sign in to Supabase again, and we use that access only to delete the FlareLog drains you pick and their API key, then revoke the access. You can also remove the drain yourself under Project Settings → Log Drains in Supabase. Supabase bills log drains separately.
6. Who we share it with
We use a small number of providers to run FlareLog. They are listed with their purpose and location on our Subprocessors page. We also send data where you tell us to, such as your Slack, Discord or webhook alert destinations. We disclose data to authorities only when the law requires it.
7. International transfers
The logs and traces you send are stored in the European Union (Frankfurt, Germany). Some of our providers are United States companies or process other data, such as account and billing data, in the United States. These transfers are covered by the UK Extension to the EU-US Data Privacy Framework where the provider is certified, or otherwise by the UK International Data Transfer Addendum and the EU Standard Contractual Clauses.
8. How long we keep it
- Logs and traces: 7 days on Free, 90 days on Pro and Scale. Deleting a project, or its logs, deletes them sooner.
- Account data: until you delete your account. You can do this yourself from the billing page; it deletes your projects, logs and sign-in, and cancels your subscription.
- Cost calculator saves: 30 days.
- Billing records: Stripe keeps invoices and payment records for as long as tax law requires.
9. Your rights
You can ask to access, correct, delete or export your personal data, to restrict or object to how we use it, and to withdraw consent where we rely on it. Email hello@flarelog.dev and we'll reply within one month. You can delete your account and all its data yourself at any time.
You can complain to the UK Information Commissioner's Office (ico.org.uk), or, if you're in the EU, to your local data protection authority. We'd appreciate the chance to fix things first.
10. If you send us your users' data
You decide what your apps log. Avoid logging passwords, payment details or other sensitive data. Our SDK leaves out client IP addresses unless you turn that on. Your own privacy policy should mention that you use FlareLog for error and log monitoring.
11. Cookies
We set one cookie, __session, to keep you signed in to the dashboard. It's strictly necessary, so we don't ask for consent. Signing in with Google or GitHub loads Firebase scripts from Google on the sign-in page.
12. Security
Data is encrypted in transit with TLS. Our storage providers encrypt data at rest. API keys are stored hashed, webhook deliveries are signed, and access to production systems is limited to the people who run FlareLog.
13. Children
FlareLog is a developer tool and isn't meant for anyone under 16.
14. Changes
If we change this policy, we'll update the date at the top. For significant changes we'll email account holders before they take effect.
Remote Skills Ltd · Registered in England and Wales · Registered office: 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom