offloadSign in

Last updated 30 October 2026

Privacy policy

offload only works if you put real material into it, and you should only do that if you know where it goes. This page says where it goes.

The short version

This summary is not the policy. Where the two differ, the sections below count.

  • What you put in is yours. We do not sell it, rent it or use it for advertising.
  • We do not use your content to train models, and the companies that process it for us are bound not to either. A few act for themselves, as section 6 says.
  • Only what a task needs goes to the companies that help run offload. They are listed on their own page.
  • Delete anything, or your whole account, whenever you want. What you put in a shared thread stays with the people in it. Section 9 says why.
  • Take it all with you. You can export everything yourself, in Settings.
  • The files you put in are encrypted by us. Your text is not. Section 14 is exact about it.
  • offload is for adults in the United States.

1. Who we are

offload is not a company yet. It is run by Behrooz Afghahi, an individual in the United States. This page will name the company when there is one. “We” on this page means him and anyone who helps him run offload.

offload is only offered in the United States, to people aged 18 and over. Write to us about anything on this page at hello@offload.club.

2. What this covers

The offload apps, the web app, and this website. Sites and services a link takes you to have their own policies.

3. What we collect

What you give us

  • Your email address and name, from the service you sign in with. You can change your name in Settings.
  • If you join the waitlist, the email address you give it, which we keep until you are invited or ask us to remove it.
  • Everything you put in: notes, links, photos, screenshots, documents, voice notes, what you type to offload, and email you forward to it, with who sent it and when. Files can carry details the device that made them wrote into them, such as when and where a photo was taken; we keep those with the file.

What offload makes from it

  • How it is organised: the threads and labels it files things into, and the dates, places and other details it pulls out, including when something needs a reminder.
  • Transcripts of voice notes, and descriptions of what images and documents show, including the words in them.
  • Notes about a thread, written by you or by offload.
  • Memories: what offload knows about you across your threads, such as the people in your life, how they relate to you, their birthdays, and how you like things done. offload keeps one when you ask it to remember something or answer a question it asked, learns some from what you put in, and you can add your own. It is told not to keep sensitive details, such as your health, beliefs or money, unless you asked it to, and never an ID number or a password. That is a model following instructions, not a guarantee, so you can see and forget every memory in Memories.
  • Its replies to you, with the addresses of the pages it read to answer.
  • Suggestions, and search indexes that make all of this findable.

We advise against putting passwords, card numbers or government IDs into offload, or into any AI tool. offload is asked to leave those out of what it writes down, but that is an instruction to a model, not a guarantee.

What comes from an app you connect

If you connect an app, such as a calendar, offload reads what you choose to give it, keeps what its features need, and writes to it when you ask. Section 7 says more about Google.

What we collect because software has to run

  • Your IP address and a description of your device and browser, kept with your sign-in sessions.
  • Your device’s time zone, so dates mean what you meant. We do not ask your device for its location.
  • The country you set in Settings, if you set one.
  • Records of what each request did, how long it took and what it cost, including each call to an AI model. These are built to hold no content.
  • Product events, such as finishing setting up, under a random identifier that only we can link back to you, until you delete your account.
  • Records of staff access to your account, kept for security.
  • If you turn notifications on, a token that identifies your device, and a record of what was sent to it.

4. Why we use it

  • To run offload for you: store, sort, search, answer, look things up, remind you, show places on a map, send the notifications you choose, and work with the apps you connect.
  • To keep accounts secure and stop abuse.
  • To find out whether offload works and what it costs, from records that carry no content.
  • To email you about your account and about changes to this page.
  • To answer a lawful request, or to establish or defend a legal claim.

First run asks you to agree to offload holding what you put in, which can include private matters, and to it being processed to run offload, including by AI services from other companies. You need that, and an email address, to have an account. If you no longer agree, delete your account; you can take a copy first.

5. AI

Sorting, reading, transcribing, looking things up and answering you are done by AI models from other companies, which we call on your behalf. Each call carries only what its task needs: what you just put in, the context needed to file or answer it, such as the recent conversation, your threads and what offload knows about you, and, when offload answers, what it reads from your threads to answer. Not more.

  • No training. We do not use your content to train models. The companies that process your content for us are bound, by their terms or by settings we have turned on, not to use it to train theirs.
  • Looking things up. When offload needs a public fact it does not hold, it may search the web and read pages, including a link you pasted. A search uses words from what you put in, and your country if you set one, and never what offload knows about you. A site offload reads sees a request from us or from the company doing the reading, not from you, though your device may load a picture from it. You can turn searching and link reading off in Settings under Privacy; offload still asks a site you link to for the picture it shows beside the link.
  • Places. When something you keep names a place, the place’s name, on its own, goes to a maps service to put it on a map.
  • Automated decisions. Filing is automatic, which is the point of offload, but it has no legal or similarly significant effect on anyone. You can see and correct everything offload does.

6. The companies that help us run offload

We use a small number of companies, for things like hosting, storage and backups, AI models and web search, search indexing, transcription, email, building the apps and sending notifications, signing in, maps, and the apps you connect. The current list, with what each does and receives, is on the companies page, which has its own date.

Most process data only to provide their service to us, under terms that require them to protect it. Some act for themselves under their own terms: the service you sign in with, a calendar you connect, which stays in your own account, and Google Maps Platform, which draws maps and finds places by name. It receives a place’s name from us with nothing about who asked. From your device while a map is on screen, it receives your IP address, device details, an identifier, how the map is used, and crash and performance reports. Its terms allow it to keep that and use it to improve its products, and it may recognise you if you are signed in to Google.

We keep the list current. If a change would materially change how your content is handled, offload tells you the next time you open it and asks you to agree again before you go on.

7. Google user data

If you connect a Google account, offload accesses your calendar list, the events in the calendars you choose, and who your calendars are shared with. It uses them to show your calendar in offload, to file and answer from it, to mention your events in the notifications you choose, and to add, change or delete events when you ask, and it asks you first before a change that would notify other people. We keep only what those features need, delete it when you disconnect or delete your account, and ask Google to revoke our access when you delete your account. What offload already wrote in your threads from your calendar stays until you delete it.

Calendar data goes only to the companies on our list that are needed to provide those features, and to the members of a shared thread you choose to show a calendar in.

offload’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, we do not sell it, and we do not use it to develop, improve or train AI or machine learning models. Nobody at offload reads it unless you have agreed to that for the specific data, for example to fix a problem you reported, it is needed for security, or the law requires it.

8. Other people in offload

  • You can share a thread with a connection: someone you have both agreed to connect with. There are no public links.
  • Everyone in a thread can read everything in it and add to it, and sees your name next to what you add.
  • Somebody who knows the email address you signed up with can ask to connect with you. They cannot see anything you have put in.
  • A calendar you show in a shared thread is visible to its members while it is shown.
  • A document in a shared thread opens for its members as a clean copy, without hidden details such as who made it.

9. Shared threads, and deleting

Sharing is deliberate: one thread, with people you already know. What you put in a shared thread becomes part of a record the other members rely on, so it stays with them when you leave the thread or delete your account. Taking it out would leave them with gaps and delete information about them on your instruction.

While you are in a thread, nobody else can delete what you wrote, and you cannot delete what they wrote. Any member can export the thread as they see it, and any member can take another out. Once you leave, what you left becomes the thread’s, and the others can edit or remove it. When the last member leaves, the thread is deleted.

We show you this when you share a thread. If you want something to stay entirely yours, keep it in a thread you have not shared.

10. If someone else asks for your data

A court, a regulator or the police can compel us to disclose data. We hand over only what a valid request requires, we push back on requests that are not valid or go too far, and we tell you before we do, unless the law forbids it or there is no time, in which case we tell you when we can. We hold the keys to what we encrypt, so a request to us can reach your files as well as your text.

11. If offload is bought or merges

Whoever ends up holding your information is bound by this page. Anything weaker needs your agreement first. We email account holders before a change of ownership completes, with time to take a copy and delete the account.

12. Where it is kept

offload runs in the United States. Some of the companies on our list may process data in other countries, under the terms section 6 describes.

13. How long we keep it

  • What you put in, and what offload makes from it: for as long as your account exists, or until you delete it. Nothing expires on a clock, because finding something from years ago is the point. A memory that is replaced is kept for a short time and then deleted.
  • What you delete is deleted. It is removed from our live systems promptly, and from our backups when they expire, which they do on a short, regular cycle.
  • Data from a connected app: while it is connected, and only the part offload is using. Its copy goes when you disconnect or delete your account; what offload already wrote in your threads from it stays until you delete it.
  • Working records, such as what offload keeps so a change can be undone, or a list of the notifications it sent: only as long as the feature needs them.
  • A copy you export: long enough for you to download it, then it is deleted.
  • Logs and usage records: server logs for a limited period set by our host. Records of what requests did and cost are kept to understand cost and reliability over time. They hold no content, and nothing links them to you once your account is deleted.
  • Security records, including staff access to your account: for a fixed period long enough to look into a problem, then deleted.
  • Product events: kept to see how offload is used over time, and deleting your account destroys the identifier that links them to you.
  • The companies on our list keep what we send only as long as their service needs, under their terms, except those that act for themselves, as section 6 says.

14. Security

We would rather make a narrow claim that is true than a broad one that sounds better.

Encrypted by us: the files you put in, such as photos, screenshots, documents, voice notes and what is attached to email you forward, before they are stored, with keys our storage provider never receives. Our own backups and your exports are encrypted too, with keys our storage provider never receives. A file you open is decrypted so your device can show it. We hold the keys, so this protects against a breach at our storage provider, not against a compromise of offload itself.

Our host’s recovery copies of the database are protected by its encryption, as the database is, not by ours.

Not encrypted by us: the text in offload, including transcripts and what offload writes about your files. It sits in our database protected by our host’s disk encryption and access controls. Someone who obtained a copy of our database could read it.

Access to your data is checked on our servers for every request. Only a few people can reach production, and they read your content only when you ask for help or a specific fault requires it, and Google user data only as section 7 allows. Our staff tools show no content, and their use is recorded. Our logs, analytics and monitoring are built to carry no content. Notifications are the exception: they carry a few words of what is in your threads, what offload remembers for you, or your calendar, which somebody else may have written, to your own device.

15. Health information

offload does not ask for health information. If you put some in, it is treated like everything else you put in: used only to run offload for you, never sold, never used for advertising, and deleted when you delete it. The companies on our list receive it only as section 6 says, and deleting it removes it from them and from our backups as section 13 says. offload is told to keep it as a memory only when you asked it to, and you can forget any memory in Memories.

16. Your choices and your rights

In Settings you can export everything, delete your account, turn web search and link reading on or off, connect or disconnect apps, and choose your notifications. You delete something you put in, or a thread, where it is. How deleting an account works. In Memories you can see, add, change and forget what offload knows about you, and your export includes them.

Wherever you are in the United States, you have the right to know what we collect and why, to a copy, to correct it, and to delete it, and we will not treat you differently for asking. You may use an authorised agent. Write to hello@offload.club. We answer within the time the law gives us, and may need to confirm it is you, usually by having you write from the address you sign in with. One limit on deleting: section 9.

If we turn a request down, we say why, and you can ask us to look at it again by replying. If you are still unhappy with the answer, you can contact your state attorney general.

We do not sell your personal information or share it for cross-context behavioural advertising. We use sensitive information only to run offload for you.

17. If you are not on offload

What people put in can mention you: an event you are invited to, an email you sent that someone forwarded, a note with your name in it, or a memory of theirs that says who you are to them or when your birthday is, which offload can mention in a reminder to them. We hold that only as part of their account, for the purposes above, and the same retention and security apply. To ask about it, write to hello@offload.club.

18. Cookies and tracking

offload sets what it needs to sign you in, keep you signed in and stop abuse, and your browser or phone keeps your display preferences on your device, and your recent searches until you sign out. There are no advertising cookies and no third-party analytics in your browser, so there is no banner. We do not track you across other sites, so we treat a Do Not Track signal the way we treat everyone. Others can see your device’s requests while you use offload: the maps service while a map is on screen, which may recognise you as section 6 says, and a site whose picture is shown for a link.

19. Age

offload is for people 18 and over. If we learn an account belongs to someone younger, we delete it. Tell us at hello@offload.club if you think that has happened.

20. Changes to this page

When we change this page we change the date at the top. If a change materially affects how your information is handled, offload tells you the next time you open it and asks you to agree again before you go on. The list of companies has its own date and changes there.

21. Contact

hello@offload.club. We have no postal address to give yet.