Privacy & terms

Privacy policy

What this website collects

If you joined the waitlist (the form is no longer on this site; the beta download replaced it), we store the email address you typed, the time you submitted it, and the path of the page the form was on. When the visit has them, we also store the referring site, the campaign parameters in the link (utm_source, utm_medium, utm_campaign, utm_content, utm_term), and a ref code. A repeated email does not create a second row.

We also count a few anonymous events so we can see whether the page is doing its job: a page view, the demo starting, a signup starting, succeeding or failing, and a click through to the privacy or verify page. Those rows have no email and no IP address.

waitlist(email UNIQUE, created_at, source, referrer, utm_*, ref) · events(name, path, attribution) · Cloudflare D1

What this website does not do

• No third-party analytics, advertising pixels, fingerprinting, or session recording.
• No tracking cookies. The one cookie this site sets is the short-lived beta download session described below, and only after you send the beta form. Your theme preference stays in localStorage if you change it. Campaign parameters for this visit stay in sessionStorage so the signup can include them. Neither is sent anywhere except the two requests above, to this site.
• No fonts, scripts or images loaded from third parties, with one exception below.

The exception: anti-spam

The waitlist form uses Cloudflare Turnstile to reject automated submissions. The Turnstile script loads only when the form comes into view or is focused, from Cloudflare, which also hosts this site. Cloudflare processes the request as our provider under its own privacy policy. We receive a pass/fail token, nothing more.

The beta download

If you use the form at /beta, we store your email address, the platform you chose (Mac or Windows), when you first sent the form and when you last sent it. We use it to know who is testing the beta and, if a build has a serious problem, to write to you about it personally. No newsletter, no mailing list, never shared or sold. This site sends no automated email.

Before we store the address, we check that it looks valid, that its domain is not on a public list of disposable-inbox providers (a copy kept with this site), and that the domain can receive email. That last check asks Cloudflare's public DNS resolver about the domain only, never the full address.

To stop abuse, the beta forms count requests per IP address and per email address. The counter table holds a keyed hash of each, never the IP address or the email itself, and the counts are deleted within 24 hours. The same Turnstile check described above protects the beta forms.

Sending the form sets one cookie, fry_dl: signed, HttpOnly, limited to this site, and expired after 2 hours. It only lets this browser open the download page at /download and the files, and is strictly necessary for that. Without it, /download sends you back to the form at /beta. The installers are served by this site from our private Cloudflare storage; no third party is involved in the download.

When you click Update in the app, it asks askfry.com/updates/latest.json and, after a second click, downloads the update from this site through a link valid for one hour. That is the one network call from the app that reaches this website, and it is listed as the update host on the verify page. We do not log or store anything about those requests.

Feedback sent from /feedback is stored with the time you sent it, plus the rating, platform, version and email if you gave them. If you leave the email empty while the download cookie is still valid, we attach the address you gave on the beta form. No IP address.

Ask us to delete your beta signup and feedback at any time; both are removed from the database. Legal basis: your request for the download, and our legitimate interest in improving the beta.

beta_signups(email UNIQUE, platform, created_at, last_seen_at) · beta_rate_limits(keyed hash, count, 24 h) · beta_feedback(email, platform, app_version, rating, text, created_at) · Cloudflare D1

The feedback bubble

If you send a message from the feedback bubble at the bottom of each page, we store the message, your email address, the page you sent it from and the time. We forward a copy to our own inbox and to our team’s notification channel so we can reply. We use your email only to answer you. No IP address. The same Turnstile check described above protects it, and loads only when you open the bubble.

Ask us to delete a message at any time and the row is removed. Legal basis: your request to contact us.

feedback(email, message, page, created_at, delivery status) · Cloudflare D1

Where the data lives and who sees it

The waitlist and the anonymous event counts live in a Cloudflare D1 database in our Cloudflare account. Cloudflare is the processor; we are the controller. Nobody else has access. Server logs at Cloudflare's edge may contain your IP address for a short retention period as part of operating the network; we do not export or analyse them.

What we use the email for

Occasional notes about major updates. No newsletters, no partner offers, no resale. Reply to any message to be removed and the row is deleted.

Your rights

You can ask what we hold about you, ask for it to be corrected, or ask for it to be deleted, at any time, by writing to [email protected]. Because the record is a single row, the answer is fast. If you are in the EU or UK, you also have the right to complain to your supervisory authority.

Your content never reaches us

Since version 1.0.65, AskFry sends anonymous, allowlisted usage counts to help us improve it. They are on by default: opt out on the first-launch screen or anytime in Settings › Privacy › Usage stats. None are recorded or sent in Paranoid mode. Never your searches, files or content. You can see exactly what is sent; the full list is on the verify page. Nothing AskFry reads is visible to us. Every network call AskFry can make is listed on the verify page. Apart from the update check described above, none of them reaches this website.

Since version 1.0.68, AskFry can answer AI apps you connect to it over MCP. It is off by default and set per app, search is a separate opt-in, and nothing works in Paranoid mode. AskFry's MCP server talks to the AI app over stdio and to AskFry over a local socket (a Unix domain socket on Mac, a named pipe on Windows); it opens no network port. The only listening network socket the app ever opens is the temporary sign-in callback, closed after the flow. What an allowed AI app receives goes to that app's AI provider unless the AI runs locally; none of it comes to us. Every request is recorded in the app's local audit log, without the search text. Details on the verify page.

Legal basis

Consent, given when you submit the form under the one-line notice beneath it. Withdrawing consent removes the row.

contact: [email protected]

Terms

Stub. A fuller version will replace this before the app leaves beta.

This website

The content on this site is provided as information about a product in development. Features and dates described here are indicative and may change. Nothing on this site is a contract to deliver the product.

The waitlist

Joining the waitlist creates no obligation on either side. You may leave at any time.

The desktop app

The app is in public beta: send the form at /beta to reach the download page at /download. Beta builds aren't signed by Apple or code-signed for Windows yet. Its licence terms are not published on this site.

Liability

This site is provided as is. To the extent permitted by law, we accept no liability for decisions taken on the basis of its content.

Contact

[email protected]