Privacy Policy
Effective 1 October 2026.
BlinkWrite reads what is on your screen. That is an unusual thing to let a piece of software do, and this policy exists to tell you exactly what happens as a result — what leaves your computer, what does not, what we keep, and for how long.
The short version
| What BlinkWrite reads | The text in the window you are actively working in, so it can suggest what to write. |
| What leaves your computer | Text, after an on-device process has tried to strip out contact details, account and ID numbers, and credentials. It does not remove people's names — see Section 2.3. Screen images never leave your computer. |
| Where it goes | Through BlinkWrite servers in the United States to an external LLM provider that generates suggestions. |
| How long we keep it | BlinkWrite does not save production writing in its application database or content logs. Provider retention still applies — see Section 2.5. |
| Do we train on it | No. Not your text, not the suggestions we generate for you. |
| Do we sell it | No. We do not sell personal information. Optional website, product-milestone, and ad-performance measurement is described in Section 7. |
| Can you turn it off | Yes, at any time, without asking us — see Section 5. |
This summary is here to be useful, not to replace the rest. The detail below is what governs.
1. Who we are
BlinkWrite is provided by TalentHQ Labs, Inc., a Delaware corporation with its principal place of business at 2261 Market Street, STE 85253, San Francisco, CA 94114, United States ("BlinkWrite", "we", "us", "our").
For the purposes of the EU and UK General Data Protection Regulation, we are the controller of the personal data described in this policy.
Privacy contact: [email protected]
This policy covers the BlinkWrite apps for macOS and Windows, our website at blinkwrite.ai, and our support correspondence. It forms part of our Terms of Service.
2. What BlinkWrite reads from your screen
This is the section that matters. Please read it.
2.1 The two permissions, and what each one allows
On a Mac, BlinkWrite needs two macOS permissions to work. You grant them yourself in macOS System Settings. We cannot enable them for you and macOS will not let us.
Accessibility. Lets BlinkWrite read the text content of the application window you are actively working in, through the same macOS interface that screen readers and other assistive software use. This is how BlinkWrite reads most chat threads and email, and how it inserts a suggestion when you accept one.
Screen Recording. Some applications do not make their text available through the accessibility interface. This permission lets BlinkWrite read the text in those applications by capturing the screen image and extracting the text from it on your Mac. It also helps BlinkWrite place suggestions next to your cursor.
On Windows, BlinkWrite does not ask for these permissions. It reads text through the accessibility features built into Windows and, in a few applications, extracts it from a screen capture on your PC.
2.2 What we do with them, and what we do not
macOS grants these permissions at the system level. What BlinkWrite actually does is narrower than what they technically allow:
- BlinkWrite reads the window you are actively working in. It does not read background windows, other desktops, or other users' sessions.
- BlinkWrite does not record video, take continuous screenshots, or keep any recording of your screen. A screen capture is taken only when BlinkWrite needs one: to extract text, to place a suggestion next to your cursor, or, in some applications, to show a still image of the text field while a suggestion is inserted. It stays on your computer and is discarded right after use.
- BlinkWrite does not log your keystrokes outside the text field you are working in.
- BlinkWrite does not type or send anything on its own. It proposes text; you accept it and you send it.
2.3 On-device masking — what it does and what it does not
Before anything is transmitted, BlinkWrite runs a process on your computer that attempts to detect and mask certain kinds of personal information, so they are not sent to us. This is what it looks for, and it is the complete list:
- Contact details — email addresses, phone numbers, postal addresses
- Financial details — card numbers, bank account numbers, dollar amounts
- Government and identity numbers — social security numbers, passport numbers, driver licence numbers, tax identification numbers, dates of birth
- Credentials and technical identifiers — passwords, PINs, API keys, access tokens, secret keys, IP addresses
It does not detect or remove people's names. That is a real limitation and we would rather state it than let the list above imply otherwise. What happens to names is covered in the next two paragraphs and in Section 3.
Your own name is handled separately. Where your name appears in the text, it
is replaced with a neutral [USER] marker before the text is sent, so the model
can tell your messages from everyone else's. We do also send your display name
alongside the text, as a separate field, so that a suggestion can address you or
sign off in your name. So your name reaches us — just not buried in the middle of
the text.
Other people's names are not masked. In a chat thread or an email, the names of the other participants are sent to us along with what they wrote, because that is how the model tells one speaker from another. Anything else our list covers — their email address, their phone number, their address — is masked in the normal way.
This is automated and best-effort. It is not perfect, even for the categories it does cover. It uses a machine learning model that can miss things, particularly in unusual formats, in mixed-language text, or in contexts it was not designed for. We do not promise that all personal or sensitive information is detected or masked.
For that reason, we treat everything we receive as personal data and apply this policy to it. We do not claim the text reaching our servers is anonymous, because we cannot prove it is.
And for the same reason: do not use BlinkWrite in text fields containing information you cannot afford to have transmitted to us — health records, payment card data, government identification numbers, legally privileged material, classified information, or trade secrets. You can pause BlinkWrite for one application or one website, pause it everywhere, or withdraw the permissions entirely, at any time — see Section 5.
2.4 What we transmit, and to where
Your masked draft, available context, masked Memory excerpts (Section 2.7), the name of the app you are writing in, display name, language, and writing instructions travel over encrypted connections through BlinkWrite servers to an external LLM provider. The provider generates a suggestion, which BlinkWrite returns to your computer. Our application servers run in the United States. Provider processing locations and international transfers are described in Section 10.
Screen images are not transmitted. Where BlinkWrite uses Screen Recording, the text is extracted from the image on your computer and only text is sent. The image itself never leaves your device. Masking is best-effort, as described in Section 2.3.
2.5 Data retention
BlinkWrite does not save production drafts, conversation context, or suggestions in its application database or content logs. Our application processes this content to return a suggestion. Account records and usage counts have separate retention periods in Section 11.
On the Free plan we do store a fingerprint of each suggestion request: a one-way code computed from the request with a secret key. It lets us recognise a retried request so it is not counted against your allowance twice. It cannot be turned back into your text, and it is deleted after 14 months with the rest of your usage records (Section 8).
Production requests to the LLM provider explicitly disable API response storage. This controls the stored API records available for review and evaluation. It does not disable the provider's separate abuse-monitoring retention.
We do not currently promise Zero Data Retention for LLM processing. The provider can retain prompts and responses in abuse-monitoring logs for up to 30 days. Longer retention can apply where required by law or reasonably necessary to protect the service or others from harm. Prompt caching can retain encrypted model data on provider infrastructure for up to 24 hours.
Development and test environments can enable provider API call logging for debugging and evaluation. These settings do not enable production API response storage.
If you request access to or deletion of writing content, contact us under Section 12. We do not maintain a production writing history. We will assess the request and work with the relevant provider where applicable. Provider retention exceptions can limit immediate deletion.
2.6 We do not train on your content
We do not use production writing or suggestions to train, fine-tune, or evaluate models. We do not opt in to provider training on API content. Provider safety processing and retention are separate from training and are described in Section 2.5.
We do keep records of how the product is used: how many suggestions were requested and accepted, and whether each one was shown, accepted, or dismissed. They contain no text, and they are covered in Section 8.
2.7 Memory
Memory helps BlinkWrite match how you write to each person. It is on by default and is stored, encrypted, on your computer. When it is relevant, short masked excerpts from it, such as how you replied before and any instructions you set for that person, are sent with a suggestion request. Section 2.5 applies to them. You can turn Memory off or delete it in Settings → Memory.
BlinkWrite also keeps an encrypted cache of recent suggestions on your computer for up to 60 days.
3. Other people's information
BlinkWrite reads conversations, and conversations have other people in them. When you use BlinkWrite in a Slack thread or an email chain, the text on your screen includes messages written by people who have not agreed to anything and do not know BlinkWrite is running.
Here is what happens to that content:
- It goes through the same on-device masking as everything else, so their email addresses, phone numbers, postal addresses and account numbers are masked exactly as yours are.
- Their names are not, and are sent to us. In a thread, the name against each message is what tells the model who said what, so it travels with the message. We would rather say this plainly than let the paragraph above imply otherwise. Names can also reach the LLM provider with the request.
- What survives masking is transmitted and used to generate your suggestion. The retention controls in Section 2.5 apply to this content too.
- We do not use it for training or sell it. The service providers described in Section 9 can process it to provide and protect the service.
We are the controller for that content while we process it, and we process it on the instruction of the BlinkWrite user whose screen it is on. Under our Terms of Service §6.1, that user is responsible for having the rights and permissions needed to run BlinkWrite over content involving other people — including any duty of confidentiality they owe, and any consent rule that applies to recording or monitoring communications where they live.
If your information reached us because someone else used BlinkWrite, and you want to exercise a right over it, contact [email protected]. We will assess your request and work with the relevant provider where applicable. The retention limits and exceptions in Section 2.5 apply.
4. The personal data we collect
| Category | What it is | Where it comes from |
|---|---|---|
| Account data | Your email address, your first and last name, your sign-in method, and whether you have ever started a free trial. For Apple or Google sign-in, this includes the provider account identifier. For email sign-in, this includes a salted one-way password hash. We never store your plaintext password. | You, when you create an account or sign in — see Section 4.1 |
| Message text | Masked text from the window you are working in, sent to generate a suggestion, plus the suggestion returned | Your computer, at the moment you ask for a suggestion. See Section 2.5 for BlinkWrite and provider retention. |
| Subscription data | Your plan, price, billing period, renewal date, trial and cancellation status, and a Stripe customer reference | Stripe, as your subscription changes. We never see or hold your card number — see Section 4.2 |
| Usage records | Per day and per suggestion type: how many suggestions were requested and accepted, and how many tokens were used. For each suggestion: its type, your plan, when it was generated, and whether it was shown, accepted, or dismissed. On the Free plan, also your allowance period and how much of it you have used, when you reached a limit and whether the limit notice was shown, and a fingerprint of each request (Section 2.5). None of it contains your text. | Our servers, when the app asks for a suggestion or reports what happened to one — see Section 8 |
| Email preferences | Whether you get upgrade emails, when you turned them off or unsubscribed, whether our email provider reported your address as bouncing or as a complaint, when you last used BlinkWrite, and which upgrade emails we sent you | You, in Plan & Billing or through an unsubscribe link; the app and the web app; Amazon Web Services, which sends our email — see Section 8.1 |
| Session records | For each active session: a token record, the IP address and app or browser user agent it was created from, and when it was last used. For the BlinkWrite app, also the computer's name and type. This is how sign-out, session expiry, your list of signed-in computers, and account security work. | Automatically, when you sign in |
| Technical and security data | Timestamps, request volumes, response codes, error codes. Aggregate server metrics that are not tied to an account. No message content. | Automatically, when the app talks to our servers |
| Consent records | Which version of the Terms, of this policy, and of our Consumer Health Data Privacy Policy you accepted, when, and where you accepted it, with a fingerprint of the exact text | You, when you sign in and continue past the notice that links to these documents, and when you accept a later version |
| Optional measurement data | Browser/session identifiers, campaign labels and click IDs, privacy settings, limited product milestones, and subscription payment amounts with invoice IDs | Website activity and our servers when measurement is enabled — see Section 7 |
| Support data | Your email address, your messages, and any files you attach | You, when you open a support ticket or email us |
| Feedback | What you send on the Feedback page, and any files you attach. An AI service helps us group similar feedback. | You, when you send feedback |
| Docs assistant questions | What you ask the assistant in our documentation. It is sent to an AI service to write the answer and is not stored. | You, when you use the assistant |
| Early-access list | The email address you give to join early access | You, on our website |
| Download link requests | The email address you give to get the download link by email | You, on our website |
| Setup events | Which setup steps the Mac app showed, whether permissions were granted, whether downloads finished, and the app and macOS versions. No message content. | The Mac app, during setup |
Your BlinkWrite app settings — your paused apps and sites, and your app preferences — and your Memory are held on your computer, and we cannot see them. Only the masked Memory excerpts described in Section 2.7 are sent, with a suggestion request.
4.1 Signing in
You can sign in with your email address and password, Sign in with Apple, or Google.
For email sign-in, we store a salted one-way password hash. We never store your plaintext password. We also store one-way hashes of email-verification and password-reset tokens. Verification links expire after 24 hours. Password-reset links expire after one hour and stop working after use.
For Apple or Google sign-in, the provider confirms who you are. It gives us an account identifier and your email address. We do not receive your contacts, your calendar, or your mail. Apple and Google control the records that they keep about the sign-in under their own privacy policies.
If you use Apple's Hide My Email, we receive a relay address rather than your real one. That works normally, and we will only ever have the relay address. Turning the relay off in your Apple ID settings stops our emails reaching you, including receipts and renewal notices.
4.2 What Stripe holds, and we do not
Payments run through Stripe, which acts as merchant of record — it is the seller for the purchase, and it calculates and collects any tax due. Your name, billing address, country, card details, and invoice history sit with Stripe, under its own privacy policy. We receive back only what is listed as subscription data above: the plan, the status, the dates, and a customer reference.
We never receive your card number, and we could not produce it if you asked.
5. Turning it off
You do not need our permission or our help to stop BlinkWrite reading anything.
| To do this | Do this |
|---|---|
| Stop it reading a specific app or website | Pause BlinkWrite for that app or site in settings — for an hour, for the day, or until you turn it back on |
| Stop it everywhere, for a while | Pause BlinkWrite globally, or quit it |
| Stop it reading apps that don't expose text | On a Mac, withdraw Screen Recording in macOS System Settings. Everything else keeps working. |
| Stop it entirely | Quit or uninstall BlinkWrite. On a Mac, you can also withdraw Accessibility in macOS System Settings. BlinkWrite can then neither read through the accessibility interface nor insert suggestions, so the product stops working. |
| Close your account | Close it in settings on the web, or email [email protected] - see Section 11.1. On a Mac, you can also uninstall the app and tick Also delete my BlinkWrite account to do both at once. |
| Remove it from your computer | On a Mac: Settings › General → Uninstall BlinkWrite. It removes the app, the on-device model, your settings, your Memory, and your sign-in — see Section 11.2. On Windows: see Section 11.3 |
| Stop upgrade emails | Turn off upgrade tips in Plan & Billing, or use the unsubscribe link in any upgrade email — see Section 8.1 |
6. Why we process your data, and on what legal basis
The right-hand column applies if you are in the EEA, the United Kingdom, or Switzerland. It is the basis we rely on under Article 6 of the GDPR.
| What we do | Why | Legal basis |
|---|---|---|
| Generate suggestions from the text on your screen | It is the product | Performance of a contract (Art. 6(1)(b)) |
| Run your account and your sign-in sessions | To provide what you signed up for | Performance of a contract |
| Take payment, run the trial, handle renewals and cancellations | To bill you | Performance of a contract; legal obligation for tax and accounting records (Art. 6(1)(c)) |
| Count the suggestions you request, and record whether each was shown, accepted, or dismissed | To enforce the limits of your plan, including the Free plan's monthly allowances, and to learn which features and limits work | Performance of a contract for the limits; legitimate interests (Art. 6(1)(f)) for the rest |
| Email you about Pro after you reach a Free limit | To tell people on the Free plan about the paid plan | Legitimate interests. You can opt out at any time — see Section 8.1 |
| Keep the service secure; detect and investigate abuse, fraud, and duplicate trials | To protect the service and other users | Legitimate interests — running a service that is not defrauded or abused |
| Measure website use, product milestones, and ad performance | Understand which experiences and campaigns lead to useful product use and subscriptions | Consent for optional measurement in the EEA, UK, and Switzerland |
| Keep a record of which terms you accepted | To be able to show what was agreed | Legal obligation and legitimate interests |
| Diagnose and fix faults | To keep the product working | Legitimate interests |
| Establish, exercise, or defend legal claims; comply with lawful requests | To handle disputes and legal obligations | Legitimate interests and legal obligation |
Where we rely on legitimate interests, we have weighed our interest against your rights and concluded it does not override them. Ask us at [email protected] and we will explain the assessment for any given purpose.
We do not use your writing or screen content for advertising. We measure which ads lead to visits, download clicks, account creation, product milestones, and subscription payments under the settings in Section 7. Google Signals and ad personalisation remain disabled. We do not sell your data.
7. Cookies and the website
We use Google Analytics 4 to measure website use and limited product milestones. Ad-performance measurement connects campaign labels and advertising click identifiers to downloads, signups, and subscriptions through Google Analytics and Google Ads. We do not send your writing, screen content, name, email address, payment-card details, or BlinkWrite account ID through this measurement. Google Signals and ad personalisation remain disabled. We do not use user-provided data for enhanced conversions.
7.1 If you are in the EEA, the UK, or Switzerland
The Google Analytics script and optional measurement stay off until you choose. The same rule applies when we cannot determine your country. Analytics and ad-performance measurement have separate controls; advertising measurement also requires analytics. You can accept all, reject all, or manage each purpose.
7.2 If you are somewhere else
Analytics and ad-performance measurement start by default, including in the United States, unless you have opted out. We record this as a regional default, not as a statement that you clicked Accept. We check your country through our own Cloudflare endpoint on each page load. A saved explicit refusal takes precedence. A previous regional default does not bypass the prompt in a consent-required region.
You can change these settings through Cookie settings at the foot of any website page. Turning analytics off stops new browser events and clears optional cookies. Turning ad performance off removes browser campaign attribution and disables the advertising measurement setting. Once the update reaches our API, analytics withdrawal also cancels pending server events. The browser retries when connectivity returns. Withdrawal cannot recall events already delivered to Google. Choices are specific to that browser; other devices may have different choices.
7.3 What is stored on your device
| Item | Purpose | Lifetime |
|---|---|---|
_ga, _ga_YW6ZRMG9BX | Anonymous browser and session measurement | Up to 400 days; removed when analytics is turned off |
bw_consent_v2 | Explicit choices or labelled regional measurement defaults | 180 days |
bw.cookie-consent.v2 | Notify other open tabs about explicit changes; cannot grant measurement by itself | Until browser storage is cleared |
bw_measurement_token | Connect or revoke this browser's server measurement settings | 180 days from the effective setting |
bw_acquisition_attribution | First eligible campaign labels and advertising click identifiers | Up to 90 days; cleared when ad performance is turned off |
apple_signup_attribution | Carry eligible campaign labels through Apple sign-in | Up to 10 minutes |
A legacy refusal stored as bw.cookie-consent.v1 remains effective until changed.
Regional location results are held only in page memory. We do not refresh the
measurement setting's effective date merely because you visit another page.
7.4 What Google Analytics collects, and who sees it
Website events describe page views, download-link clicks, general site interactions, documentation interactions, performance, and general error counts. They exclude search text and raw error messages. A download click does not confirm installation.
When analytics is enabled, a random browser token connects your anonymous Google Analytics browser identifier to your signed-in account. Our database stores a SHA-256 hash of that token. Our servers can then report verified account creation, first observed suggestion use, activation, and trial starts. They can report subscription payments with an invoice identifier, amount, currency, and plan details. Renewal payments are also reported as purchases. The server sends the Google browser identifier, not your BlinkWrite account ID. Events are checked against the current measurement settings before delivery.
When ad performance is enabled, campaign labels and advertising click identifiers can be used to associate these outcomes with ads. We also store eligible acquisition labels and click identifiers on your account when it is created. That account record is retained with the account; changing browser cookie settings does not itself delete previously stored account data. Use the privacy request process in Section 12 to request deletion of previously collected personal data.
Google's data processing terms apply to our Analytics use. Google LLC is in the United States; see Section 10. Our configured Analytics event and user-data retention is 14 months. Server measurement records and the associated event ledger expire after 180 days and are removed by a daily cleanup.
7.5 The web app and the desktop apps
There is no Google Analytics SDK in the BlinkWrite apps, and no Google Analytics page tag on the account pages. Account requests can connect the browser measurement token to your account, and our servers report only the limited milestones described above. Nothing in this measurement sends your writing or screen content to Google.
7.6 If this changes
We publish changes to purposes, recipients, and retention as described in Section 17. We ask for consent where required and preserve existing explicit opt-outs.
8. Usage records
Our servers count what the app asks for: per day, and per kind of suggestion, how many suggestions were requested, how many you accepted, and how many tokens were used. They also keep a record of each suggestion: its type, your plan, when it was generated, and whether the app showed it, you accepted it, or it was dismissed, with a short reason when the app discards one.
On the Free plan, these records also hold when your allowance period started, how much of each allowance you have used, which feature reached its limit and when, whether the limit notice was shown, and the request fingerprint described in Section 2.5.
These records contain no message content. They record that something happened, not what you wrote. They are kept against your account, because that is what makes them useful — they are what enforces the limits of your plan and what fills the usage view in your account.
The detailed counts remain in our own database. When analytics is enabled, our servers derive the first-use and activation milestones described in Section 7 from these counts. There is no Google Analytics SDK in the BlinkWrite apps, and they do not send your device model, operating system version, or app version to Google.
Counts and per-suggestion records are kept for 14 months and then deleted. Two small records are kept while your account exists: the date your Free allowance started, and the allowance period in which you first reached a Free limit, so that the emails in Section 8.1 go out once per account. These records are what produce the aggregate numbers our Terms of Service §6 refers to.
8.1 Emails when you reach a Free limit
The first time you reach a Free limit, we may email you: once when it happens, and up to twice more within the following week, telling you when your allowance resets and how Pro works. The follow-ups go only if you have used BlinkWrite in the previous seven days. They stop when your allowance resets, when you move to Pro or a trial, or when you opt out. This happens once per account, not every month.
Upgrade emails are on by default. You can turn them off at any time in Plan & Billing, or with the unsubscribe link in any upgrade email. Turning them off does not change your plan. Emails about your account's security and your payments are separate and are not affected.
We send these emails through Amazon Web Services. If it reports that your address bounces, or that you marked one of our emails as spam, we stop sending upgrade emails to that address.
9. Who else sees your data
We use the service providers and provider categories below. Their roles include application hosting, LLM generation, service security, payments, and optional measurement. Applicable data processing terms govern their processing. Where a provider acts as a separate controller, its own terms and privacy policy also apply.
| Who | What they do | Where | What they can see |
|---|---|---|---|
| Amazon Web Services, Inc. | Application hosting, our database, supporting services, and sending our email | United States | Account, subscription, usage, and technical data, and the emails we send you. Message text passes through memory during a request and is not stored. |
| External LLM provider | Generates writing suggestions and performs service safety monitoring | United States and other locations permitted by the provider terms | Masked drafts, conversation context, display name, instructions, and suggestions. Production API response storage is disabled; the retention in Section 2.5 applies. |
| Stripe, Inc. and its affiliates (shown as Link at checkout) | Merchant of record — payments, tax, invoicing | United States and Ireland | Name, email, billing address, card details, transaction history. Stripe is a controller in its own right for the payment; its own privacy policy applies. |
| Cloudflare, Inc. | CDN and reverse proxy in front of our website, our web app, and the endpoint the app sends suggestion requests to | United States and globally | Web request logs, including IP address. Suggestion requests pass through Cloudflare in transit, so the masked text passes through it too. It does not store the contents of a request, and keeps no copy of your text. |
| Google LLC and Google Ireland Limited | Website analytics, limited product milestones, and ad-performance measurement — see Section 7 | United States and Ireland | Website events, browser/session identifiers, campaign labels and click identifiers when ad performance is enabled, limited product milestones, and subscription payment amounts with invoice identifiers. No writing, screen content, name, email address, or payment-card details through this measurement. |
Google appears above for the optional measurement described in Section 7. If you use Apple or Google sign-in, that company verifies your identity as a separate controller. Its privacy policy covers the records that it keeps about the sign-in. See Apple's privacy policy or Google's privacy policy, and see Section 4.1. Apple is not on the processor list.
For more information about the LLM provider and its processing arrangements, contact [email protected]. We do not opt in to provider training on API content.
We will also disclose data where we are legally required to — in response to a valid court order, subpoena, or lawful request from a public authority. We will tell you if that happens, unless we are legally barred from doing so. Our application does not maintain a production writing history. The LLM provider can retain content under Section 2.5 and can be subject to legal requirements concerning that content.
If we are ever acquired or merged, your data may transfer to the acquirer. We will tell you beforehand, and this policy will continue to apply until you are given notice of a new one.
We do not sell your personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under California and other US state privacy laws.
10. Where your data is processed
BlinkWrite application servers and the account database run in a United States region of Amazon Web Services. We do not currently operate application infrastructure in Europe. Our external LLM provider can process data in the United States and other locations permitted by its terms. We do not promise EU-only LLM processing.
If you are in the EEA, the UK, or Switzerland, that means your data is processed in a country whose surveillance and privacy laws differ from your own, and which the European Commission has not found to provide an equivalent level of protection generally.
We take these steps as a result:
- The GDPR and UK GDPR apply to us and we comply with them, because we offer the service to people in Europe (Article 3(2) GDPR). Being in the United States does not exempt us.
- Where a transfer to one of our service providers requires a safeguard, we use the European Commission's Standard Contractual Clauses (Decision 2021/914) and, for the UK, the International Data Transfer Addendum.
- On-device masking and disabled production API response storage reduce the content retained for the service. Provider retention under Section 2.5 still applies, including its legal and safety exceptions.
- The optional website, product-milestone, and ad-performance data described in Section 7 goes to Google in the United States. The transfer safeguards in Google's data processing terms apply. In the EEA, UK, and Switzerland, optional measurement requires your choice before it is enabled. Your writing and screen content are excluded.
11. How long we keep things
| Data | Kept for |
|---|---|
| Message text and generated suggestions | BlinkWrite: no production application database or content logs. LLM provider: up to 30 days for abuse monitoring, with legal/safety exceptions; encrypted prompt-cache data up to 24 hours. See Section 2.5. |
| Screen images | Never transmitted; discarded on your computer right after use |
| Account and subscription data | While your account exists. Erased when you close it — see Section 11.1. |
| Acquisition attribution stored on your account | While your account exists, subject to deletion requests |
| Server measurement settings and event ledger | 180 days from the effective setting; removed by daily cleanup after expiry |
| Google Analytics event and user data | 14 months in the property configuration |
| Session records | Until the session expires or you sign out |
| Usage counts and per-suggestion records, including Free request fingerprints | 14 months, then deleted |
| Your Free allowance start date, and the allowance period in which you first reached a Free limit | While your account exists |
| Email preferences, and the record of upgrade emails sent | While your account exists |
| Support tickets, feedback, and setup events | While your account exists |
| Early-access list email | Until you ask us to remove it. It is not linked to your account. |
| Download link email address | Not stored. We use it only to send the link, and keep a one-way fingerprint of it for one day to limit repeat requests. |
| Memory and cached suggestions on your computer | Memory until you delete it or uninstall BlinkWrite; cached suggestions up to 60 days |
| Security and access logs (IP, timestamps, error codes) | 12 months — long enough to investigate an incident or abuse pattern found some months after it happened |
| Terms-acceptance records | Kept after the account is closed, as proof of what was agreed |
| Trial fingerprint | Kept after the account is closed, so the one-time trial stays one-time |
| Deletion record | Kept after the account is closed, so we can show the deletion was carried out |
| Invoices and tax records | Held by Stripe, for as long as tax law requires |
11.1 Closing your account
You can close your account from the web app, or by emailing [email protected].
It is a hard delete, not a hidden flag. Your profile, your sessions, your subscription record, your usage records, your Free plan records, and your email preferences are erased immediately, and your Stripe customer is deleted, which cancels any active subscription.
One qualification, because "immediately" should mean what it says: our database takes routine encrypted backups, which are kept for 14 days and then expire. Your data is gone from the live service the moment you close your account, and ages out of those backups within a fortnight. We do not restore a backup to recover a deleted account.
Three things survive, deliberately, and this is the complete list:
- an irreversible hash of your email address, so the one-time free trial cannot be taken again by deleting the account and signing up with the same address. It is a one-way fingerprint — it cannot be turned back into your address, and it is useless for identifying you. Lawful basis: Art. 6(1)(f), fraud prevention;
- a dated record that a deletion happened, with no personal data in it, because we have to be able to show we honoured the request (Art. 5(2) GDPR);
- the record of which terms you accepted and when, because we have to be able to show what was agreed even after the account is gone (Art. 7(1) GDPR). It carries no IP address and no user agent.
If you joined our early-access list, that email address is kept separately until you ask us to remove it.
Stripe keeps past invoices, which it is required to do by tax law.
Closing your account is permanent. You cannot reactivate it or recover your settings, and a new account would not come with another free trial — that is what the fingerprint above is for.
Closing your account does not remove the app from your computer. That is a separate step, below, and either one can be done without the other.
11.2 Removing BlinkWrite from your Mac
Everything BlinkWrite stores on your Mac can be removed from the app itself: Settings › General → Uninstall BlinkWrite. It removes the app, the on-device model it uses to mask personal information, your settings and per-app rules, your Memory, the sign-in credential held in your Mac's Keychain, and the Accessibility and Screen Recording permissions it was granted. Nothing is left for you to find and delete by hand.
Dragging the app to the Trash removes only the app, and leaves the rest in place.
Uninstalling is local and does not close your account. To do both at once, tick Also delete my BlinkWrite account in the uninstall confirmation.
11.3 Removing BlinkWrite from a Windows PC
Uninstall BlinkWrite from Windows Settings → Apps. This removes the app and what it stored on your PC, including your settings and Memory. It does not close your account or sign the PC out. You can remove the PC from your account under Computers on your account page.
12. Your rights
12.1 If you are in the EEA, the UK, or Switzerland
You have the right to:
- know what we hold about you and get a copy of it;
- have it corrected if it is wrong;
- have it deleted;
- restrict or object to our processing, including any processing based on legitimate interests;
- take your data elsewhere in a machine-readable format;
- withdraw consent at any time, for anything we do on the basis of consent — which does not affect what we did before you withdrew it.
How to use them: email [email protected]. We will respond within one month. If a request is complicated we may take up to two further months, and we will tell you within the first month if that happens. It costs nothing.
We may need to confirm who you are before we act, so that we do not hand your data to somebody else.
Complaints. You can complain to the data protection authority in the country where you live, work, or where you think something went wrong. We would rather you came to us first, but you do not have to. Because we have no establishment in the EU, there is no single lead authority for us — your own national authority is the right one.
12.2 If you are in California
We are a California company, so we will say this plainly: we do not sell your personal information, we do not share it for cross-context behavioural advertising, and we do not use it for profiling that produces legal or similarly significant effects. There is no "Do Not Sell or Share" mechanism on our site because there is nothing to opt out of.
You may request to know what we collect and disclose, delete it, correct it, and receive a portable copy. You may name an authorised agent to act for you. We will not discriminate against you for exercising any of these rights — your price, your plan, and your service stay the same.
Contact [email protected]. We verify identity before acting and respond within 45 days, extendable once by a further 45 with notice.
12.3 If you are in another US state
Colorado, Connecticut, Virginia, Texas, Oregon, Montana, and a growing number of other states give residents comparable rights to know, delete, correct, and obtain a copy of their data, and to appeal a refusal. We extend those rights to everyone in the United States regardless of where you live, because operating one process is simpler than operating fifteen. Use the same address: [email protected].
12.4 If you are in Canada
You may request access to your personal information and ask us to correct it. If you are not satisfied with how we handle a complaint, you may escalate to the Office of the Privacy Commissioner of Canada or to your provincial privacy commissioner.
13. Security
We protect data in transit with TLS and at rest with encryption. Access to production systems is limited to the people who need it, requires multi-factor authentication, and is logged. Payment card details are handled by Stripe and never reach our systems. For email sign-in, we use salted scrypt hashes and never store plaintext passwords.
Our application does not maintain a production writing history. On-device masking and disabled production API response storage reduce exposure. These controls do not remove the provider retention described in Section 2.5.
No system is perfectly secure, and we do not claim otherwise. If a breach occurs that puts your rights at risk, we will notify the relevant authority within 72 hours where the law requires it, and tell you directly where the risk to you is high.
14. Children
BlinkWrite is for adults. You must be 18 or over to use it, and we do not knowingly collect personal data from anyone under 18. If we learn that someone under 18 has an account, we will close it and delete the data. If you believe a child has given us data, tell us at [email protected].
15. Automated decisions and AI
BlinkWrite generates text with AI models. It does not make automated decisions about you that produce legal effects or similarly significant effects, and there is no profiling of that kind anywhere in the product. Nothing here decides whether you get a service, a price, or a credit line.
Every suggestion is exactly that — a suggestion. It appears, you accept it or you do not, and nothing happens without your keystroke.
AI output can be wrong. That is covered in our Terms of Service §7.
16. Contact us
Privacy questions, and any request under Section 12, go to [email protected]. So does everything else — it is one address and it is read.
17. Changes to this policy
We will update this policy as the product changes. Each version is published with a version identifier, an effective date, and a note of what changed. Every past version stays available at its own address, so you can always read exactly what applied when — see previous versions. We keep a record of which version you accepted and when.
If a change materially affects how we handle your data — a new category collected, a new purpose, a new recipient, or a longer retention period — we will email you at least 30 days before it takes effect, and ask you to accept it. The new version is published at its own address during that notice period, so you can read it before it applies. If the change requires your consent, we will ask for it rather than assume it.
Editorial changes — typos, formatting, clearer wording that changes nothing about what we do — are published as a new version without asking for a new acceptance.
We will not make a change that lets us train our AI models on your content, or sell your personal data, without your express opt-in consent. Those two commitments are the point of this document.
Previous versions
- 2026-09-13Effective 13 September 2026 · Explain regional analytics choices, ad attribution, limited product milestones, subscription measurement, and the Free plan's usage records and upgrade emails.
- 2026-09-03Effective 3 September 2026 · Documented the in-app uninstall, which removes BlinkWrite and everything it stored on your Mac.
- 2026-08-24Effective 24 August 2026 · Added email sign-in and password-security details before publication.