Version 2026-11-19
Privacy
We keep as little about you as the service needs, store it in the EU, and delete it when it's no longer needed. This page says exactly what that means.
Who is responsible
Programlabbet AB, Lund, Sweden, makes Theirway and is responsible for your personal data. Write to privacy@theirway.app about anything on this page. For anything else, write to hello@theirway.app.
What we store, and why
If you join early access
Your email address, when you confirmed it, and which version of this page you agreed to. We use it to tell you when there's a place for you, and for nothing else. The legal basis is your consent.
If you don't confirm within 7 days, the address is deleted automatically. Once confirmed, it stays until you remove it with the link in the email we sent to confirm it, or ask us.
If you have an account
Your email address, and what's needed to sign you in: sign-in links (valid for 15 minutes), sessions (30 days), and any access tokens you create for your tools or agents. The legal basis is our agreement with you to provide the service.
Your deliveries: the files, their names, the names and email addresses of the people you send them to, and what happened to each delivery (uploaded, opened, downloaded, and when). Tags and notes you add to files are stored with the file in that delivery, shown to the person you send the delivery to, and deleted with the delivery.
If you give a sender name, we show it to the people you email links to, in who the email is from ("Anna Berg via Theirway"). We keep it with the record of each of those emails for seven days, and Lettermint keeps it with each email for up to 28 days. You can change or remove it at any time, and it is deleted with your account.
You can delete a delivery in the app. Deleting it stops it working at once for the people you sent it to: when they open their link they see that you deleted it, and when, and a download link they were already given stops working within an hour. For 30 days you can restore it. After 30 days we erase the delivery: its list of files, the names and email addresses of the people you sent it to, its title and descriptions, its history, and any requests to send its files to a server. If you don't want to wait, you can erase a delivery at once. A file you also use in another delivery stays in storage for that one; any other file is removed from storage about a week after the erasing. What we erased can remain in our database backups for up to 35 days. What stays is that the delivery existed, and when it was created and deleted, with nothing about what was in it, except the record of the changes you made to its files and, if you asked to be emailed when files arrive, the counts in the record of those emails (both below).
You can keep a delivery up to date. You can retract a file in it, with a reason your client reads next to the file, and put it back; or prune a file for good, which keeps a line with its name, its size and, if the file has one, its SHA-256 fingerprint. Your client reads that line where the delivery is shown as a list of files; where it is shown as pictures, the page says only that some files were removed. When you change how a delivery is kept, or retract, put back, prune, release or remove a file, we keep a record of it: what was done, when, whether one of your access tokens did it, which file by its size and, if it has one, its SHA-256 fingerprint, and never by its name (for a removed file, not even those), and the reason you gave for a retraction. When a delivery is erased, the names and your reasons go with it; the fingerprints, sizes and dates in the record stay while your account exists, so what was delivered can be checked against a copy someone kept. When we delete your account, the reasons in the record go within minutes, and the rest of it once it is more than 12 months old. You can also freeze files as a snapshot: a fixed list of them under a tag you choose, with its own links. We keep that list, each file with its SHA-256 fingerprint, and a fingerprint of the whole list, which you and your client can check a download against. Freezing is in the record too, with the fingerprint of the list and how many files and bytes it holds. When a snapshot is erased, its tag and its list go with it, and the fingerprint of the list stays in the record like the other fingerprints; a used tag stays reserved, so it can never name another list (we keep a fingerprint of the tag for that). A snapshot is a delivery of its own: erasing the delivery it came from does not erase it.
If you ask other people for files, with a request link, what they send is stored in that delivery on your behalf. It counts toward your storage like your own files, you can see the name each person gave and the folder their files are in, and it is deleted with the delivery. You are the person who asked: you decide who gets the link and what you do with what comes back.
If you ask us to email you when files arrive on a request, we email you at most once every three hours for that request, through Lettermint, which keeps each email for up to 28 days. It says how many files came and from how many people, and the name each person gave, as they typed it. It never holds a file, a file's name or your message. We keep a record of each of those emails: when it was made, how many files and people it counted, and whether Lettermint took it, with no names in it. That record stays after you erase the delivery, for as long as your account exists. You can turn the emails off for a request in the app, or with one click in any of them.
You can't yet delete your account in the app. Until you can, write to us and we'll delete it.
If someone sends you files
The person who sent them gave us your name and email address, and we handle them on the sender's behalf. We record when you open the delivery, when you start a download, and when the page has handed the files to your browser, so the sender can see it. None of that shows the files arrived. You don't need an account, and we don't use your details for anything else, except one thing that we decide ourselves: we ask Gravatar for a picture to show next to your name (see "Pictures next to names" below).
If the sender asks us to, we email you the link through Lettermint. The email shows the sender's address and the name they chose to show, if any, and a reply goes to them. We record that we sent it and when, and the sender can see that. For seven days we also keep a coded form of your address (not the address itself) with that record, so that no sender can email you more than a few times; then we delete it, even if the sender deleted the delivery sooner. Lettermint tells us whether your mail server took the email. The sender's page tells them whether it did, or that it could not be delivered. If you use "Stop these emails" in it, we keep a coded form of your address so that we don't email it again for anyone, until you ask us to start again, which you can do by writing to us. If it could not be delivered, or you marked it as spam, we keep a coded form of your address so that we don't email it again for anyone. Lettermint keeps the email, link included, for up to 28 days. Anyone who holds the link can open your files, so don't pass it on. If your email program sends your reply to us instead of to the sender, our mail server receives it and we pass your words on to the sender, in an email from Theirway sent through Lettermint, which keeps that email for up to 28 days. We do this only for a reply from the address we emailed (or the same mailbox written a little differently), within seven days of our email. We delete your reply from our mail server as soon as we have dealt with it, usually within minutes. We record that a reply was passed on and when, not what it said. The sender's page shows them when. A reply is never shown to the AI service that sorts support mail.
If the sender also asked other people to add files to the delivery, those files come to you with the rest, in folders named after the people who sent them, with the name each person gave, if they gave one. Everyone the sender sends the delivery to sees them.
If you add files to someone's request
When someone sends you a link to add files, you don't need an account. What we store is the files you add, their names and folders, the name you gave if you gave one, and when. Our software and our database don't store your IP address, and nothing else about your device. The servers your files travel through, and the storage they land in, see the address your browser connects from, as any web server does. Your browser keeps a random code for that request, so you can see and remove your own files from the same browser, and it keeps the name you gave. This page sets no cookie.
Who sees it: the person who asked sees your name, if you gave one, and your files' names, sizes and times. So do the people they have sent the delivery to, now or later: they see your files, and your name as the name of the folder your files are in, as soon as a file arrives or, for a file they release first, once they release it. We don't show them to anyone else; the person who asked decides whom to share them with.
If the person who asked chose to be emailed when files arrive, that email tells them the name you gave and how many files you added. It goes through Lettermint, and stays in their mailbox after we erase the delivery.
We handle your files on behalf of the person who asked, as we handle the files our customers upload. When the person who asked takes photos and videos only, we read the first few thousand bytes of each file you add to check that it starts like a photo or a video, and delete a file that isn't one. When they take any kind of file, or keep zip files as they are, we read only the first few thousand bytes of each such file, to tell what kind of file it is, and don't check its contents; nobody they sent the delivery to sees it until they release it. When they have us unpack zip files and you add one, we take it apart on our server, check each file in it the same way, add the photos and videos to the delivery, and show the zip itself to nobody; the zip, and anything in it that wasn't added, is deleted from storage about a week later. We keep the files as you sent them, including any location or camera details your phone recorded; only the preview pictures have those removed. We make small preview pictures of what you add, as we do for every delivery.
How long we keep them: until the person who asked deletes the delivery. Then, as for any delivery, they can restore it for 30 days, after that we erase it, and your name goes with it. What we erased can remain in our database backups for up to 35 days. The person who asked can remove everything you added at any time; you can't add more from the same browser then. While the request is open you can remove your own files from the same browser. A file you remove, or that they remove, or that we erase, is deleted from storage about a week later, unless the person who asked also keeps it in a snapshot of the delivery; then it stays for the snapshot, and goes when the snapshot is erased. After that, ask the person who asked you, or write to us.
If you report content
Anyone can report illegal or abusive content on our report page, or by writing to abuse@theirway.app. A report holds the category you chose, the link or place you gave, what you wrote, your name and email address if you gave them, and when it arrived. We use it to find the content, decide what to do about it, keep a record of what we decided, and, if you gave an email address, confirm that we received it. We rely on our legitimate interest in keeping Theirway free of illegal content, and on any legal duties we have.
A person at Theirway reads every report. Nobody else sees it, and it is never shown to the AI service that sorts support mail. When a report arrives we get a note with its number, its category and when it came in, and nothing you wrote. If you gave an email address, we send a confirmation to it through Lettermint. We may share a report with the authorities where we are required to.
If you report by email, a person at Theirway reads your message and may enter it in our list of reports, in their own words. That report holds the address you wrote from, and is kept by the rule below even if the conversation your message started is deleted sooner. We send the confirmation to the address you wrote from.
The person whose delivery you report is not told who reported it. If we remove their delivery, our service shows that Theirway removed it, and not who reported it.
We keep a report while we work on it, and for 12 months after we close it. Then we remove your name, your email address, what you wrote and the link you gave. What stays can't identify you: the report's number and reference, its category, its dates and how we decided it. A delivery we removed after a report is erased 30 days later, like any deleted delivery. What we removed can remain in our database backups for up to 35 days.
If you ask us to send the files to your own server
When you ask us to send a delivery's files to a server or bucket of your own (an SFTP server, or an S3-compatible bucket), a separate service in our cluster in France reads the files from storage and sends them to the destination you entered. The files pass through that service only while they are being sent, and only when you ask. We don't send files anywhere you haven't chosen, and we don't support unencrypted FTP.
The details you enter to reach your destination (a password, a private key or access keys) are kept encrypted only until the transfer finishes or you cancel it. If it fails, we keep them so you can try again, and never for more than 7 days. They are never shown again, and then they are deleted. Encrypted copies can remain in our database backups for up to 35 days after that. A day after a transfer ends, we delete its list of files. We keep how many files and how many bytes were sent, and the result, in the delivery's history. We also keep where you sent them (the server name, your user name and the folder, never the password) for as long as the delivery exists, so your page can show you what happened. The sender sees only that you asked for the files to be sent and when it finished, with counts and nothing about your destination. The legal basis is our agreement with you to provide the service.
If you write to us
We keep your message so we can answer it. An AI service sorts and summarises incoming support mail to help us answer faster. It may also suggest a reply, and to do that it reads the conversation: your messages and our earlier replies. A person reads every reply, changes it where it needs changing, and is the one who sends it. A suggestion is kept with the conversation and deleted with it. Mail to privacy@theirway.app is different: a person reads it, and neither it nor the rest of that conversation is shown to the AI service. We answer from support@theirway.app, through Lettermint. Our reply is kept with the conversation and deleted with it; Lettermint keeps its copy for up to 28 days, and a database backup may hold it for up to 35 days. Lettermint tells us whether your mail server took our reply, or that it could not be delivered or was marked as spam. We keep that with the reply and delete it with the conversation. With each message we keep whether our mail server confirmed the sender's address and whether it was sent automatically, such as an out-of-office reply. If your message has attachments, the person reading it sees their names. We do not open them, their names are not shown to the AI service, and they are deleted with the message. To answer you, a person at Theirway can look up what we already hold under the address you wrote from: an account with that address and its deliveries, deliveries sent to that address, and your other messages to us. Each lookup is recorded. What it shows is not kept with the conversation and is not shown to the AI service. We don't look this up for mail to abuse@theirway.app. We keep a support conversation while we're still working on it, and delete it 12 months after we close it. Mail we identify as junk is deleted after 30 days. Deleting a conversation removes its messages, our replies, your address and our summary of it. What stays can't identify you: the ticket number, its topic and urgency, the date it closed, and how it was resolved and why, each chosen from a fixed list. Our database backups are deleted after 35 days, so a deleted conversation can remain in a backup for up to 35 more days. The log of what our staff and tools did with support tickets holds ticket references and fixed words, not what you wrote. The legal basis is our legitimate interest in answering you, or our agreement with you if you're a customer.
Pictures next to names
Next to a producer's name in the app, and next to the people they send files to, we show a small picture if the email address has a Gravatar: a picture a person has chosen to be shown with their address on many websites. This is on by default. The people a producer sends to have not chosen it.
What leaves us. A one-way fingerprint of the email address: a short code worked out from it. Our server sends it, never your browser, so Gravatar never sees your IP address or your browser. We send no name and nothing else. A fingerprint is not anonymous: anyone who already knows an address can work out its fingerprint. What Gravatar can learn from it is that this address exists and is used with Theirway.
To whom. Gravatar, run by Automattic in the United States. We only ask about an address we already hold. If the address has no Gravatar there, we get nothing back and show initials instead.
How long we keep the picture. Up to a day, then we fetch it again, so a changed picture shows within a day. If Gravatar can't be reached we keep showing the last one until it can. For an address with no Gravatar we keep its fingerprint alone, so we don't ask again for a day. A picture, or a fingerprint kept like this, that nobody has looked at for 30 days is deleted.
How to stop it. Write to us: we can switch it off for everyone with one setting. A person can also remove their own Gravatar at gravatar.com, and the picture disappears here within a day. The legal basis is our legitimate interest in showing who is who.
To keep the service running
Our server keeps short-lived technical logs to find faults. They never contain file contents, passwords or sign-in links.
To stop misuse, our software counts how often the same address calls it, using the address your browser connects from. It keeps that in memory only, never writes it to a file or to our database, and forgets it when the server restarts.
Cookies
This website sets no cookies and uses no analytics or tracking. Its fonts are served by us, not by a third party.
The app sets one cookie when you sign in, to keep you signed in. It's needed for the app to work, so we don't ask for consent to it.
Where your data is, and who helps us
We use these companies to run Theirway. Each processes data only on our instructions, under a data processing agreement.
- OVHcloud, France: our server, the database, the mailboxes support mail and replies to link emails arrive in, and file storage. Files go straight from your browser to storage in France. A separate process in our cluster in France fetches a file from storage to make pictures of it: a small preview when your browser can't make one, and a larger preview picture (about 1600 pixels on its longest side, with the location data and camera details removed) that is shown to the client instead of the original file. When the file is a video, it makes a still picture from the video, a single frame taken from the video (usually about a tenth of the way in), and the same two pictures from it. It also makes a small playable copy of the video, no more than 1280 pixels on its longest side and covering at most its first five minutes, which the client can watch in the page instead of downloading the whole file. A still picture from a video and a small playable copy of it are kept like the other previews. The video's own location data, device details and recording time are not carried into any of them, and the process reads the original video only while it makes them. The process keeps nothing else, and the pictures and the copy are stored next to the file and deleted with it. When a client asks us to send the files to a server or bucket of their own, another separate service in our cluster in France reads them from storage and sends them on, as "If you ask us to send the files to your own server" above says. A third, also in our cluster in France, reads a zip file from storage to take it apart, when it was added through a link that has us unpack zip files or when the person who owns the delivery asks us to unpack it, and writes the files in it back to storage; it keeps nothing.
- Lettermint, the Netherlands: sending our emails: sign-in links, the links a sender asks us to email to the people they send files to (the email, including the link, which Lettermint keeps for up to 28 days) and the replies to those emails that we pass on to the sender, the emails to senders when files arrive in a request (counts, and the names the people who sent them gave), our replies to your support mail (kept by Lettermint for up to 28 days), and the confirmation of a report.
- Berget AI, Sweden: sorting and summarising support mail, and suggesting replies to it. Messages are processed in the EU, under a data processing agreement.
- Google Workspace: our own company mailbox. When a support message needs a person, we get a note there with a ticket number, its topic and how urgent it is, and another if it waits too long for an answer. About once an hour we may also get a list of the ticket numbers of mail set aside as junk. The message itself is not sent to Google. Google may process data in the United States, under the EU-US Data Privacy Framework and standard contractual clauses.
One more company receives something from us, and it is not one of those above. Gravatar, run by Automattic in the United States, receives a one-way fingerprint of an email address, so it can tell us whether that address has a picture. It runs its own public service and handles the fingerprint under its own privacy policy. "Pictures next to names" above says what we send and how to stop it.
When Google Drive, Dropbox and OneDrive arrive as delivery options, a client who picks one asks us to copy the files there. Those are US services, so the copy leaves the EU because the client chose it, and their screen will say so first.
Your rights
You can ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, and to receive it in a format you can take elsewhere. Where we rely on your consent, you can withdraw it at any time. Write to privacy@theirway.app, and we'll answer within a month. If you ask us to delete a support conversation, we can delete it as soon as you ask instead of after 12 months. Two copies are beyond our reach and run out by themselves: Lettermint's copy of our replies, after at most 28 days, and our database backups, after at most 35 days.
If you think we handle your data wrongly, you can complain to the Swedish Authority for Privacy Protection, IMY.
Changes
If we change what this page says, the version date at the top changes. If a change affects something you agreed to, we'll tell you by email first.