Last updated October 25, 2026.
Who we are
Flared (“Flared”, “we”, “us”) operates the hosted service at flared.page, the short-link domain flared.link, and the page domain flared.site. This policy explains what personal information the hosted service processes and why. For privacy questions and requests, email support@flared.page.
Self-hosted installations run in their owner’s Cloudflare account. The installation owner controls that data and is responsible for the privacy information they give their own users and visitors. Flared receives no telemetry and has no administrative access to self-hosted installations.
This website
The website has no advertising trackers, third-party analytics scripts, or nonessential cookies. Fonts and logos are served from our own site. Cloudflare, our hosting provider, processes technical request information such as IP address and browser type to deliver and protect the site. Links to GitHub and other services lead to sites with their own privacy policies.
Our own measurement
We measure how people find and use Flared with our own code in our own Cloudflare account. No third party receives these records. For each page and API request to flared.page and api.flared.page, we record the address requested, the referring site without its query, any campaign (UTM) parameters, the browser and operating system names with their major versions, the device type, the approximate location that Cloudflare derives from the network address (country, region, city, postal code, and time zone), the network operator, and the preferred language. A short script on our pages also reports the window size class, the light or dark color scheme, and clicks on main buttons.
We do not store your IP address or full user agent in these records, and we set no cookie for them. To count visitors, we combine the network address, the user agent, and a random value that changes every day into a one-way code. We delete each day’s random value after the day ends, so visits on different days cannot be connected.
When you are signed in, the records also carry your account and workspace IDs, your role, and the plan. We also record account events: when a sign-in email is sent, when you sign up, when you create a link and through which channel, when you connect an app and which tools it calls, when a workspace reaches a plan limit, and checkout, payment, refund, cancellation, and billing interval changes with their amounts. When you sign up, we keep the referring site, campaign, and first page of your first visit on the same day with your account, if that visit was recorded.
When your account is deleted, we remove your account ID from these records within a day.
Your account
To sign in or create an account, you give us your email address. We verify it with a one-time code or a sign-in link sent from no-reply@flared.page. Codes and link tokens are stored only in hashed form and expire after five minutes.
A session cookie keeps you signed in for up to seven days. We do not store your IP address or browser user agent with your session. To limit abuse of sign-in emails, we keep keyed hashes of your email address and network address for 48 hours to enforce sending limits.
We process the links you create, their destinations, your domain settings, and your usage, so that we can provide the service.
Links, domains, analytics, API tokens, connected apps, and the plan belong to a workspace. You can own several workspaces, each with a name you choose. A workspace has one owner and can have members. The owner manages its plan, domains, members, and deletion, and receives its billing, usage, and suspension emails, which name the workspace. Members create and manage its links and see its analytics.
To add a member, the owner enters their email address. We send one invite email from no-reply@flared.page and keep the address with a hashed invite token until the invite is accepted, cancelled, or expired after seven days. People in a workspace see each other’s email addresses and roles. We record who invited, joined, left, removed a member, or became the owner, and when, without email addresses, and keep this record for 90 days or until the workspace is deleted. When a member leaves or is removed, their API tokens and connected apps for that workspace end; their account and other workspaces stay.
When you connect an app, such as an AI assistant through our MCP server or Zapier, we store the app’s name and web address as the app declares them, the permissions you approved, and the time of each access token we issue. Access and refresh tokens are stored only in hashed form. To limit abuse of app registration, we keep a keyed hash of the network address that registers an app for 24 hours. The app receives the link data that it requests with your approval; its own privacy policy governs what it does with that data. An app works only in the workspace you choose when you approve it. You can remove an app at any time under Connections in that workspace.
The workspace owner can add webhook endpoints under Settings, Webhooks. When a link is created, changed, turned off or on, or reaches a click count, we send the link’s data, including its destination, to each endpoint URL the owner set. The receiver’s own privacy policy governs what it does with that data. We keep the events and their delivery results for 30 days.
The workspace owner can connect one Slack workspace under Integrations, Slack. We store the Slack workspace ID and name, the user ID of the Flared app in that Slack workspace, its access token, encrypted with AES-256-GCM, who connected it and when, the channels the owner chose, and the day, hour, and time zone of each weekly summary. When a link alert, a weekly summary, or an automation post is due, we send a message to the Slack channel the owner chose. A message contains the short link and the link’s title, the destination of a new link, the old and the new value of each changed field of a changed link, for a weekly summary, the workspace’s total clicks of the week, the change from the week before, and the short links, titles, and clicks of its top five links, and for an automation, its name, its trigger, and the actions that ran. Slack’s own privacy policy governs these messages. We keep the post results for 30 days. When the owner disconnects Slack or deletes the workspace, we delete the token and the channel rules, and we ask Slack to revoke the token when no other Flared workspace uses the same Slack workspace.
The workspace owner can add Microsoft Teams channels under Integrations, Microsoft Teams. For each channel rule, we store the Teams workflow link the owner pasted, encrypted with AES-256-GCM, the rule name, its events, and the day, hour, and time zone of a weekly summary. When a link alert, a weekly summary, or an automation post is due, we send a message to that workflow link, which Microsoft runs and posts in the channel. A message contains the workspace name, the short link and the link’s title, the destination of a new link, the old and the new value of each changed field of a changed link, for a weekly summary, the workspace’s total clicks of the week, the change from the week before, and the short links, titles, and clicks of its top five links, and for an automation, its name, its trigger, and the actions that ran. Microsoft’s own privacy terms govern these messages. We keep the post results for 30 days. When the owner removes a rule or deletes the workspace, we delete its workflow link; the workflow stays in Teams until someone deletes it there.
Anyone in a workspace can connect Zapier, which works as a connected app. When a Zap starts with a Flared trigger, we store the Zapier address that receives the events, the event, the click interval of a milestone trigger, who subscribed, and when. When the event happens, we send the link’s data, including its destination, to that address. Zapier’s own privacy policy governs what it does with that data. We delete a subscription when Zapier ends it, when Zapier is removed under Connections, or when the person who subscribed leaves or is removed from the workspace, and about 14 days after Zapier last renewed it.
The Flared browser extension works as a connected app. It keeps its access and refresh tokens in the browser’s extension storage on that device. It sends us the address of each page or link that you choose to shorten, and nothing else: it does not read the pages you visit and has no analytics. We send no data to the browser makers or to the Chrome Web Store. Sign out in the extension, remove it under Connections, or remove it from the browser to end its access.
The workspace owner can connect Google Analytics 4, Amplitude, Mixpanel, or PostHog under Integrations to send each counted click of the workspace’s links there. For each connection, we store the tool, its settings (such as the data region and the Google Analytics Measurement ID), its key, encrypted with AES-256-GCM, who connected it and when, and the number of clicks sent and failed each month. For each click, we send the link ID, the short URL, its campaign (UTM) parameters, the time, the country, the device type, the browser and operating system family, the referring hostname, the visitor’s full user agent, and a visitor ID. We pass the user agent on and never store it, and we never send the IP address or the destination. While a workspace sends clicks to a tool, its short links set a first-party cookie, flared_vid, on the short-link domain: a random value that lasts one year. We mix it with the workspace before the visitor ID leaves our servers, so two workspaces never get the same ID for one visitor, and we store neither the cookie value nor the visitor ID. A browser that sends Global Privacy Control gets no cookie. The tool’s own privacy policy governs what it does with these events. The workspace owner confirms that they are responsible for any notice or consent that the law asks for, including for the cookie. When the owner disconnects a tool or deletes the workspace, we delete its key.
A link can have a password. We store a keyed hash of it, never the password itself. When a visitor enters a link password, we count the tries for that link and the visitor’s IP address for one minute to limit them, and we do not store the IP address.
A link can have a link card: a title, a description, and an image that apps such as Slack and LinkedIn show when someone shares the link. We store them with the link. Anyone can see the card and its image at the short link’s address while the link is on. We delete an image when it is replaced or removed, and every image of a workspace when the workspace is deleted.
A workspace can publish link pages at its address on flared.site or on its own domain. We store the page’s address, title, bio, theme, blocks, and avatar and background images, and anyone can see a page while it is on. A page sets no cookies and runs no scripts. An embed loads its provider’s player, such as YouTube or Calendly, and that provider’s privacy policy governs it. We count page views with the same aggregate fields as clicks: the day, the country, the device category, the browser and operating system family, and the referring hostname. We do not store IP addresses or user agents for them. When someone saves a page, and again each day, we send the destinations of its buttons and payment cards to Google Web Risk to check them against Google’s lists of unsafe sites. We send no other data with them. Old page addresses stay with the workspace, also after the page or the workspace is deleted, so that nobody else can take them.
The workspace owner can create automations, and people in the workspace apply them to links. When an automation runs, it can change a link’s destination, turn the link off, send the link’s data to a webhook endpoint the owner chose, post a message in a Slack or Microsoft Teams channel the owner chose, or email the workspace owner. The email contains the automation name, the workspace name, and the short URL or the number of links. When an automation checks a link’s destination, we request that page from our servers about every six hours with a Flared user agent and keep the time and result of the last check. We keep a record of each run, with the automation name, the link, and the result, for 90 days.
After you sign up, we ask up to four optional questions: your role, personal or work use, team size for work use, and where you heard about Flared. We use the answers to order your setup steps and to understand who uses Flared. You can skip them. They are deleted with your account.
Payments
Polar handles checkout and payments as merchant of record under its own privacy policy. We keep only the subscription and billing references needed to apply your plan. We never receive or store your card details.
What click analytics records
Click analytics records aggregate click totals and daily breakdowns by country, device category, browser family (such as Chrome or Safari), operating system family (such as iOS or Windows), and referring hostname where available. It does not store raw IP addresses, full user-agent strings, browser or operating system versions, or complete referrer URLs in product analytics.
Clicks are not unique people. Bot filtering is best effort, test traffic is labeled, and missing or delayed analytics is reported. Analytics uses no visitor cookies or cross-site identifiers. The one exception is analytics forwarding: while a workspace sends its clicks to an analytics tool, its short links set the flared_vid cookie described above, unless the browser sends Global Privacy Control. We do not use that cookie for click analytics. Infrastructure security logs are separate from product analytics.
Service providers and transfers
Cloudflare provides hosting, the database, and email delivery. Account data is stored in a Cloudflare D1 database located in the Asia-Pacific region and is served through Cloudflare’s global network, so it can be processed in countries other than yours. Polar processes payment data. Google Web Risk checks the destinations of link page buttons and payment cards.
We do not sell personal information, and we do not share it for advertising. We disclose information to others only when a provider needs it to run the service, when you send it somewhere, such as to a webhook endpoint, a Slack or Microsoft Teams channel, Zapier, or an analytics tool, or when the law requires it.
Legal bases
Where laws such as the EU General Data Protection Regulation apply, we process account and service data to provide the service you ask for, sign-in limits and security logs for our legitimate interest in protecting the service and its users, our own measurement for our legitimate interest in understanding how people find and use Flared, and billing records to meet legal obligations.
Security and operator access
The service uses HTTPS, managed encryption at rest, tenant isolation, and restricted operator access. Authorized operators can technically access hosted data for support, security, and operations. Hosted data is not end-to-end encrypted. Every operator view of account details and every abuse action is recorded in an audit log that we keep for 90 days.
A public short link reveals its destination when followed. A link password asks for the password before the redirect, but anyone who knows the destination can still open it. Do not use a short URL as access control for confidential content.
Retention and deletion
Sign-in codes and links expire after five minutes, sessions after seven days, and sign-in limit records after 48 hours. Connected-app access tokens expire after one hour and refresh tokens after 30 days; removing an app deletes them at once. An app that nobody approves is deleted a week after it registers. Operational logs are kept for at most seven days. Analytics retention is 30 days on Free and 365 days on Plus. Webhook events and their delivery results, including Slack and Teams posts and Zapier deliveries, are kept for 30 days, and automation run records for 90 days. The user agent and the visitor cookie value we send to an analytics tool wait only in our delivery queue until the tool accepts the click; we do not save them anywhere else. A click that waits more than a day is not sent. Exports are built in your browser or the CLI, so Flared keeps no copy of an export file.
In Settings, after you confirm your sign-in, you can delete one workspace, or your account with every workspace you own. The short links of a deleted workspace stop within a minute, and we delete its links, link pages and their images, domains, analytics, automations, Slack connection, Teams channel rules, analytics tool connections, API tokens, and connected apps, usually within an hour. Deleting your account also deletes your account record and removes you from workspaces that others own. We email you when the deletion starts and when it is complete. Minimal domain-and-slug reservations remain permanently so an old short address cannot be reassigned. These reservations contain no account identity or destination. A deletion record with the workspace ID and dates, but no email address or workspace name, stays for 90 days so that a database restore cannot bring the workspace back. Polar keeps its own payment records as merchant of record.
When you report abuse or ask for a review, we keep the short link or page address, your description, and the email address you give. We keep a keyed hash of your network address for at most two days to limit reports. We delete your email address 90 days after we close the report, and the report itself 365 days after we close it.
Cloudflare’s recovery history can retain deleted database data for up to 30 days.
Your rights and requests
Depending on where you live, you may have the right to access, correct, delete, or export your personal information, and to object to or restrict its processing. Email support@flared.page from the email address on your account. We reply within 30 days and may ask you to confirm the request from that address.
You may also complain to the data protection authority where you live.
Children and changes
Flared is not directed to children under 16, and we do not knowingly collect their personal information.
We will post changes to this policy on this page and update the date above. If a change materially affects account holders, we will email them before it takes effect.