Privacy Policy

This Privacy Policy explains what information Falcontext (the browser extension for Chrome, Edge, Brave, Arc and Firefox, the desktop app for Mac and Windows and the falcontext.com website) collects, how it’s used, and the choices you have. Falcontext is built around a simple principle: your manuscript is yours, and it stays on your device unless you explicitly choose otherwise.

1. Who we are

Falcontext is operated by Falcontext, based in the Netherlands. You can reach us at support@falcontext.com for any privacy questions or requests.

2. What we collect

2.1 Data stored only on your device

The extension stores the following locally in your browser’s own storage, and it never leaves your device except through cross-device sync (below), which is on unless you turn it off:

• Writing and editing goals, daily/total word targets
• Word count history (rolling 14-day window), editing history, and writing-activity days
• Streaks and personal records (best day, most words revised or removed in a day, longest streak)
• Achievement/badge progress
• Chapter and scene markers you create
• For the documents you track, a short code for each word, as the document was at the start of the day, at the start of the last day you worked on it, and at its latest reading, to count the words you revise and remove; and while a writing sprint runs, as it was when the sprint started, to check only what the sprint wrote. Kept on your device, replaced each day (a sprint’s when it ends), deleted after a week without use, and never synced or sent anywhere.
• For the documents you track, a short code for each paragraph (to show what you wrote or changed today and last time, and to find a paragraph pasted twice), the day each chapter and scene was last worked on, and a short code of the few words at each chapter and scene marker and around each finding you chose to ignore in its place (so they follow your text as you write). Codes are made from the words but are not the words; they’re kept on your device, and only Drive sync (2.2a) carries any of them.
• App settings (theme, tracking toggles, reminder times, interface preferences)

2.2 Data synced across your devices (on unless you turn it off)

Sync across your devices is on unless you turn it off (Settings → Sync, “Sync across my devices”). It syncs a subset of the data above: settings, the manuscript list (names, goals, reminders, and which documents belong to each), achievements, and for each tracked document its title, its address (the Google Docs link or the page’s web address), goals, recent history and records. It uses Chrome’s own built-in sync infrastructure, tied to your Google account – the same mechanism Chrome uses to sync your bookmarks or passwords – so this data passes through Google’s sync servers. In Firefox, the browser’s own sync is used instead (Firefox Sync, tied to your Mozilla account, if you use it), and the data passes through Mozilla’s sync servers; Falcontext does not operate a separate server that stores this data. Browser sync never carries your chapter and scene marker names or the check findings you ignored (those can hold words from your writing; only Drive sync, 2.2a, carries them). We never sync: your license key, or the text of your manuscript itself.

2.2a Sync through your Google Drive, Dropbox or OneDrive (optional)

If you turn on sync through Google Drive (in the extension, or in the desktop app, where it’s the only way to sync), the same data as in 2.2, plus your chapter and scene markers (their names, and the scenes you ticked) and the check findings you ignored (a phrase, a name, or a sentence’s first words each), and the codes and days of 2.1 that keep Today and last time the same on every device (the paragraph codes at the start of a day and at a reading at most every half hour, never the codes per word), is kept in one file in the hidden app-data folder of your own Google Drive. Falcontext asks Google for the drive.appdata permission for this: it lets Falcontext see only its own file in that folder, and nothing else in your Drive. The folder doesn’t show in your Drive; you can see how much space it takes, and delete it, under Settings → Manage apps in Google Drive. This is how the desktop app, and browsers other than Chrome, share your progress. The file goes directly between your devices and Google; Falcontext does not operate a server that sees it. As with Chrome sync, your license key and your manuscript’s text are never included in this file. (The writing pad’s manuscripts, if you write in it, are kept in files of their own in the same folder: see 2.2d.) Turning Drive sync off in Settings can delete the file.

You can instead (or as well) turn on sync through your Dropbox or your OneDrive. The same file, with the same data, is then kept in that service’s “Apps/Falcontext” folder in your own account: Falcontext asks Dropbox and Microsoft for access to that one folder only (Microsoft’s Files.ReadWrite.AppFolder), and can see nothing else in your Dropbox or OneDrive. You sign in on Dropbox’s or Microsoft’s own page. They send a one-time sign-in code back through Falcontext’s sign-in page (falcontext.com/app/write/oauth.html), which only hands it on to Falcontext on your device; the code works once, and only with a secret that never leaves your device. The resulting sign-in tokens are kept on that device only (in the extension’s or Perch’s storage in your browser, or in the desktop app’s own data on your computer), never synced; turning that sync off removes them, and can delete the file. The file goes directly between your devices and Dropbox or Microsoft, under their own privacy policies; Falcontext does not operate a server that sees it. You can revoke Falcontext’s access at any time in your Dropbox or Microsoft account settings.

In the desktop app, signing in to Google happens in your browser, on Google’s own page. The app keeps the resulting sign-in token on your computer, readable only by your user account, to sync without asking again; signing out, or turning Drive sync off, removes it and withdraws it at Google. The app also keeps your Google account’s email address, only to show which account is signed in.

2.2b The desktop app

The desktop app tracks the Scrivener projects and Word, Pages and LibreOffice Writer documents you choose. It reads them on your computer to count words and run the checks, in the same way the extension reads a web page: the text is processed on your device and never sent anywhere. What it stores (the data listed in 2.1, and the list of documents you track) stays on your computer, except for what Drive sync (2.2a) shares, if you turn it on. To suggest documents and offer newly created ones for tracking, it looks up the names of recent Scrivener, Word, Pages and LibreOffice files: on a Mac through macOS’s Spotlight, on Windows by looking through your Documents, Desktop, Downloads and cloud-drive folders (OneDrive, Dropbox, iCloud Drive). Those names stay on your computer. It checks for updates by downloading a small file from GitHub, which sees your IP address as for any download.

2.2c Falcontext Perch (the web app)

Falcontext Perch (the web app at falcontext.com/app/) is the same panel as the extension, as a web page for phones and tablets. It counts only the Google Docs you choose in Google’s file picker, reading them with the same drive.file permission as the extension (2.3), in your browser; with “Write in your Google Docs here” turned on in the pad’s Preferences (off unless you turn it on), a Google Doc you may edit can be written in there too, and what you type goes to that document the way 2.3 describes. What it stores (the data listed in 2.1, and the list of documents you chose) is kept in your browser’s own storage for falcontext.com; the Google sign-in token is kept only for the browser tab’s session and lasts about an hour. Signing in turns on sync through your Google Drive (2.2a), which is how Perch shares your progress with the extension; you can turn it off in its Settings. Falcontext’s server only serves the page: nothing you write, count or store reaches it.

2.2d The writing pad

The writing pad in Perch (falcontext.com/app/write/) keeps what you write in your browser’s own storage on your device, with earlier versions and recently deleted manuscripts; Falcontext’s server never receives it. If you choose, each manuscript is also backed up as a Word file to a place in your own account: your Google Drive (a “Falcontext” folder, with the same drive.file permission as 2.3), your Dropbox or your OneDrive (their “Apps/Falcontext” folder: Falcontext can only see that folder), or a folder on your computer. The file goes straight from your browser to that service, under that service’s own privacy policy. To connect Dropbox or OneDrive you sign in on their own page; the resulting sign-in tokens are kept in your browser only, and disconnecting (or clearing your browser’s data) removes them. You can revoke Falcontext’s access at any time in your Dropbox or Microsoft account settings.

So that your manuscripts are the same on all your devices, when you’re signed in with Google in Perch and the Google Drive backup is on, the writing pad also keeps an exact copy of each manuscript in the hidden app-data folder of your own Google Drive (the same folder and drive.appdata permission as 2.2a), one file per manuscript, and your other devices read it from there. A manuscript you delete leaves only its title and when it was deleted, so your other devices delete it too. The files go directly between your browser and Google; Falcontext’s server never sees them. Turning the Google Drive backup off (the pad’s ☰ → Backups) stops it; you can delete the folder under Settings → Manage apps in Google Drive. The pad’s Preferences (quotation marks, spell check, page layout and your substitution list) go with your other settings (2.2a).

2.3 Google Docs access

If you track a document in Google Docs, Falcontext asks for Google’s drive.file permission through Google’s own sign-in. With it, Falcontext can only open the Google Docs you choose yourself – it cannot see, list, or open any other file in your Google Drive. When you click Fix on a Google Doc, or type in one in Perch, Falcontext asks Google Docs to make that change in your document, straight from your browser.

The first time you use Falcontext on a document, a small window opens on falcontext.com/allow with Google’s file picker, showing just that document (or the documents you track). Falcontext can read a document only after you select it there. You can withdraw this access at any time in your Google Account, under Security → Third-party apps & services.

That page signs you in with Google only to open the picker. Google’s sign-in token is kept in the page’s memory while it’s open; it is not stored, and it is never sent to any Falcontext server. The page itself doesn’t read your document.

This access is used solely to count words, to run the checks described below (such as Prose Analysis and chapter/scene outlines), and, when you click Fix or type in a Google Doc in Perch, to make the change you asked for in that document. Document text is read in your browser, only to compute those results, and it never leaves your device: it is never sent to Falcontext or to anyone else, and we never receive it or anything made from it. A Fix sends Google only the change itself (a quotation mark, a word spelled the book’s way) and where it goes, to your own document, the same way typing it in Google Docs would; it doesn’t go through Falcontext. Typing in a Google Doc in Perch works the same way: a moment after you pause, the words you typed (and nothing else) go from your browser to your own document through Google, and Perch reads the document back to show it as it is. What your browser keeps from it, on your device only, is listed in 2.1: the resulting numbers, and a short code for each word as it was at the start of the day.

Falcontext’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data from Google Docs is never used for advertising, never sold, never used to train AI or machine-learning models, and never read by a person.

2.3a Other web editors, and counting with Falcontext closed

On other sites (Atticus, Ellipsus, WordPress, Reedsy Studio and Wattpad and other web editors), the browser lets Falcontext read a page only after you click its icon there, and only until that page reloads. While it can, Falcontext keeps counting the words in the editor as you write, even after you close its panel, so the day still counts.

In the extension’s Settings, under “Count without opening Falcontext”, you can let it count on Google Docs, Ellipsus or Atticus without clicking each time. Your browser asks you to allow each site, and you can take it back there at any time. On a site you allow, Falcontext watches the pages you open for typing, to keep the word count of documents you have counted with it before; on Google Docs it only notices that you typed and reads the count as in 2.3. It reads nothing on any other site. As everywhere else, only the numbers are kept, on your device, and the text never leaves it.

On Atticus, WordPress and Ellipsus (soon Reedsy Studio and Wattpad too), a check’s Fix types the change into the editor in your browser, as you would; the editor saves it as it saves your own typing, and its Undo takes it back.

2.4 Prose Analysis

The Prose Analysis tool and Bird’s Eye (every check, from adverbs and passive voice to tense slips, pacing and the character tracker) run entirely inside your browser, with rules and word lists: no AI is used. Your text is never sent anywhere for these features, including to us.

Those rules and word lists can be updated between versions of Falcontext. From the version after 6.0.0 (and in Perch now), when you open the Edit tab or click Scan now (at most every five minutes), and once a day when Falcontext opens (so the checks as you write get newer rules too), Falcontext asks falcontext.com for its rules file, and downloads the parts that changed. The request carries nothing you wrote and nothing about you, only which Falcontext asked (the extension, Perch or the desktop app), and, once, after the extension or the desktop app is installed, that it’s that copy’s first ask. Like any download, falcontext.com’s web host sees the request and your device’s internet address in its usual server logs, which we use only to count how many times each rules file is downloaded, by which Falcontext; and the server counts the asks themselves, each copy once a day (see 2.9). The rules are kept on your device and used there; nothing is sent back.

From the version after 6.0.0 (and in Perch now), News (the bell in Falcontext: new versions and blog posts) is read the same way: once a day when Falcontext opens, and when you open News, Falcontext asks falcontext.com for its news file. That request carries nothing about you or your writing and isn’t counted; what you’ve read is kept on your device. Turn News off there and it’s never asked for.

2.5 Synonym Checker

From version 4.1.1 the Synonym Checker looks words up in a thesaurus built into Falcontext (made from Princeton University’s WordNet), so nothing is sent anywhere. In earlier versions, the single word you looked up was sent to Datamuse, a third-party API, to retrieve synonyms; no surrounding manuscript text or context was sent.

2.6 Subscription and license status

Signing in to Pro with your email (from 4 November 2026). When you type your email address in Falcontext’s Settings, it goes to falcontext.com’s server, which asks Paddle and Lemon Squeezy whether Pro was bought with it and, if so, emails you a Sign in button. Clicked in the browser where you asked, it opens falcontext.com, which hands its one-time secret to Falcontext in that browser; it only works with the request that device made. Clicked anywhere else, the page shows a 6-digit code to type where you asked. The secret and the code travel after the # in the link, which browsers never send to a server. The device then gets its own credential, which Falcontext keeps on the device and sends, with the device’s label (e.g. "Mac · a1b2"), when you sign in, after that at most once an hour as Falcontext opens, and when Settings shows your plan or you open Manage subscription. The server replaces the credential with a new one at most once an hour, so a copy of it stops working. The server never stores your email address: it keeps a code made from it with a secret of its own (from which the address can’t be worked out), your Paddle customer ids and Lemon Squeezy license-key ids, and for each signed-in device a random id, its label, when it was last seen and a fingerprint of its credential (its SHA-256). A code and the button’s secret are kept as fingerprints for their 10 minutes. To limit how often codes are asked for, it counts them per address and per IP address that day, with codes made from them and a secret (never the addresses), deleted the next day. So that someone else asking can’t keep your sign-in email from you, a device that signed in is remembered as one that may always ask: Falcontext makes a random mark on the device for this (never in a backup), and the server keeps, with the code made from your address, a code made from that mark and one made from the IP address it signed in from (with its secret: neither can be worked out from it), until neither is used for over a year. A device not seen for over a year is forgotten. To stop Pro being passed round, the server also keeps the time of each sign-in, with that code, for 30 days. When you start a trial from Falcontext’s Unlock with Pro, the pricing page’s address carries a random one-time code from that app, so Pro switches on there once you click the button in the email we send you: the server keeps its fingerprint with the code made from your address, for an hour. Falcontext’s emails (sign-in, your trial, your purchase, a move, and, if you buy here while a Lemon Squeezy subscription still renews, one asking whether to cancel it) are sent through Resend, an email service, from its servers in the EU (Ireland), which keeps its records in the US: it gets only your address and the email, and processes your email address for us.

Pro from Paddle. To start a trial, the pricing page sends your email address, country and postcode to falcontext.com’s server, which emails you a link to start it; they travel sealed (encrypted) in that link, for a day, and the server keeps none of them. When you click it, the server passes them to Paddle to set up your subscription. When Paddle confirms it, the server emails you how to sign in, and one reminder before a trial without a card ends; it asks Paddle for your email address each time and never stores it. For each subscription it keeps Paddle’s subscription and customer ids, the plan, its status and dates. To limit trials, it counts the trials started from each IP address that day the same way. The page for adding a card, falcontext.com/pay/, and the pricing page when you buy, load Paddle’s checkout script (Paddle.js) from Paddle; the pricing page asks falcontext.com for the prices in your country (from the country Cloudflare gives, never your address).

Moving from Lemon Squeezy to Paddle. When you’re signed in with a Lemon Squeezy subscription, the server asks Lemon Squeezy when it renews and what you paid, to offer the move in Settings. If you move, it keeps your Lemon Squeezy subscription id with the code made from your address until the move is done (a month at most; once moved, that you moved, for as long as you have Pro, so your other devices switch over), and cancels that subscription at Lemon Squeezy once Paddle confirms the new one. Once you’ve moved, a device that renews its plan with your license key is signed in with your email instead, by itself: the server takes the email from Lemon Squeezy’s answer about the key and keeps it no more than for any sign-in.

Pro from Lemon Squeezy (bought before 4 November 2026). To verify whether your subscription is active, Falcontext sends your license key directly to Lemon Squeezy’s License API each time it needs to check or re-check your status, along with a label identifying this device (e.g. "Mac · a1b2"). Lemon Squeezy’s response tells Falcontext which plan the key unlocks.

Falcontext also sends your license key, and the id Lemon Squeezy gave this device’s activation of it, to falcontext.com’s own server when you enter it and after that at most once an hour, as Falcontext opens. For a Lemon Squeezy key, the server asks Lemon Squeezy whether the key works on this device and, if it does, sends back a signed confirmation of your plan, which Falcontext keeps on your device. The server stores nothing: not your key, not your IP address, and no record of the request (like any website, our host’s server logs may record your IP address for a short time). No writing, titles or counts are ever part of it.

Separately, a small record derived from that result – your subscription tier, the device label, and (if applicable) the last 4 characters of the key – may be stored locally and, if sync is enabled, synced across your devices so you can see your plan status on each one. Your full license key and payment details are never included in this record, and are never synced.

2.7 Payment information

Subscriptions from 4 November 2026 are billed through Paddle (Paddle.com Market Limited), our payment processor and merchant of record; earlier ones through Lemon Squeezy. They collect and process your payment details (card information, billing address, etc.) directly – we never receive, see, or store your card details ourselves. Their own privacy policies govern that data: Paddle’s and Lemon Squeezy’s.

After each order (with Paddle: a trial started, and its first payment), Lemon Squeezy or Paddle tells falcontext.com’s own server the order number, its date, the plan, which button or page on falcontext.com (or in Falcontext) the checkout started from, such as “hero”, and the name of the site the visit came from, such as reddit.com (see 2.9). We keep only those five things, to know which parts of the site, and which other sites, lead to sales: never your name, email address or payment details, and nothing is stored on your device for it.

2.8 Support communications

If you email support@falcontext.com, we receive your email address, any name you provide, and the content of your message. We use this only to respond to your request.

2.9 The falcontext.com website, and analytics

falcontext.com uses no cookies and no outside analytics: no Google Analytics, and nothing that follows you to other sites. Its fonts and images come from falcontext.com itself. If you choose light or dark with the sun and moon in the menu, that choice is kept in your own browser (its local storage) and never sent anywhere. (The pricing page loads Lemon Squeezy’s checkout script, and the page for adding a card, falcontext.com/pay/, Paddle’s, so they can open the checkout on the page; that isn’t analytics, see section 4.)

Instead, falcontext.com counts visits on its own server, without cookies. It counts each page you view (how long it was on screen and how far down you scrolled), the buttons and links you click (another site’s link only by that site’s name), downloads of the desktop app, Pro checkouts started and done (the plan and price; never the order or who bought), addresses that aren’t pages (to mend broken links), and how long each page took to load (your browser’s own timings, to fix slow loading). With each: where you came from (only a site’s name, such as reddit.com, or a link’s campaign name), your window’s size as one word (mobile, tablet, laptop or desktop), your browser and system with only their main version (such as Chrome 130 on Windows 11), and your country (from your device’s time zone, or else from your IP address). Nothing is stored on your device.

To count each visitor once a day and follow a visit through the site, the server makes a code from your IP address and browser name, mixed with a secret it replaces every day at midnight (Amsterdam time), and keeps each view and click as a record with that code. Once the secret is gone, nobody, the site’s owner included, can tell whose a code was or link one day to another. Your IP address and browser name themselves are never kept. A visit from a data centre’s network (Google Cloud, Amazon and the like: a program, not a person) isn’t counted; the network is read from your IP address, never kept. A random number made as each page opens, carried in links between its pages, keeps a visit together if your IP address changes; it’s kept with the code for that day and the next only. Daily and hourly totals are kept too. When you start a Pro checkout, the name of the site your visit came from goes to Lemon Squeezy with it (section 4). The site’s owner’s own visits are left out, apart from their load times. The sign-in and allow pages aren’t counted.

From the apps, falcontext.com counts five things. The extension and the desktop app open its welcome page once, when installed, counted as an install. If the extension is in your browser, falcontext.com’s pages ask it whether it’s there, and it answers yes and nothing else (in Firefox, it marks the page), kept with the page’s record; no other website can ask it. And from the version after 6.0.0, the apps’ asks for the checks’ rules (2.4) are counted once a day per copy, by the same one-day code, with which app asked and the country from your IP address; from the version after 6.1.1, a copy’s first ask is also counted as a first open, by app and country. And a link from Falcontext to falcontext.com (a help page, Pricing, the challenge) says which app and which part or button it’s from, and your plan (free, Pro or Ad-Free), so that visit is counted as Falcontext’s. And from the version after 6.0.0, the desktop app counts which of its features you use, and what went wrong, as Perch does: by the same fixed names (each once a day, or once each time it starts), with the same one-day code, the time, your system (macOS or Windows) and the country from its time zone. Your writing, your documents’ names and contents and word counts are never part of it. Beyond these, the extension sends no analytics: what you click inside it is never counted.

Perch (the web app at falcontext.com/app/) counts which of its features a visit used, by fixed names such as “Settings opened” (with a check’s name, such as “adverbs”, where that applies), and how long it was open, with the same one-day code. It also counts what went wrong, to find bugs: by a fixed name, such as “Fix didn’t go through”, and where (the editor, or the place in Falcontext’s own code), never an error’s words. Your writing, your documents’ names and contents, word counts, words you look up and anything else you type are never part of it. The writing pad sends nothing.

The Google Docs allow page (falcontext.com/allow) and the sign-in page load Google’s sign-in and file picker, as described in 2.3, and no analytics; Google’s own privacy policy applies to those.

2.10 The November challenge (optional)

The November challenge is at falcontext.com/challenge. If you join, falcontext.com keeps: the pen name or nickname you choose (we don’t ask for your real name, and suggest you don’t use it), whether you want to be on the public boards, whether words or days written matter most to you, the groups you start or join, and for each day of November the number of words you type in on the page. Never any text, titles, chapter or document names.

If you let Falcontext count your words for the challenge (in any version of Falcontext, from its menu), Falcontext sends falcontext.com, for each day of November, two numbers: how many words you wrote in the documents and manuscripts you chose there, and how many of them you typed rather than pasted. Falcontext itself sends no name: you type that on the challenge page. Which documents count stays in Falcontext.

There are no accounts. Joining makes a random secret key in your browser, kept in its local storage (not a cookie), and Falcontext makes one of its own (synced to your other devices if you use sync); the server stores only a scrambled form of each (its SHA-256 hash), to know your numbers are yours. Your challenge link carries your key, after the #, which browsers never send to a server. The server doesn’t store your IP address; like any website, our host’s server logs may record it for a short time. To stop anyone flooding the boards with made-up writers, it counts requests per visitor with a code made from the address and a secret that is replaced every day, so the code can’t be turned back into the address or followed from one day to the next; it’s kept only as a count until the next day.

To tell typed words from pasted ones, Falcontext notes on your device, per day, how many minutes you were typing and how many words you pasted into each document (numbers, not the text). Those notes stay on your device; only the resulting count of typed words is sent.

Who sees what: your pen name and numbers appear on the public boards only if you choose it, and to the members of any group you join (anyone with a group’s code or invitation link can join it). Names on the public boards must not include links or offensive words, and we may hide a name from them.

Leaving the challenge (Your settings, on the challenge page) deletes your pen name, numbers and group memberships from the server at once. Everything from a November is deleted on 1 February.

2.11 Reviews (optional)

If you write a review on falcontext.com/reviews, falcontext.com keeps what you send: the stars you give, the words you type, the name you type (if any; it’s shown with your review, so use a pen name if you like), a photo of yourself you add (if any; it’s shown with your name: your browser crops it to a small square and sends only the picture itself, never where it was taken or with which camera, and the server makes it anew the same way) and, when you came from one of Falcontext’s apps, which one (the extension, the desktop app or Perch), with the day it was sent. Nothing else: no email address, no IP address, no account. A review shows on the page only once the site’s owner has read it, and its words are never changed; the owner can hide or delete it, or take its photo off. A photo is shown only with a review that shows. To have yours taken down, email support@falcontext.com with its words, and it’s deleted. Like any website, our host’s server logs may record your IP address for a short time.

The reviews page also shows posts that writers made about Falcontext elsewhere (such as on X), copied with their permission: their words, name, handle and profile photo, with a link to the post. The photo is a copy kept on falcontext.com, so viewing the page never contacts X. To have yours taken down, email support@falcontext.com.

2.12 The Discord bot (optional)

If a Discord server adds Falcontext’s bot, its /sprint command posts a writing sprint in a channel. For each sprint, falcontext.com keeps the server’s and channel’s numbers, the bot’s message number, the sprint’s length and start, and the Discord user numbers of who started or joined it, to show them and ping them; all of it is deleted a day after the sprint ends. If you use /timezone, it keeps your Discord user number with your time zone (or your offset from UTC), deleted after 180 days without a sprint by you. Never a name, a message’s words or anything you write. Discord sends these commands under its own privacy policy. Falcontext itself sends nothing to Discord: the sprint link holds only the start and length.

3. Legal basis for processing (EU/EEA users)

Where the GDPR applies, we process your data on the following bases: performance of a contract (providing the extension and Pro subscription features you’ve signed up for), your consent (e.g. turning on sync through Google Drive, Dropbox or OneDrive, or Google Docs access, joining the November challenge or writing a review), and our legitimate interest in operating and improving Falcontext, which includes counting visits to falcontext.com without cookies, with a code that lasts one day (2.9), knowing which button or page each order started from (section 4) and keeping your progress the same on your devices through your browser’s own sync (you can turn that off at any time in Settings → Sync).

4. How we share data

We do not sell your data. We share data only with the service providers needed to run Falcontext:

• Paddle – payment processing and subscription billing (merchant of record) for Pro from 4 November 2026 (2.6, 2.7)
• Resend – sending the sign-in codes and the emails about your trial, from the EU (Ireland); it processes buyers’ email addresses (2.6)
• Lemon Squeezy – payment processing and subscription billing (merchant of record) for Pro bought before then, and license-key verification, directly and through falcontext.com (2.6)
• Google – Google sign-in, the Google Picker, Google Docs API access (only for documents you select), Chrome Sync, Google Drive’s app-data folder if you turn on Drive sync, governed by Google’s own privacy policy
• Mozilla – in Firefox, Firefox Sync if you turn on sync and use it, governed by Mozilla’s own privacy policy
• GitHub – hosts the desktop app’s updates (its downloads come from falcontext.com itself)
• Cloudflare – delivers falcontext.com’s pages and files from a server near you (a content delivery network): every request to falcontext.com passes through it, so it sees your IP address and what’s asked for, as any network in between does, under Cloudflare’s own privacy policy. It adds nothing to the pages and runs no analytics or tracking for us
• Hostinger – hosts falcontext.com, including the November challenge’s server and database (2.10), the reviews (2.11), the Discord bot (2.12) and the license check (2.6)
• Discord – only in a Discord server that adds Falcontext’s bot: the bot’s messages and pings go through Discord (2.12)
• Dropbox and Microsoft (OneDrive) – only if you choose them as a place for the writing pad’s backups (2.2d) or for sync (2.2a); the files go from your browser or the desktop app to your own account
• Datamuse – single-word synonym lookups, in versions before 4.1.1 only

5. Data retention

Local history is capped to a rolling window (typically 14 days) by design; personal records, achievements, and settings are kept until you clear them yourself using the extension’s built-in export/backup and cleanup tools, or until you uninstall the extension, which removes all locally stored data. Paddle and Lemon Squeezy retain billing records as required by law. falcontext.com keeps a Paddle subscription’s record (2.6) while it runs and for a year after it ends (refunded too). To give each inbox one free trial, it keeps a code made from your address (never the address) for as long as falcontext.com sells Pro, and your account (that code, your Paddle customer ids and Lemon Squeezy license-key ids) until you ask us to delete it: support@falcontext.com. The November challenge’s data is deleted when you leave it, and in any case on 1 February after that November (2.10). A review is kept until you ask for it to be deleted, or the site’s owner deletes it (2.11). The Discord bot’s sprints are deleted a day after they end, a time zone after 180 days unused (2.12). The site’s visit records and totals (2.9) and the order records (2.7) are kept as long as falcontext.com runs: once a day’s secret is gone, nothing in them can be traced to a person.

6. Your rights

Depending on your location, you may have the right to access, correct, delete, restrict, or export your data, and to object to certain processing. Since most Falcontext data lives on your own device, you can exercise most of these rights directly – through the extension’s Settings panel (export, backup, or clean-up tools) or by uninstalling it. To delete your November challenge data, leave the challenge in its settings. To delete a review, email us its words. For anything else, including subscription/billing data, contact us at support@falcontext.com. EU/EEA users also have the right to lodge a complaint with their local data protection authority.

7. Children’s privacy

Falcontext is not directed at children, and we do not knowingly collect data from anyone under 16.

8. Security

We take reasonable measures to protect the data described above, but no method of storage or transmission is completely secure, and we can’t guarantee absolute security.

9. International data transfers

Our service providers (Google, Mozilla, Paddle, Lemon Squeezy, Resend, GitHub, Cloudflare, Discord, Dropbox, Microsoft, and Datamuse for versions before 4.1.1) may process data outside the Netherlands/EEA. Where this happens, we rely on the safeguards those providers make available, such as Standard Contractual Clauses.

10. Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date at the top of this page.

11. Contact

Questions about this policy or your data? Email support@falcontext.com.