Privacy policy

Your account

Your email address, your handle and display name, and a profile photo if you add one. To sign you in, we keep your passkeys (only the public part), your password if you set one (only as a one-way hash), the one-time codes and links we email you, and any API tokens you create for the fffd CLI or the MCP server. We also keep which app you signed up in, a record of each time you sign in, and your email preferences.

Your files

The files you upload, and everything you add to them: names, folders, tags, favorites, playlists, galleries, file requests, review links, and who you share them with.

Details read from your files

Software reads some of what's inside your files to power the map, the players and each file's details. From photos and videos, that's the dimensions, camera, date taken and, if the file includes it, where it was taken. Videos get a thumbnail. From audio, it's the tags (like title and artist), album art, and measurements of tempo, key, loudness and peak levels, including whether a lossless file was made from a compressed one. We don't browse your files, and we only access one when you ask us for help with it, when it's reported for abuse, or when the law requires it.

Searching inside files

Only if you turn it on: what's said in your audio and video, what your pictures and video scenes show, and the text of your documents and pictures, kept as short passages with where in the file each one is, so you can search for them. We also keep how much reading used each month, which your plan's allowance is held to. It's off until you turn it on.

AI images

The prompts you write, the model and settings you choose, and the images that come back, which are saved privately in your library.

Connected apps

When you connect an app like Claude or ChatGPT to your drive, we keep which app it is, how much of your drive you let it reach, when that ends, and when it was last used. Its tokens are kept only as one-way hashes. Each time a connected app, or an API token used with our hosted MCP server, uses a tool in your drive, we log which tool, whether it worked, and a short note of what it touched. You see that log on the Agents page.

Folders you share with someone's AI

When you share a folder with someone else's AI, we keep the folder, who you said it's for, when it ends and when it was last used. The secret in its link is kept as a one-way hash, and encrypted with a key only our agent's server has, so you can copy the link again. Each time their AI uses a tool through the link, we log which tool, whether it worked, and a short note of what it touched, on your Agents page.

Standing orders

When you set up a standing order, something your drive does by itself each time files arrive, land in a folder or get notes, we keep what you asked for, the steps it was planned into, what it watches, the model that planned it and what that cost. Its token is kept as a one-way hash, and encrypted with a key only our agent's server has. To know when to run them, we note each time files finish arriving at your requests, files are added to your drive, or reviewers leave notes, and which app or token added a file. Each run keeps what set it off, how each step went and what it cost, and what it did shows on your Agents page.

Tasks for our agent

When an app gives our A2A agent a task, we keep the task's messages, what the agent made, the model it ran on and what it cost. For a task that's waiting on something, like files arriving at a request, we keep what it's waiting on, and the address the app asked us to send updates to.

Activity

How much storage you use, and what you play and where you stopped, so we can show your recent plays and pick up where you left off.

Views

When someone other than its owner opens a file, we count it, once a day for each person. If the file was shared with them, its owner sees their name, unless they've turned that off on their account's Profile page. Anyone else, including anyone opening a public link, is counted without a name: we keep a code made from the day and their account, or from their IP address and browser if they're signed out. It can't be turned back into either, and it changes every day. Counting doesn't set a cookie.

Sending to a file request

You don't need an account to send files to someone's file request. We keep the files, the name and the note you give, and when you sent them, and the person who asked sees all of it. From then on the files are theirs. We don't ask for your email address. To stop abuse, we count uploads from your IP address for an hour, in memory rather than in our database. An AI sending them through our connector is counted the same way, by the connection it came through or its address.

Leaving notes on a review

You don't need an account to leave notes on a video or track someone sent you for review. We keep the name you give, your notes and replies, where in the file each one sits, and when you wrote them. The person who asked sees all of it, and anyone else with the link sees your name and your notes. An email address is optional. If you give one, we use it only to tell you when someone replies to your notes, the person who asked sees it too, and every one of those emails lets you stop them. Your browser keeps a pass so the review knows you when you come back.

Payments

Your plan, your subscription status and your billing history. Stripe processes payments, and your card details stay with Stripe.

Referrals

The invitation on what you share publicly, and on your file requests, is your referral link, and it carries your account's id. If someone signs up with it, we record that you referred them, and when their first payment earns you a month. You see how many people joined with your link and how many months you've earned, never who. If you signed up with someone's link, they don't see who you are either.

Messages

Support requests and anything else you send us, and the feature requests you post.

Technical details

Your IP address, your browser and device type, and the request logs our hosting provider records when you use FFFD.

To run FFFD

To store, deliver, play, organize and share your files, generate the images you ask for, measure your audio, draw your map, and serve the fffd CLI, the MCP server, our agent and the API.

To keep it safe

To protect accounts, stop fraud and abuse, and enforce our terms.

To bill you

To charge for your plan and keep the financial records the law requires.

To email you

Sign-in codes, verification, payment and security notices, and important changes to FFFD, plus updates on your feature requests, which you can turn off. When your reviews get notes, we email you what they say. We don't send you marketing email unless you've agreed to it, and every one lets you unsubscribe.

To measure our ads

To see whether our Google ads lead to sign-ups. The section on advertising below explains what that involves.

What we don't do

We don't sell your personal information, and we don't use your files or prompts to train AI models.

The providers who run FFFD with us

Fly.io runs our servers and databases, mainly in the United States. Tigris Data stores your files and serves them from 11 regions around the world, close to the people who open them. Stripe processes payments. Twilio SendGrid sends sign-in codes and other email, with open and click tracking turned off. Each only uses your information to provide their service to us, except that Stripe also uses it to prevent fraud and meet its own legal obligations.

AI image models

When you generate an image, your prompt and settings go to Replicate, which runs the model. For some models, Replicate passes them on to the company that made the model, like Black Forest Labs, ByteDance, Google or OpenAI. Their own terms and privacy policies cover what they receive.

AI text models

When our agent works on a task, plans a standing order or writes a step of one, the task's messages or what you asked the order to do, what our tools return, what set the order off, like a sender's note, and the files it reads or looks at, including photos, video frames and documents, go to OpenRouter. OpenRouter passes them to the company that made the model the task runs on, like Anthropic, Google or OpenAI. We ask OpenRouter to send them only to providers that don't collect them. Their own terms and privacy policies cover what they receive.

Reading your files

When searching inside files is on, we read the text in your documents and the captions in your recordings ourselves. The speech in your audio and video goes to OpenRouter, which passes it to one of the providers that host the Whisper model, like Groq, to transcribe it. The frames, pictures and scanned pages we read go to OpenRouter too, which passes them to Google, whose Gemini model reads them, and for those we ask OpenRouter to use only providers that don't collect them. To search by meaning, the passages read and the words you search for also go through OpenRouter to Google's Gemini embedding model. Their own terms and privacy policies cover what they receive.

Apps you connect

What an app you connect reads from your drive goes to that app, and its own terms cover what it does with it. What someone else's AI reads through a folder you shared goes to their app, and anyone with the link can read the folder until it stops. Updates on a task for our agent go to the address the app that gave it asked for.

Google

For measuring our ads, as described below. The app and our docs also load fonts from Google's servers, and the app loads some of its code there too, so Google sees your IP address when they do.

OpenStreetMap

The map loads its tiles from OpenStreetMap, which sees your IP address and the part of the map you're looking at.

Other people

Your handle, display name and photo are public, and anyone can look you up by them. Your public profile shows the playlists, galleries, audio and video you've made public, and the feature requests you post are public too. Anyone can open a public file, playlist or gallery, and people you share a file with can open it. Anyone with a file request's link sees its title, its message and your display name, and can send you files until you close it. Anyone with a review's link can play its file, even a private one, and sees your display name, your replies and everyone's notes, until you close it. When you open a file someone shared with you, they can see you did, unless you turn that off.

When the law requires it

We disclose information when a law, subpoena or court order requires it, and we'll tell you when we're allowed to. We report apparent child sexual abuse material to the National Center for Missing and Exploited Children, as US law requires, and keep what we report for as long as the law says.

A new owner

If Absurd Technologies is sold or merged, your information may move to the new owner. We'll tell you first and give you the chance to delete it.

We run ads on Google. To see which ads lead to sign-ups, the FFFD website and app load Google's ad tag. It sets cookies and tells Google about your visit, and about when you go on to open the app, sign up or subscribe, so Google can match them to ad clicks. We don't send Google your name, your email address or your files. Google's use of this information is covered by Google's privacy policy.

Opting out

If your browser sends Global Privacy Control, or it's set to a time zone in the EU, the EEA or the UK, we don't load Google's ad tag at all. You can also limit ad personalization in your Google account's ad settings, or block cookies in your browser. Under California law this measurement can count as "sharing" personal information for advertising, and Global Privacy Control is how you opt out of it.

Cookies

Google's ad tag is the only part of FFFD that sets cookies. The app keeps you signed in and remembers your settings in your browser's own storage, and a review you leave notes on remembers you the same way.

When you make a file public, anyone with its link can open it, and they get exactly the file you uploaded. That includes anything stored inside it, like where a photo was taken. If you don't want that seen, remove it from the file before you share it. Anyone who opens a public playlist or gallery can open everything in it, even files you've kept private.

Taking sharing back

Making a file private again stops its public link, though a copy may be served from a cache for a short time. Moving a public file to the trash doesn't stop its link until it's deleted for good, so make it private first. A private link you've already shared keeps working until it expires, 6 hours after it was made.

Files

Until you delete them. A deleted file waits in the trash for 30 days, then it's permanently deleted from storage. Deleting it from the trash, or emptying the trash, deletes it right away.

Your account

Until you ask us to delete it. We then delete your account and all your files within 30 days.

If your plan ends

Your files stay where they are. You can't upload until you subscribe again, and you can still download everything with the fffd CLI or the API. Our terms explain when we may delete the files of an account without a plan, and we'll always email you first.

Backups

We back up our database, which holds account details and file details but not the files themselves. Backups are thinned out as they age, and each one is deleted within a year. If we ever restore one, we delete again anything you'd already asked us to delete.

Everything else

Your prompts, images, play history and messages are kept until you delete your account, or until you delete them yourself. A file's views are deleted with the file, and the views you made by name are deleted with your account. The names and notes people send with files to your file requests are kept until you delete the request. The names, email addresses and notes left on your reviews are kept until you delete the review or its file, and reviewers can delete their own notes. Our hosting provider keeps technical logs for a limited time.

Searching inside files

What was read in a file is kept for as long as the file is, and forgotten when you delete the file or turn searching inside files off. How much reading you used each month stays with your account.

Connected apps

An app you connect, its log and the tasks it gave our agent are kept while it's connected. Once you disconnect it, or its access ends, they're deleted 90 days later, or sooner if you delete the app on the Agents page. Deleting your account deletes them too. The app that gave a task can remove its update address at any time.

Folders you share with someone's AI

A share and its log are kept while its link works, and deleted 90 days after you stop it or it ends, or sooner if you delete it on the Agents page. Deleting your account deletes them too.

Standing orders

What happens in your drive is noted for 30 days, so a standing order can run on it, and then deleted. A standing order and its runs are kept while it stands; each run is deleted 90 days after it, and the order and its runs 90 days after you stop it, or sooner if you delete it on the Agents page. Deleting your account deletes them too.

Records the law requires

Billing and tax records, and anything we've reported to the authorities, for as long as the law requires.

Get your data

Download your files in the format you uploaded them: in the app while you have a plan, and with the fffd CLI or the API at any time. Email us for a copy of your account details.

Correct it

Change your display name and handle in your account settings. To change anything else, like your email address, email us.

Delete it

Delete files in the app, with the fffd CLI or through the API. To delete your account and all your files, email support@freakingfast.io and we'll do it within 30 days.

What's required

You need an email address and a handle to have an account. Everything else is up to you. No decision that has legal or similarly serious effects on you is made by software alone.

In the EU and UK

You can also object to or restrict how we use your information, withdraw consent you've given, and complain to your data protection authority.

In California

You can ask what we collect, and ask us to correct or delete it. You can opt out of the "sharing" described under advertising with Global Privacy Control. We don't sell personal information, and we won't treat you differently for using these rights.

How to ask

Email support@freakingfast.io. We may need to confirm it's you, and we'll reply within 30 days.