Skip to main content
CapCats logoCapCats

Privacy Policy

Effective date: October 29, 2026

This policy explains what personal data CapCats collects, why, who receives it, how long it is kept and what you can do about it. It covers the CapCats app for Android, the website capcats.app and the emails you send me. There is no iPhone app yet. CapCats is provided by Think Languages LLC. I'm Stefano, and I run CapCats for Think Languages LLC. In this policy, "I" and "me" mean Think Languages LLC.

The short version

  • CapCats is an app for photographing real cats, turning them into stickers, and browsing and collecting other people's cat pictures.
  • Your original photo never leaves your phone through CapCats. The app cuts the cat out on your phone, and only that cat is uploaded, with the background and text you choose.
  • Pictures are public unless you make them private. Your alias is always public. Your first name is public unless you switch it to private.
  • There are no ads in CapCats and I don't sell your data.
  • I use a few service providers to run CapCats. They are listed in section 8.
  • The app sends usage data to Google Analytics unless you turn off Share usage data in Settings. Crash reports go to Sentry either way.
  • The website pages of capcats.app use Google Analytics for every visitor, without asking first. The pages that open from a picture or profile link do not.
  • You can delete your account in the app at any time. Deletion is immediate.

1. Who is responsible

Think Languages LLC, 1309 Coffeen Ave, Suite 1200, Sheridan, WY 82801, United States, provides CapCats and is responsible for your personal data.

For anything about privacy, write to [email protected]. I handle every privacy question myself.

2. What CapCats collects and why

Your account

When you first open CapCats, it creates a guest account for you without asking for anything. The account has a random ID. This is what lets you like, save and take pictures straight away.

If you secure your account with Sign in with Apple or Google, I receive from Apple or Google the details they share for sign in. From Apple that is an ID for you at Apple, your email address (the private relay address if you chose to hide your email) and, the first time you sign in, the name you choose to share, if any. From Google it is an ID for you at Google, your email address, your name, the web address of your Google profile picture and, for a work or school account, its domain. I use these to sign you in and to recognize your account, and the app offers the first name Apple or Google shares as a suggestion for the first name on your profile. Nothing is saved to your profile until you continue.

CapCats sends no emails of its own, and I never send marketing email. I write to you only to answer an email you sent me, or about your account when I need to.

Your profile

  • Alias. Every account gets a generated alias, such as sunny_whisker_482. You can change it. It is always public.
  • First name. Optional. If you sign in with Apple or Google on the first name screen, the name they share is suggested in the field, and nothing is saved until you continue. It is public unless you turn on Private.
  • Profile photo. Optional. It is copied from a picture of one of your public cats when you choose it. It is public, except while it is hidden during a review. The copy is separate from the picture: if you later delete that picture, or make the picture or the cat private, the profile photo stays until you change or remove it in Edit profile.

Your pictures

When you save a picture, CapCats uploads:

  • your cat, cut out of the photo, in a few sizes,
  • a preview image of the finished picture, used when a link to it is shared,
  • your choices for it: background, meme text, optional title, the cats it belongs to, and whether it is public or private,
  • the language your meme text is written in, worked out from your app language and the letters you typed, so the text displays correctly for everyone who sees the picture,
  • the day you took it, your phone's time zone offset at that moment, and the time you saved it.

The uploaded files carry no camera or location details.

Your original photo

The full photo you take stays on your phone. CapCats does not upload it, and nobody else can get it from the app.

Two copies exist on your phone. One is the app's working copy. It is deleted when you save or discard the picture, or otherwise the first time CapCats opens more than 7 days after you took the photo. The other is a copy in your phone's gallery. Save photos to your gallery is on unless you turn it off in Settings. That copy is your own file, so your phone treats it like any other photo. If you use a cloud photo backup, it is backed up with the rest. CapCats never reads your gallery and never uploads from it. If you have already allowed CapCats to use your location, the gallery copy carries a rough location, rounded to about 1 km. You can turn gallery copies off in Settings.

Finding and cutting out the cat

CapCats looks for a cat and cuts it out on your phone, using Google's ML Kit. Your photo is not sent to a server for this. Google says ML Kit works on your phone and does not send your photo, or what it finds in it, to Google.

The part of CapCats that cuts out the cat is a module that Google Play services downloads and keeps up to date on your phone. If it is not on your phone yet, CapCats asks Google Play services to download it when the app starts, when you open the camera and before it cuts out a photo. That request carries no photo, and the download happens between your phone and Google.

ML Kit does send Google technical data about how it runs: your phone's make, model and system version and the machine learning hardware it has, the app's identifier and version, an identifier that Google describes as one for this installation of the app or, for some features, for your phone, how long things take, the settings it ran with, such as the format and size of the images it works on (not the images themselves), and event and error codes. Google says that the part that finds the cat also uses Google's Firebase installation and remote configuration services. Google uses this data to measure performance, to fix and improve ML Kit and to detect misuse. The Share usage data switch does not turn this off.

What you do in CapCats

To make the app work, I keep:

  • the pictures you like,
  • the pictures you hide from your feed,
  • your cats, your collections and what you saved in them,
  • which pictures you have already seen, so your feed can show new ones first,
  • your settings for who can see your pictures, your Liked collection and your first name,
  • a record of each save: the day you took the picture, your phone's time zone offset, and when you saved it. This record stays when you delete the picture and is deleted with your account. CapCats counts these records to celebrate your 1st, 10th, 50th and 100th saved picture and every 100th after that, so a deleted picture still counts. I plan to use the record for more personal stats in a later version, such as how many days in a row you saved a cat. Only you see any of it.

Location of a picture, and its rough area

Add location is on for every new picture, and you can turn it off for that picture before you save it. CapCats adds a location only if you have allowed it to use your phone's location. It asks your phone for an approximate location only, rounds it to about 1 km on your phone, and stores that with the picture in my database. That stored location stays private: CapCats never gives it to anyone else.

From the stored location, my server works out the picture's rough area: one square of a fixed grid that covers the whole world, about 2 km across wherever you are. Every picture taken in the same square has the same rough area. Anyone who is allowed to see the picture can receive its rough area, including people who open a link to it. A private picture, a picture whose cats are all private, a picture hidden for review, and people you blocked or who blocked you never get the rough area, just as they never get the picture. This version of the app does not show the rough area yet. I share it so that CapCats can later show cats found nearby and a map of cats.

Many pictures taken in one place, such as your home, all show the same rough area. Someone who sees them can then tell roughly where you take most of your pictures, to within about 2 km, but never the street or the house. If you'd rather not share that, turn off Add location before you save, or remove the location later in Edit picture, which removes the rough area too. Pictures you saved before rough areas were introduced keep their location private and show no rough area.

On Android phones with Google Play services, CapCats gets your rough location through Google Play services, so Google's own location settings on your phone decide what Google collects. CapCats itself sends no location to Google.

Reports and blocks

If you report a picture, a profile or a collection, I keep who reported, what was reported, the reason, any details you add, when you reported it and when I reviewed it. The person you report is never told it was you.

If you block someone, I keep that so the two of you stop seeing each other in CapCats. They are not told. A block works inside the app. Public pictures and profiles also have pages on capcats.app that open for anyone with the link, and a block can't stop that.

If one of your pictures, collections, cat names, your first name or your profile photo is put under review or removed, I keep that state and the reason, and you see a notice on your profile.

The Community guidelines

The first time you save a picture, CapCats asks you to agree to the Community guidelines. I keep which version you agreed to and when.

Usage data

If Share usage data is on, CapCats sends usage events to Google Analytics for Firebase: which screens are opened, actions such as a like, a save or a share, how long things take, and error codes. Events refer to pictures and collections by their IDs, and they say whether you are a guest and which language the app is in. Once your profile has loaded, they also carry a random analytics ID for your account. The analytics ID is not your account ID, so Google can't tell which CapCats account it belongs to. I keep the link between the two on your profile, and it is deleted with your account. Google's software also records the time, the app version, your phone's brand and model, its system version, screen resolution and language, and its own ID for this installation of the app, which is the only ID on events sent before your profile has loaded.

On Android, Google's analytics software includes a way to read the Google Play install referrer: information Google Play keeps about how the app was installed, such as the link or campaign that led to it and when.

Usage events never include your alias, your first name, titles, meme text or images, and the app never sends your location in a usage event. Google Analytics works out an approximate place from the internet address of each request, such as the country, the region and the city. Google says that for people in the EU, Switzerland and the UK it uses the address only for this and then discards it, without logging or storing it. For everyone else Google says it also uses the address to detect spam, never links it to an ID, and discards it after use.

CapCats does not use an advertising ID: the app switches off its collection in Google's analytics software and does not have the permission to read it. Usage data is not used for ads. I have turned off Google signals, which would link this data to people's Google accounts, and the setting that lets Google use it for its other products and services. Google processes the data for me under its data processing terms. Three of Google's sharing settings are on. Google may use the data, combined with data from other sites and apps and with identifying details removed, to build features, benchmarks and publications and for market research. Google's Analytics support staff may look at it when they help me with a technical problem. And Google may look at it to give me tips and offers about using its products.

Share usage data is on when you install CapCats, so usage events are sent from the first screen. You can turn it off in Settings, under Privacy. It applies on that phone from that moment, and Google Analytics collects no more usage data from it. ML Kit's technical data, described above, and crash reports, described below, are not covered by this switch.

Crash reports

When something goes wrong in the app, CapCats sends a crash or error report to Sentry so I can fix it. A report contains the error and where in the app it happened, a short technical trail of what the app was doing, your account ID, for some errors the ID of the picture or photo involved, and details of your phone such as its model, system version, memory and language. Sentry also records the approximate place a report came from (country, region and city), which it works out from your IP address. CapCats attaches no screenshots and adds no alias, first name or text you wrote to a report, and it removes picture addresses, and any text an error would quote, from the reports it makes itself. When the app crashes outright, Sentry's own software records the crash at a lower level, without that last step.

CapCats also tells Sentry each time the app is opened, so I can see what share of sessions end in a crash. That record holds the app version, the time the session started and how long it lasted, whether it ended in a crash and how many errors it had, and an ID for you or for your installation of the app, which Sentry scrambles before it stores it. It holds nothing you made or wrote. A new record starts when you open the app, and again when you come back after more than 30 seconds away.

Crash reports and session records are sent whether or not Share usage data is on.

Technical data every request carries

Like every app that uses the internet, CapCats makes requests that carry your IP address and some technical details: the software the app uses to connect, and your phone's operating system and its version. The sign in service keeps the IP address of each of your sessions with your account, together with the name and version of that connection software. The record of a session is deleted when you sign out while your phone is online, or when you delete your account. Supabase also keeps logs of the requests to CapCats for 7 days. They hold your IP address, your phone's operating system and its version, the name of your internet provider, an approximate place worked out from the IP address (city, region and country, and for some requests a postal code and time zone) and, for most requests, your account ID. If you secured your account with Apple or Google, the sign in logs also hold your email address and the name Apple or Google shared. My other providers may keep these in their logs for a limited time for security and to keep the service running.

Emails you send me

If you tap Contact support, your mail app opens with a few lines already filled in: the app version, your phone's model and system version, and a short support code taken from your account ID. You can delete them before sending. Emails to [email protected] are received and stored by Hostinger, which hosts the mailbox. I keep them as long as I need to answer you and follow up, and I delete them at the latest two years after your last message.

3. What stays on your phone

CapCats keeps some things only on your phone: the draft of the picture you are working on (until 7 days have passed and CapCats opens again), pictures waiting to upload, likes and saves waiting to be sent while you are offline, a copy of what you last browsed so the app works offline (a copy older than 7 days is never shown), copies of picture files you viewed so they load again quickly (each is removed after 7 days without being viewed, and the oldest go first when there are many), a note of where you were browsing so the app can reopen there, and your app settings. Deleting the app deletes all of this. Photos saved to your gallery stay, because they are your own files.

CapCats asks Android to leave your sign in on that phone, your settings, its databases, your drafts, the things waiting to be sent and the copies of pictures you browsed out of your phone's backup to Google and out of transfers to a new Android phone.

4. The website

This policy also covers capcats.app: the pages that open from a picture or profile link, the page that explains how to delete an account, and the website pages, including the pages that hold this policy, the Terms of Service and the Community guidelines. None of these pages has a sign in.

The website pages are hosted by Hostinger on a server in the United States. They use Google Analytics for every visitor, from the first page you open, without asking first. Google Analytics records the pages you view, an approximate location worked out from your IP address, and details of your device and browser. Google sets its analytics cookies on capcats.app itself to recognize repeat visits, and they last up to two years unless you clear them. I use this to see how many people visit and which pages they read. Google keeps the detailed data for at most 14 months after your last visit. Totals in its standard reports that do not identify you are not bound by that limit. Google explains how it uses this data in its page on information from sites and apps that use its services. Hostinger may keep its own logs of requests to the website for a limited time.

You can stop Google Analytics by blocking scripts from googletagmanager.com in your browser or with a content blocker, or, in a desktop browser, with Google's opt out browser add-on. Clearing or blocking cookies for capcats.app stops Google from recognizing a repeat visit.

If you pick a theme in the website's theme menu, your browser remembers that choice in its own storage. It stays in your browser and is not sent to me.

The link pages, which open from a picture or profile link, and the page that explains how to delete an account are served separately by Cloudflare. They set no cookies, run no analytics and load no scripts. The only things they load from outside the page itself are images from Cloudflare's picture host: the pictures, and a profile photo when there is one. They show only what is public. I don't keep a log of requests to these pages.

Cloudflare sits in front of the whole website. It sees each request, with your IP address and browser details, because it delivers the pages for me. If Cloudflare's security checks suspect that a request comes from a bot, Cloudflare may show its own check page, which can run a script and set a cookie to remember that you passed.

5. What other people can see

  • Always public: your alias, and your profile photo except while it is hidden during a review.
  • Public unless you change it: your first name, your pictures (with their title, meme text and when they were saved), your cats, your Liked collection, and each collection you create. You choose public or private for each picture, each cat and each collection. You can also set a default: every picture you have not set on its own follows it, including pictures you already saved, and the app tells you how many pictures will change before it changes them.
  • A private cat hides its pictures. Other people see a picture only when the picture is public and at least one of its cats is public. A cat that is hidden for review or removed counts as private here.
  • Public with the picture unless you turn it off: the rough area, about 2 km across, where a picture was taken, when Add location is on for it. It follows the picture: whoever can't see the picture can't get its rough area.
  • Never shown to others: the location stored with a picture (rounded to about 1 km), how many likes your pictures got, the pictures you hid, the pictures you have seen, who you blocked, and what you reported.
  • Likes. There is no list of who liked a picture, not even for its creator. Only the creator sees how many likes a picture has. Your Liked collection shows the pictures you liked, newest first, to anyone who opens it, unless you make it private. The app of anyone who opens it also receives the time you liked each one.
  • Other people's collections. When someone saves your picture to their collection, it stays your picture, with your alias on it. If you make it private or delete it, it disappears from their collections too.
  • Links. A link to a public picture or profile opens for anyone, including people without the app and people you blocked.
  • Outside CapCats. Pictures and cards that you or someone else shared or saved outside the app can't be called back.

You can't make a whole profile private. Every profile can be opened, and it shows only what the person looking is allowed to see.

These rules are about what CapCats shows to other people. What is stored on the servers I use, I can read when I need to, for example to review a report or to fix a fault.

6. An honest limit when you make a picture private

When you make a picture private or make private the only public cat it belongs to, when you block someone, or when a picture is withdrawn for review, CapCats stops showing it to other people. That takes effect for new requests within about a minute, and apps that are already open drop it the next time they refresh.

There is one limit, and I'd rather say it plainly. Picture files are stored at long web addresses that are not locked. An address is made of two random IDs that also appear in links: one for your account, which is in your profile link, and one for the picture, which is in the picture's link. So anyone who has a link to a picture and can find its creator's profile can work out the address of its files, and so can anyone who copied a file's address while they were allowed to see it. Such an address keeps loading after the picture becomes private, after its cats become private, after a block, while it is hidden for review and after it is removed for breaking the rules, until the file itself is deleted. None of those deletes the file. Deleting the picture, or your account, does.

To deliver pictures quickly, Cloudflare's network can keep copies of picture files. When you delete a picture or your account, the files themselves are deleted straight away, but a copy kept for speed can go on loading for a while: a copy in Cloudflare's network for up to a year, and a copy on a phone or in a browser that already loaded the picture for as long as that phone or browser keeps it. I do not clear Cloudflare's copies when a file is deleted.

If deleting the files fails, CapCats keeps a note of what is left and tries again every few minutes until the files are gone.

When you edit a picture, the preview image made before your edit is deleted once the edit is saved.

So if you need a picture gone, delete it, and keep in mind the copies described above. One exception: your profile photo. It is a separate copy, made from a picture of one of your public cats when you chose it. Deleting that picture, or making the picture or the cat private, does not remove the copy. To remove it, change or remove your profile photo in Edit profile. When you change or remove your profile photo, the copy you had before is deleted too. If deleting it fails, CapCats keeps a note of it and tries again every few minutes until it is gone. Your profile photo's address holds a random ID that is new each time you change your photo, so it cannot be worked out from your profile link.

7. Automated checks

  • Is it a cat? Your phone checks that a photo shows a cat before a picture can be made. This happens on your phone.
  • Text you write. Your alias when you type one, your first name, titles, meme text, cat names and collection titles go through an automated text check. The check runs on my server while you type, a moment after you pause, and again when you save. It runs for private pictures, private collections and a private first name too, and it also sees words you typed and then removed. For this check the server may send the text to OpenAI's moderation service. OpenAI receives only the text itself, with nothing that says who wrote it. OpenAI's documentation lists no retention for text sent to its moderation service: no abuse monitoring logs and no stored data. It also says that data sent to its API is not used to train its models unless the customer chooses to share it, and I don't. If the text is flagged, you see "Let's keep it friendly. Try different words." and you can change it. When text is checked by OpenAI, I keep a scrambled fingerprint of it with the result, so the same text need not be checked twice. The fingerprint is used for 30 days and then deleted as later checks run. I don't keep the text for this, and the fingerprint is not tied to you. To limit abuse, the server also counts how many checks each account asks for in the current minute.
  • Pictures you save. When you save a new picture, my server sends a small copy of the cat in it to OpenAI's moderation service, to check that it is fine to show to other people. The copy is the cutout alone, 512 pixels in size, without the background or the text. This happens for private pictures too. OpenAI receives only that image, with nothing that says who you are: no account ID, title, meme text, location or cat name. OpenAI's documentation lists the same for its moderation service whatever it checks: no retention, and no use for training unless the customer chooses to share, and I don't. Until the check answers, only you can see the new picture. If the check flags it, the picture stays visible only to you, marked Under review, until I look at it myself. If the check can't run, the server tries again every few minutes, and the picture stays visible only to you until it passes.
  • Reports. When three different accounts, each at least a day old, report the same picture, profile or collection, it is hidden from other people in CapCats automatically until I review it. I look at every report myself. If I remove something, you see a notice on your profile with the reason.

If you think an automated check or an automatic hide got something wrong, write to [email protected] and I'll look at it myself.

8. Who I share your data with

I don't sell your data, and I don't share it for advertising. I use these providers to run CapCats. Each receives only what it needs for its job.

  • Supabase. Runs accounts and the database. It holds your account and what section 2 says I keep on my server, such as your profile, the details of your pictures, your likes, hides, cats, collections, reports, blocks and locations. It does not hold the picture files. The database and the sign in service are in the European Union (Frankfurt, Germany). The server functions, which among other things save and delete your pictures and check your text and your pictures, run in the Supabase location closest to your phone, which can be outside the European Union (for example Zurich in Switzerland). Your picture files and your text pass through that location on their way to storage.
  • Cloudflare. Stores the picture files and delivers them, serves the link pages and the page that explains account deletion, and sits in front of the website. Location: the picture files are stored in Cloudflare's eastern North America region; delivery and the web pages use Cloudflare's network worldwide.
  • Google (Google Analytics for Firebase). Receives usage data from the app, while Share usage data is on. Location: Google may process it in any country where Google or its subprocessors have facilities, including the United States.
  • Google (Google Analytics on the website). Receives data about visits to capcats.app, as described in section 4. Location: the same as for the app's usage data.
  • Google (ML Kit and Google Play services). Find and cut out the cat on your phone, deliver the cutout module, and provide your phone's location service whenever CapCats reads your rough location: when you add a location to a picture and, if you have allowed CapCats to use your location, each time you take a photo, for the gallery copy. Google receives technical data about how ML Kit runs, but not your photo. The details are under "Finding and cutting out the cat" in section 2.
  • Sentry. Receives crash reports and session records. Location: the United States (Iowa).
  • OpenAI. May check the text you write in names, titles and meme text, and checks a small copy of the cat in each new picture you save, as described in section 7. It receives only that text or that image, with nothing that says who you are. Location: OpenAI does not limit this processing to one country, so it can take place in the United States or in another country where OpenAI or its providers operate.
  • Apple and Google (sign in). Only if you choose to sign in with them.
  • AppsFlyer (invite links). When you tap a CapCats invite link, AppsFlyer receives that request, including your IP address and browser or device details, to send you to the right app store. The app itself contains no AppsFlyer software. AppsFlyer keeps this data for up to 24 months.
  • Hostinger. Hosts the website capcats.app, on a server in the United States, and the support mailbox for [email protected].
  • Google Play. If you agree to rate CapCats, the app asks Google Play to show its own rating window. I never learn whether you wrote a review.

I may also disclose data when the law requires it, for example to answer a valid order from a court or an authority, or when it is needed to protect someone's safety.

Nobody besides me can open my accounts with Supabase, Cloudflare, Google Firebase and Sentry, or the tool I use to review reports. The providers' own staff can access data only as their terms allow.

9. Where your data is processed

Think Languages LLC is based in the United States, and my providers process data in several countries, including the United States, the European Union and Switzerland. Your data may therefore be processed outside the country where you live, under data protection laws that may differ from those of your country. Where the law requires safeguards for such transfers, I rely on the ones my providers offer in their data processing terms, such as the European Commission's standard contractual clauses. You can write to me for more information about them.

10. How long I keep your data

  • Your account and what is in it: until you delete the item or your account, with the exceptions in this list.
  • The record of each save: until you delete your account, even after the picture itself is deleted.
  • Earlier preview images of a picture you edited: until the edit is saved. Then they are deleted.
  • Your profile photo: until you change or remove it, or delete your account. Deleting the picture it was copied from does not remove it.
  • Which pictures you have seen: for as long as your account exists.
  • An alias you gave up: it stays reserved for you for 30 days. After that it stays on my list of aliases, still marked as once yours, until someone else takes it.
  • Your sign in sessions: until you sign out while your phone is online, or delete your account.
  • Reports you sent and moderation decisions: there is no set time limit in this version. A report is deleted when you delete your account or when the reported item is deleted. A moderation decision is kept with the item it is about and is deleted with it.
  • Guest accounts nobody can reach any more: no time limit, as section 12 explains.
  • The text fingerprints of the text check: used for 30 days, then deleted as later checks run.
  • Usage data at Google: Google keeps the detailed usage events for 2 months, and the data tied to each analytics ID or installation ID for 14 months after the last event from it. It deletes data that reaches these limits once a month. Totals in Google's standard reports that do not identify you are not bound by these limits.
  • Website analytics at Google: at most 14 months after your last visit for the detailed data. Totals in Google's standard reports that do not identify you are not bound by that limit.
  • Crash reports at Sentry: at most 90 days.
  • Invite link taps at AppsFlyer: up to 24 months.
  • Session records at Sentry: Sentry publishes no fixed period for them. They hold only the scrambled ID described in section 2.
  • Backups of the database: Supabase makes a daily backup of the database, and the last 7 days of backups can be restored.
  • Provider logs: Supabase keeps the logs of the CapCats project (requests, server functions, the database and sign ins) for 7 days. Cloudflare and Hostinger keep their own logs for periods they set.
  • Emails you send me: as long as I need to answer you and follow up, and at the latest two years after your last message.
  • On your phone: drafts until CapCats opens more than 7 days after the photo; copies of pictures you viewed until they have gone 7 days without being viewed; things waiting to be sent, until they are sent.

11. Deleting your account

You can delete your account in the app: Settings, Account, Delete account. Guests can too. If you signed in with Apple or Google, CapCats asks you to sign in once more to confirm it's you.

Deletion is immediate. There is no waiting period and no way to undo it.

What is deleted at once:

  • your profile: alias, first name and profile photo,
  • your pictures and their files, including from other people's collections and Liked,
  • your cats, your collections and your Liked collection,
  • your likes, the pictures you hid, the pictures you have seen and the accounts you blocked,
  • the reports you sent, and reports about your profile, your pictures and your collections,
  • the sign in link to Apple or Google held for your account, and your sign in sessions.

What remains, and for how long:

  • Your alias stays reserved for 30 days, so nobody can take it straight away. After that the word itself stays on a list of released aliases, linked to nobody, until someone else takes it.
  • Backups of the database made before the deletion still hold your data until Supabase removes them. The last 7 days of daily backups can be restored.
  • Logs at Supabase, which can hold your account ID, your IP address and, for a secured account, your email address, stay for up to 7 days.
  • Crash reports already at Sentry stay until they expire, which is at most 90 days after they were sent. They carry your account ID.
  • Session records already at Sentry stay, with only the scrambled ID described in section 2.
  • Usage data at Google. Deleting your account does not ask Google to delete your usage data. That data is labeled with random IDs: an analytics ID for your account and Google's own ID for the app on your phone, never your account ID. Once your account is deleted, my database no longer holds the analytics ID, and my database backups drop it when they expire. Google deletes the detailed usage data when it reaches the limits in section 10. If you go on using CapCats on the same phone, Google's ID for the app on that phone stays the same. Totals in Google's reports that do not identify you are not bound by those limits.
  • Apple. If you signed in with Apple, deleting your account removes the link to your Apple account from CapCats, but CapCats does not ask Apple to remove its permission. You can remove it yourself. On an iPhone, open Settings, tap your name, tap Sign in with Apple, choose CapCats or its developer and tap Delete. On another device, sign in on account.apple.com and open Sign-In & Security, then Sign in with Apple.
  • Emails you sent me are kept as described in section 10.
  • Photos in your phone's gallery stay there. They are your own files.
  • Anything shared outside CapCats, by you or by others, and anything other people saved to their own phones, can't be called back.
  • An earlier address. As explained in section 6, a file address that someone copied or worked out earlier stops working once the file is deleted and the copies kept for speed are gone. A copy in Cloudflare's network, or on the phone or browser of someone who loaded the picture, can keep loading for a while.

If you no longer have the app, see capcats.app/delete-account, or write to [email protected] from the email address of the Apple or Google account you signed in with. I delete an account by hand only when the request comes from that address. Otherwise I'll ask you to install the app, sign in and delete it there, so that nobody can delete someone else's account.

If you hid your email when you signed in with Apple, I only have Apple's relay address for you, so I can't match your email. In that case the only way is to install the app, sign in with the same Apple account and delete the account there. A guest account has no sign in at all, so I can't confirm by email that a request comes from the person who owns it. Delete it in the app, on the phone it lives on.

12. Guests

A guest account can do everything a signed in account can. It lives on one installation of the app. If you delete the app or lose your phone, a guest account and its pictures can't be recovered. To keep them, secure your account with Apple or Google in Settings.

Deleting the app does not delete a guest account. Its public pictures stay visible to other people. If you want them gone, delete your account in Settings before you delete the app. I don't remove guest accounts that nobody can reach any more. They stay, with their public pictures, and there is no time limit on them in this version of CapCats.

Everything in this policy applies to guests in the same way.

13. Children

CapCats is for people aged 13 and over, or the age at which you can agree to this kind of service by yourself in your country, if that is higher. It is not directed at children, and it does not ask for your age. I don't knowingly collect data from children under that age. If you believe a child under that age has used CapCats, write to [email protected] and I'll delete the account once I can identify it.

14. Your rights

Depending on where you live, you may have the right to:

  • get a copy of your data,
  • have wrong data corrected,
  • have your data deleted,
  • object to some uses of your data, or ask me to limit them,
  • take your data to another service,
  • withdraw a consent you gave,
  • complain to the data protection authority where you live or work.

You can do much of this yourself in the app: edit your profile, change who sees what, turn off usage data, remove a location, delete pictures and delete your account. For anything else, write to [email protected]. To protect your account, I may ask you to confirm a request from inside the app or from the email address of the Apple or Google account you signed in with. I answer within one month. If a request is complex, I may need up to two more months, and I'll tell you so within the first month.

I don't sell personal data, and I don't share it for advertising that follows you across other companies' apps or websites.

15. Why I'm allowed to use your data

Some laws, such as those of the European Union and the United Kingdom, ask me to name a legal reason for each use of personal data. These are mine:

  • To provide CapCats to you (your account, sign in, profile, pictures, likes, collections, settings, the cat check, the text check, the picture check and answering your emails): because it is needed for the service you asked for under the Terms of Service.
  • To keep CapCats safe (reports, blocks, moderation, the Community guidelines agreement, the text check, the picture check and provider logs): my legitimate interest in a safe service, and legal duties where they apply.
  • Crash reports and session records: my legitimate interest in finding and fixing faults.
  • Usage data in the app: my legitimate interest in understanding how CapCats is used, so I can improve it. You can object at any time by turning off Share usage data.
  • Analytics on the website: my legitimate interest in knowing how the website is used. You can object with the tools described in section 4.
  • Location on a picture and its rough area: my legitimate interest in letting people find cats near them, limited to an area of about 2 km and never the stored location itself. You can object for any picture by turning off Add location before you save it or by removing the location in Edit picture. Your phone also asks your permission before CapCats can read any location.
  • Keeping or disclosing data when the law requires it: the legal duty that applies.

16. Security

All data travels between your phone and my providers over encrypted connections. Who may see a picture is decided on the server each time it is requested, not by the app alone. Secret keys are kept on the server and never in the app. No system is perfectly secure, and the limit described in section 6 applies.

17. Changes to this policy

If I change this policy, I'll publish the new version on this page and change the effective date at the top. When a change matters, for example a new provider or a new kind of data, I'll also announce it on capcats.app before it takes effect.

18. Contact

Think Languages LLC
1309 Coffeen Ave, Suite 1200
Sheridan, WY 82801
United States
[email protected]