Privacy policy

Who we are

Filebender is made by Rabbit Labs (“we”, “us”). We decide how the personal data described here is used, so under UK data protection law we are its controller.

For anything about this policy or your data, email support@rabbitlabs.app.

What this policy covers

This policy covers:

• the Filebender website at filebender.rabbitlabs.app, including your account, the History and Status pages, passes you buy on the Pricing page, and the pages a phone opens when you use Send to phone or Add from phone;
• Filebender for Google Workspace, the add-on that opens Filebender from Google Drive, Gmail, Docs, Sheets and Slides.

The rabbitlabs.app website and our browser extensions have their own privacy policy. The rules for using Filebender are in our terms.

Your files

Filebender converts most files on our servers, so it has to receive them. Some pictures and PDFs are converted in your browser instead, on your device, and never reach us: Files converted on your device explains which, and what we record about them. This section is about the files we receive.

• What happens to them. Files you add are uploaded over an encrypted connection to private storage we control on Google Cloud. Each file is converted in its own locked-down container that can't reach the internet, and the results are stored beside it so you can download them. Working copies on the machine that converts a file are deleted as soon as that file is done.
• What we don't do. Nobody at Rabbit Labs looks at your files, and we don't share them. Filebender reads them only to check what they are and do the conversion you asked for, and they're never used to train any model.
• When they're deleted. Your files and results are deleted an hour after the conversion finishes, or at once when you press “Delete files now”. A file you add but don't convert is deleted an hour after you last used it. As a backstop, our storage deletes anything older than a day, and deleted files are not kept in any form we can recover.
• Photo and video details. By default, Filebender removes location and camera details from the photos and videos it converts. If you choose to keep them, or use the Archive preset for photos, they stay in the result.
• Reading text (OCR). When you make a PDF searchable, turn a picture into text, or convert a scanned PDF into a document, the text is read on our servers, not on your device. The file and the text read from it are handled like any other file and result, and deleted an hour after converting. The languages you chose are kept with the History record. A photo prepared for reading has its location and camera details removed unless you choose to keep them.
• Trimming. When you trim a recording, the timeline's preview, pictures and sound wave are made by your browser from the copy on your device. The file is still uploaded to be converted, like any other.
• Repairing a PDF. If your browser can't open a PDF in the PDF tools and you choose to have it repaired, it's uploaded and repaired on our servers, then handled like any other file: listed in History, and deleted an hour after it's repaired.
• History. For each file, we keep a record so the History page can show it to you: its name, size and format, what you converted it to and with which settings, the names and sizes of the results, progress notes and any error. For an archive, the record includes the names of the files inside it. Each file you add, even one you never convert, also has a short record of its name, size and type (for an archive, the names inside it; for a Drive file, its Drive ID and folder), kept for 24 hours after it last changed. These records never hold file contents. They're kept for 24 hours and then deleted automatically, which can take up to a further day, or deleted at once when you choose “Remove from history”.
• Deletion log. Each time your files are deleted, we note when, why and the file names, so the Status page can show you. These notes are kept for 24 hours and deleted the same way as History.
• Files from a link. If you give Filebender a web address, our server downloads the file for you, so the site at that address sees our server, not you. We keep the file's name, not the address.
• Download links. Each result has a long, random, signed link. A link works for at most an hour from when it's made, and never after the files are deleted. Anyone you give a link to can use it until then, so share it only with people you mean to. Links for your phone are shorter-lived: see Sending files to and from your phone.

Legal basis: contract. We need to handle your files to do the conversion you asked for.

Files converted on your device

Some conversions happen in your browser, on your device, so the file is never sent to us:

• pictures (JPG, PNG, WebP, BMP, AVIF, and GIF with one frame) that become JPG, PNG or WebP, when your browser and your device's memory can manage it and the settings you choose don't need our servers. A PNG kept as a PNG at its own size, as when you compress one, is always sent to our servers, because they can make it smaller than a browser can;
• the PDF tools, which always work in your browser: merging, splitting and organising PDFs, turning pages and taking them out, and putting JPG and PNG photos into a PDF. A photo put into a PDF leaves its location and camera details behind.

Before one of these conversions starts, your browser tells us what we need to count it against your plan: for each file, its kind (such as image or document), the format it's in and the one it becomes, its size and which tool is used. Never its name, its contents or anything taken from them. We keep that, with the time, as a record in your History for 24 hours (then it's deleted automatically, which can take up to a further day), or until you choose “Remove from history”. It's also added to your daily usage and your account's conversion totals, like any other conversion (see Usage counts and limits). If a conversion fails, your browser tells us which files failed, so they're given back to your allowance. If you leave the page before a conversion has finished, your browser tells us that too. If it can't tell us, for example because the tab closed or lost its connection first, you can ask us to put them back (see the terms). If the page is still open, it tells you so.

• The results stay in your browser tab. We never receive them, so we can't recover them for you: download them before you close the tab. Photos converted on your device always lose their location and camera details.
• No one else is involved. The software that does the converting is downloaded from Filebender's own site, not from any other company, so no one else learns what you convert.
• Uploaded only if you choose. A file read on your device is sent to our servers only if you choose that: when a conversion fails and you press “Convert on Filebender's servers”, when you pick a setting or output format only our servers have (the file's row says so first, and nothing is sent until you press Convert), or when you ask for a damaged PDF to be repaired. From then on it's handled like any other file we receive.
• What your browser can open. To decide which pictures it can convert, the page checks once which image formats your browser can open, and keeps the answer in the tab's session storage (see Cookies and browser storage).
• When it's switched off. We may switch off converting on devices for a while, for example to fix a problem. While it's off, pictures are sent to our servers and converted there, and handled like any other file we receive (see Your files); the PDF page tools are switched off until it's back. The PDF Converter and the PDF Compressor still work on our servers.

Legal basis: contract, to count the conversion against your plan and show it in your History.

Sending files to and from your phone

Two features use a QR code to move files between a computer and a phone. Both are optional.

Send to phone. A file converted on our servers can be sent to a phone with a QR code. The code holds a link that works for 10 minutes, and never after the file is deleted. The link names only the conversion, which file, when the link ends and a signature, never you or anything about you, and we store nothing about it. Anyone who has the link can download that file until it stops working, so only send it to yourself or someone you trust. To stop links being guessed, each of our servers counts how often each connection opens them, a minute at a time and in memory only.

Add from phone. This sends photos and files from your phone into Filebender on your computer, into the same account, for 10 minutes. While a session lasts, we keep a record of it:

• a session number and your account;
• your email address masked to its first letter and domain (like s***@example.com), which the phone shows so you can check the files go to the right account;
• keyed hashes of the link in the QR code, of the code you can type instead, and of a secret held by the phone that connects. Never the link, the code or the secret themselves;
• when the session was made, when it ends and when a phone connected;
• the connected phone's browser and system, as a short label such as “Safari on iPhone”, so you can see which phone connected;
• whether and how the session ended;
• the names, sizes and progress of the files the phone sent.

The record is deleted automatically an hour after the session's 10 minutes are up (which can take up to a further day), or replaced at once when you make a new code.

• The files. Files your phone sends are uploaded to your account like any others: deleted an hour after converting, an hour after they arrive if you don't convert them, or at once when you remove them. Pressing Disconnect deletes files still on their way. They count against your plan only when you convert them. Their size counts against the day's upload allowance, on your account and, on the free plan, on the phone's connection (IP address), stored as Usage counts and limits describes.
• The sign-in log. We add an entry when a phone connects (with the phone's IP address and browser), when you press Disconnect (with your computer's) and when the phone presses Finish (with the phone's). They're kept for a year, like the rest of the sign-in log. Whoever's phone it is, its IP address and browser are logged against your account, so only connect a phone you use.
• Wrong codes. Each of our servers counts wrong codes from each connection for 15 minutes, in memory only, to stop guessing. Nothing from this is stored.
• The phone's pages set one cookie, fb_phone, and only once you press “Connect this phone” or type the code (see Cookies and browser storage). They load no analytics.
• Request logs. The links for Send to phone and Add from phone are part of the page address, so they're in our request logs (see Technical logs) for 30 days. They stop working long before then.

Legal basis: contract, to provide the features you ask for; and legitimate interests, for the sign-in log entries and the limits on links and codes, which keep accounts secure.

Google Drive

You can add files from Google Drive and save results back to it. This is optional.

• Only the files you choose. Filebender asks Google only for permission to use the Drive files you use with it (Google calls this permission drive.file). So it can open only the files you pick in Google's file picker and the files it creates for you. It can't see anything else in your Drive.
• Your Google access token. When you connect Drive, Google gives the page a token that lasts up to an hour. It stays in the page's memory, isn't saved in your browser, and is sent to our server only with the requests that need it. If a conversion has to save to Drive, or export a Google Docs, Sheets or Slides file, while you wait, the token is stored with that conversion, encrypted, and deleted when the conversion finishes.
• What we keep. For a file from Drive, its History record also holds its Drive ID, the folder it's in and its Drive link, and these are deleted with the rest of the record.
• Replacing an original. Filebender changes nothing in your Drive unless you ask. If you press “Replace the original in Drive” and confirm, it saves the result where the original was and moves the original to Drive's trash, where you can restore it for 30 days.
• Google's scripts. Only when you choose Google Drive does the page load Google's own scripts for the permission window and the file picker. (Google Analytics is separate, and loads only if you accept it: see Cookies and browser storage.) Google may use its own cookies there, under Google's privacy policy.

Filebender's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Legal basis: contract, to fetch and save the files you ask us to.

The Google Workspace add-on

The add-on runs on Google's servers, inside Google Workspace. It converts nothing and keeps nothing itself: it tells you what Filebender is, gets permission for the files you choose, and opens Filebender with them.

• In Google Drive, it reads the names and types of the items you select, to show which ones Filebender can convert. When you press “Allow access to this file”, Google lets Filebender use that one file.
• In Gmail, when you open the add-on on a message, it reads the names, types and sizes of that message's attachments. It doesn't use the text of the message. When you press “Convert”, it saves a copy of that attachment to your Google Drive and opens Filebender with it. The copy is yours and stays in your Drive until you delete it.
• In Docs, Sheets and Slides, once you allow access to the open file, it reads the file's title and ID, to open Filebender with it.
• The add-on passes the files' Drive IDs to Filebender in the link it opens. From then on, Filebender handles the files as described above.
• If the add-on hits an error, Google records the error in our Google Cloud logs, which are deleted after 30 days.

Legal basis: contract, to open Filebender with the files you choose.

Your account

Every plan, free or paid, needs a Filebender account. You can sign in with Google, or create an account with your email address and a password. Your username is your email address, and each address can have only one account.

You don't have to give us these details, but Filebender can't be used without an account, and an account needs your email address and your name, from Google or typed in. The rest of what this policy describes is recorded as you use Filebender.

• Signing in with Google. You sign in on Google's own page, and we never see your Google password. We ask Google only for your basic profile and your email address, and Google must have verified the address. We keep what Google's sign-in tells us: your email address, your full name and your first and last names, the web address of your profile picture, your Google account ID, your language, and your organisation's domain if you use a Google Workspace account and Google includes it.
• An email account. We keep your name, your email address and a salted scrypt hash of your password, never the password itself. The hash lets us check the password you type but can't be turned back into it, so nobody at Rabbit Labs can read your password. You can't convert files or buy a pass until you confirm your address with the link we email you, which works for 24 hours, and the password you chose.
• Checking a new address. When you create an account with an email address and password, we check that the address isn't from a temporary or disposable email service and that its domain can receive email. We compare the domain (the part after the @) with a list of disposable email services that we keep on our servers, and look up the domain's mail servers in the internet's public directory (DNS). Only the domain is looked up, never your whole address, and we don't keep the result. Google sign-ins aren't checked.
• Using both. If you sign in with Google using an address that already has an email account, the two become one account. If that email account was never confirmed, its password is removed and you sign in with Google from then on. If the address belongs to an account that signs in with a different Google account, the sign-in is refused.
• Forgotten details. If you forget your password or your username, we email you a link to choose a new password. It works once, within 15 minutes, and the email also tells you your username. Setting a new password confirms your address and signs you out in every other browser. If your account only used Google sign-in, it also adds a password to it. The links in our emails are random, and we store only a SHA-256 hash of each, never the link itself.
• An earlier access code. If your account entered an access code while Filebender was invite-only, we still note when it did. We never stored the code itself.
• What else we keep with your account. Which ways you sign in; whether and when your email address was confirmed; when we sent your welcome email; when you created the account, when you last signed in and how many times; when you last changed your password; a session number that lets us sign you out everywhere when your password changes; how many conversions and files you have started (on our servers or on your device), and when you last started one; and your pass and purchases (see Passes and payments).

We use these details to let you sign in and convert files, to keep your files and History private to you, to apply your plan and your pass, to see how much Filebender is used, and to stop abuse. We keep your account until you ask us to delete it.

Legal basis: contract, to run the account you asked for. Counting the conversions you start, to see how much Filebender is used, relies on our legitimate interests in running the service.

The sign-in log

We keep a log of what happens to each account, to protect accounts and spot abuse. We add an entry when you create an account, confirm your email address, sign in or out, type a wrong password, ask for a password reset, set a new password, or join a Google sign-in to an email account. We also add one when a Google sign-in is refused because the address belongs to an account that uses a different Google account, and when a phone connects with Add from phone, is disconnected or finishes (see Sending files to and from your phone).

Each entry holds what happened, your account and email address, the time, the IP address and the browser's user agent (a short description of the browser and device). For a phone connecting or finishing, those are the phone's. Each entry is deleted a year after it was made.

Legal basis: legitimate interests: keeping accounts secure and finding misuse. A year lets us see a pattern of attempts on an account.

Usage counts and limits

• Daily allowance. To apply the free plan's limits (files and videos a day, how much you can upload, and a fair-use limit on conversion time), we count what you convert (on our servers or on your device) and what you upload (from your computer or your phone) each day, per account and per IP address, and the higher of the two counts applies. That stops a second account on the same connection doubling the allowance. What you use from a pass is counted on your account instead.
• Attempts. To stop password guessing and floods of email, we count, each hour, wrong passwords per account and per IP address, new accounts per IP address, and account emails per email address and per IP address.
• How addresses are stored in these counts. An IP address is stored only as a salted hash that changes every day (every hour for the attempt counts), and an email address only as a keyed hash. Neither can be turned back into the address. The counts are kept for two days after the last change, then deleted automatically, which can take up to a further day.
• Flood guard. Each of our servers also counts requests per IP address, a minute at a time and in memory only, to stop scripts overwhelming the service. Nothing from this is stored.
• Totals. We also add up the conversion time of every conversion on the free plan each day, with nothing that identifies you, to cap what the free plan can cost.

Legal basis: contract, to apply the limits of your plan; and legitimate interests, to keep the free plan fair and to protect accounts and the service from abuse.

Anonymous statistics

We keep daily totals of conversions: for each day, where files were converted (on a device or on our servers), their kind, the format each came from and went to, and a size band (such as 1 to 10 MB), with how many files and how many bytes. Nothing in them says who converted what: no account, name, file name or IP address. We use them to plan Filebender, for example to decide which conversions should run on devices, and keep them for 400 days.

Legal basis: legitimate interests, in planning and improving Filebender. The totals themselves don't identify anyone.

Passes and payments

Filebender has a free plan, with a free account: 20 files a day, up to 2 of them videos, each up to 500 MB. If you need more than it includes, you can buy a Day, Week or Month Pass. You need to be signed in with a confirmed account to buy one.

• Paying. When you buy a pass, your browser goes to SumUp's own payment page, and you type your card details there, never on Filebender. Filebender never receives or stores your card details. SumUp handles them, and anything else you enter on its page, as a payment provider in its own right, under its own terms and privacy notice. We tell SumUp only which pass you're buying, its price and an order reference. We don't send it your name or email address.
• Checking the payment. Before a pass is added to your account, our server asks SumUp directly whether the payment went through, for the right amount. A pass is only ever added for a payment SumUp confirms.
• Order records. For each order we keep your account and email address, the pass, its price and currency, the order's status, SumUp's references for the checkout and the payment (its checkout ID, transaction code and transaction ID), when the order was made, paid and added to your account, how many files your pass had already used at that moment (so we can tell whether you've used the pass if you ask for a refund), when we emailed your receipt, and your IP address when you started it.
• What you agreed to. Before you pay, you tick a box to confirm that you want your pass to start straight away and that you understand you can have a full refund while you haven't used it, but not once you have. We keep the exact words you agreed to, and when, with the order, and repeat them in your receipt.
• Your pass. With your account we keep which pass you have, how many files and videos it includes and how many you've used, the biggest file it takes, how many conversions it can run at once, when it started and when it ends, and the orders that paid for it. We also keep how many passes you've bought and when you last bought one. While a payment is waiting to be confirmed, your account notes which order it is, so the pass can be added on your next visit, and until your receipt has been emailed, it notes that order too, so the receipt can be sent again if sending failed.

We use these records to add your pass, send your receipt, show what you agreed to before paying, answer questions about a payment, refund a pass you haven't used, return a payment when our terms or the law require it, spot fraud, and keep the accounts UK tax law requires. Records of paid orders, including payments we have to sort out by hand, are kept for six years, even if you ask us to delete your account, because UK tax law requires it. Orders that were never paid are deleted after a month.

Legal basis: contract, to sell you the pass and give you what it includes; legal obligation, to keep records of paid orders for six years and to confirm your purchase and what you agreed to; and legitimate interests, for the IP address kept with each order, which helps us spot fraud.

Emails we send you

Filebender sends only these emails: the link to confirm your address, a welcome email once your account is ready, the link to reset your password, a receipt for each pass you buy, and a note when someone tries to create an account with an address that already has one. We don't send newsletters or marketing.

The emails come from support@rabbitlabs.app and are sent through Microsoft 365, which runs our email. Microsoft processes your email address, your name and the content of the email to deliver it. We don't keep copies in our sent mail.

Legal basis: contract, to confirm your address, welcome you to the account you made and let you back into it; legal obligation, for the receipt, which consumer law requires; and legitimate interests, for the note about an existing account, which tells you if someone tried to use your address.

Emails you send us

If you email support@rabbitlabs.app, or reply to one of our emails, for example about your account or a payment, we use what you send to answer you. It's kept in our support inbox, on Microsoft 365, only as long as we need it to deal with your request, and we'll delete it sooner if you ask.

Legal basis: legitimate interests, in answering you; or contract, where your email is about your account or a pass.

Technical logs

Google Cloud records a log line for each request to Filebender: your IP address, your browser's user agent, the address requested (including the link, when a phone opens a Send to phone or Add from phone link), the page you came from and the time. Our service also logs events such as a new account, a payment that needs checking or an error, naming accounts and orders by their internal ID rather than by name or email address. We use these logs only to keep Filebender secure and working, and they are deleted after 30 days.

Legal basis: legitimate interests: keeping the service secure, finding faults and stopping abuse.

Cookies and browser storage

Filebender has no advertising cookies, and uses no tracking pixels or fingerprinting. The cookies it sets itself are strictly necessary for things you ask for: three for signing in, and one on a phone you connect with Add from phone. The page also keeps a few notes in your browser's session storage and local storage, which aren't cookies and stay in your browser. Each of these is needed for something you use, such as staying signed in, buying a pass, converting on your device or keeping your presets, so under the UK's rules on cookies (PECR) Filebender doesn't ask for consent to them. Google Analytics cookies are different: they're set only if you accept them.

Google Analytics, only with your consent. On your first visit, a banner asks whether we may use Google Analytics cookies. If you accept, Filebender uses Google Analytics to count the pages people visit and a few things they do: creating an account with an email address, starting a conversion (which tool, how many files, and whether they're converted on your device), choosing a pass, and buying one (which pass, its price and the order reference). Google Analytics sets its cookies and processes your IP address on Google's systems, under Google's privacy policy. We never send it your files, their names, your email address, or the part of a page's address after a # or ? (apart from campaign tags such as utm_source), which is where links carry things like sign-in codes. Advertising features are off. If you reject the cookies, or make no choice, the Google Analytics script is never loaded and nothing is sent to Google.

Changing your mind. Use Cookie settings at the foot of any page. If you reject analytics after accepting, Google Analytics stops at once and we delete its cookies from your browser. rabbitlabs.app asks separately.

Legal basis: consent, for Google Analytics. Withdrawing it doesn't affect anything else in Filebender.

You can remove all of these by clearing your browser's data for filebender.rabbitlabs.app. If you block cookies, you won't be able to sign in.

Who we share data with

We don't sell your data, and we don't use it for advertising. We have no advertising partners. We use a few providers to run Filebender, each only for what's described here:

• Google Cloud hosts Filebender. It stores and converts the files we receive (reading text from them too, when you ask), holds our database of accounts, History and orders, keeps our logs and runs our servers. It acts on our instructions, as our processor.
• Microsoft, through Microsoft 365, sends our emails and runs our support inbox, as our processor.
• SumUp takes payment for passes on its own page. It's a payment provider in its own right, responsible for your card details and anything else you give it.
• Google Analytics, only if you accept analytics cookies, to count page views and the few actions described in Cookies and browser storage.
• Google, if you sign in with Google or use Google Drive or the Workspace add-on. Google handles your Google account, the sign-in and your Drive files under its own terms and privacy policy.

The software that converts files on your device is downloaded from Filebender's own site, so no other company takes part in those conversions.

We may also disclose information when the law requires it, for example in answer to a valid court order, and only as far as required.

Where your data is kept

Filebender stores and converts the files we receive, and keeps its database, in Google Cloud's europe-west1 region, in Belgium. Files converted on your device stay on your device. UK law recognises countries in the European Economic Area as protecting personal data properly.

Some processing happens elsewhere. Google keeps our request and service logs in its global logging system, and may process them outside the UK and Europe, including in the United States. Microsoft may also process the emails it handles for us outside the UK. Where our providers move data outside the UK and the EEA, they rely on the safeguards UK law allows, such as Standard Contractual Clauses with the UK's addendum. Email support@rabbitlabs.app if you'd like details of these safeguards. Google Analytics, if you accept it, may also process data in the United States. Google, for sign-in and Drive, and SumUp handle your data in their own right, and their privacy policies explain where they process it.

How long we keep things

Your rights

Under UK data protection law (the UK GDPR and the Data Protection Act 2018), you have the right to:

• get a copy of the personal data we hold about you;
• have it corrected if it's wrong;
• have it deleted;
• ask us to limit how we use it;
• object to our using it where we rely on legitimate interests;
• receive the data you gave us in a format you can take elsewhere.

Some rights have limits. For example, we can't delete records of paid orders before the six years are up, because the law requires us to keep them.

We don't make decisions about you by automated means that have legal or similarly significant effects. Limits such as the daily allowance and the limits on attempts are applied automatically. If you think one has been applied to you wrongly, email support@rabbitlabs.app.

To use any of these rights, email support@rabbitlabs.app, ideally from the address on your account. We may ask you to confirm it's you before we act. It's free, and we'll reply within one month.

Some things you can do yourself at any time: delete your files with “Delete files now”, clear your History with “Remove from history”, disconnect a phone with Disconnect, and sign out.

Deleting your account

To delete your account, email support@rabbitlabs.app from the address on the account. We will delete your account, including your profile, your pass and the link between your email address and the account, which signs you out everywhere at once. We will also delete your entries in the sign-in log.

Deleting your account ends any pass on it. If you haven't used a pass, ask for a refund first (see Refunds in our terms). Records of paid orders stay for six years, because UK tax law requires it. Everything else goes by itself: your files within an hour, your History and usage counts within a few days, orders that were never paid within a month, and log lines that mention your account within 30 days. If you'd like the emails you've sent us deleted too, say so.

If you signed in with Google, you can also remove Filebender's access in your Google Account's settings.

Children

You must be at least 13 years old, or the minimum age of digital consent where you live if that's higher, to use Filebender, as our terms say. We don't knowingly collect personal data from anyone younger. If you think a child has given us personal data, email support@rabbitlabs.app and we will delete it.

How we keep your data safe

• Your files are kept in private storage that can't be made public, and each conversion runs in its own container with no internet access.
• Download links are signed and stop working within an hour, and links for your phone within 10 minutes.
• Add from phone keeps only keyed hashes of its link, its code and the phone's secret. Only the first phone to connect can use a session, and you can disconnect it at once.
• The software that converts files on your device comes only from Filebender's own site, and runs in your browser under a strict security policy.
• Passwords are stored only as salted scrypt hashes, and links in our emails only as hashes. Those links expire, and each works only once.
• Wrong passwords are limited, and a new password signs out every other browser.
• We only ever send Google Drive tokens to Google, and we encrypt one whenever we have to store it.
• The keys for the services we use are kept in Google Cloud's Secret Manager, never in our code.
• Card details never reach us, and every payment is checked with SumUp before a pass is added.

No way of sending or storing data is completely secure. If a breach puts your data at risk, we will tell you and the ICO when the law requires it.

Changes to this policy

If Filebender changes how it uses personal data, we will update this policy and the date at the top. For a change that matters, we will say so on filebender.rabbitlabs.app before it takes effect.

Contact and complaints

Questions, requests or worries about this policy or your data: email support@rabbitlabs.app.

If you're unhappy with how we've handled your data, you can complain to the UK's data protection regulator, the Information Commissioner's Office (ICO). We'd be grateful for the chance to put things right first. If you live in the European Economic Area, you can also complain to your local data protection authority.