Skip to content

Privacy

Last updated 17 November 2026

This page explains what we collect when you visit canitrustthat.com, use the app at app.canitrustthat.com, subscribe to our emails, send us a brief (a description of work you want done) or write to us. "We" means CITT LLC, the company that runs CanITrustThat. "Personal data" means information that can be linked to you.

Summary

  • We never sell personal data, and we never share it for advertising. The site is ad-free.
  • On our public pages, browsers are allowed to load scripts, fonts and images only from our own site. In the app, scan videos (screen recordings of apps we test on our phones) and some images are loaded from our file storage at OVH, the company that hosts our server.
  • Page views and session recordings (a replay of the page layout, clicks and scrolling, with all text hidden) are sent to PostHog, an analytics company in the US. They are sent through our own server, without your IP address, email or account ID. In the European Economic Area (the EU plus Norway, Iceland and Liechtenstein) and the UK, nothing is sent until you choose Yes. If your browser sends Global Privacy Control or Do Not Track (privacy settings in some browsers), nothing is sent to PostHog.
  • If you have an account, we keep your email address and what you do in the app: scans, uploads, questions and answers. Your questions, and the parts of an app's code needed to answer them, are sent to Claude AI models from Anthropic, which write the answers.
  • You can ask us for a copy of your data, or ask us to correct it or delete it, wherever you live. Write to [email protected]. We answer within 30 days.

Who we are

CanITrustThat is run by CITT LLC, a US company. Filip Luchianenco runs it. For anything about this page or your data, email [email protected].

When you visit the site

Cloudflare. Every request to our site is sent through the network of Cloudflare, Inc., a US company that protects the site and delivers its pages. Cloudflare receives your IP address (the number that identifies your device or network on the internet) and the request itself. Cloudflare adds a country code and a state or province code to each request. We use these codes only to decide whether analytics starts on or off for you (see Analytics and session recording). Cloudflare keeps its own logs under its own terms.

Cloudflare also asks browsers to send it a report when a request to our site fails. A browser that supports these reports may send Cloudflare the address that failed, the page you came from, our server's IP address, the type of error and how long the request took. The report also includes your browser's identification string (a line of text naming your browser, its version and your operating system). Cloudflare receives your IP address when the report arrives, as with any request.

Cloudflare adds two small scripts to our public pages, served from our own address. One turns the email addresses on the page back into links after hiding them from spam robots. The other is a bot check. Your browser blocks the bot check under our pages' security settings.

Server logs. Our web server records each request in its log: your IP address, the time, and the page address including any part after "?" (the part of a web address that can contain extra details). The log also records the response code (whether the request worked), the size of the response, the page you came from, and the name and version of your browser. We use the log to run the site and protect it from abuse. When your browser blocks a script or file under our pages' security settings, it may send our server a short report. We log what was blocked and the page path.

Request limits. We also use your IP address to limit how many requests we accept from one device or network. Most of these counts are kept only in the server's memory and are lost when it restarts. Four kinds are stored in our account database. In the list below, "network" means your IP address. For an IPv6 address, it means the first half of the address, which identifies your network.

  • When you ask for a sign-in code by email: your network, your email address and the time.
  • When you sign in to our plugin (the citt command for the coding tools Claude Code and Codex): your IP address and the time.
  • When you ask to change your account's email address: your network, your account ID, the new email address and the time.
  • When you send a brief on the Work with us form: your network, the email address you entered and the time.

Cookies and browser storage. A cookie is a small text file a website stores in your browser. On public pages, we set one cookie, theme, and only when you switch between light and dark mode. Its value is light or dark, and it expires after one year. When you sign in to the app, we set a citt_signed_in cookie with the value 1 for all of canitrustthat.com. A small script on public pages checks for it and, if it is there, changes the Sign in link in the header to Dashboard. The full list, with the app's cookies, is on the Cookies page. Storage used by analytics is listed in the next section.

Other companies on our pages. On our public pages, browsers are allowed to load scripts, fonts and images, and to open connections, only from our own site. In the app, scan videos and some images are loaded straight from our file storage at OVH (see Companies that receive data), so OVH receives your IP address for those files.

Analytics and session recording

We use PostHog, Inc., an analytics company in the US, to see which pages people use and where the site breaks. What we send is pseudonymous: it is linked to a random ID instead of your name, email address or account.

What a page view contains.

  • the page address and the page you came from, both without the part after "?";
  • your browser and operating system with their versions, and your browser's full identification string, which it sends to every website;
  • your device type, browser language and time zone;
  • your screen and window size;
  • when you opened and left the page;
  • random IDs;
  • the version of PostHog's code.

We remove the page title before sending. In the app, a page address can contain the ID of a project or a scan. We can link those IDs to an account.

What a session recording contains. The page layout, clicks, scrolling and mouse movement. Before anything is sent, the following are replaced by asterisks (***):

  • all text on the page;
  • the text of labels, titles, image descriptions and placeholders;
  • everything you type into a field;
  • email and phone links.

Link and image addresses are recorded without the part after "?". A recording leaves out the contents and headers of the site's network requests (the data a page exchanges with our server in the background).

How it is sent. Page views and recordings are sent from your browser to our own server, at /ingest on our site. We forward them from there to PostHog's US servers, after removing your IP address and your cookies. Every event (each page view or piece of a recording) is marked with the placeholder IP address 0.0.0.0 instead of yours. PostHog's lookup of your location from your IP address is turned off. Each event is linked to a random ID; your email address and account ID are kept out of every event. PostHog's code is served from our own site.

What starts by default, by region. Our server decides whether analytics starts on or off for you, from the country and state codes that Cloudflare adds to each request. We use the codes for this decision only, and discard them after it.

Where you arePage viewsSession recording
The EU, Norway, Iceland, Liechtenstein, the UK, EU territories with their own country code (such as Réunion), and anywhere we cannot tell where you areOff until you choose YesOff until you choose Yes
The US states of California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, Nevada, New Hampshire, Oregon, Pennsylvania and Washington; US territories; Canada; and every country not named in this table, including SwitzerlandOnOff until you choose Yes
Every other US state, Washington, DC, Australia, New Zealand, Japan and SingaporeOnOn; the banner tells you and has a Stop recording button

In the US and Canada, if we can see the country but not the state or province, nothing is sent until you choose Yes.

Global Privacy Control and Do Not Track. With these settings, offered in some browsers, you ask websites not to track you. If your browser sends either one, nothing is sent to PostHog and the banner stays hidden.

Changing your choice. Open Analytics choices at the bottom of any public page, set the switches for page views and session recording, and choose Save. The app at app.canitrustthat.com keeps its own choice. To change a choice made in the app, clear the site data for app.canitrustthat.com in your browser's settings. This also signs you out, and the banner appears again.

What analytics stores in your browser. localStorage and sessionStorage are storage areas in your browser. They work like cookies, with one difference: their contents are sent to a website only when a script on the page reads and sends them. sessionStorage is cleared when you close the tab.

NameWhereWhat it is forHow long
citt-analytics-consentlocalStorageYour choice in the banner, so it applies on later visitsUntil you clear this site's data
__ph_opt_in_out_ followed by our PostHog project keylocalStorageSet to 0 when you turn off both page views and session recording, so PostHog sends nothing; set to 1 if you later turn either one back onUntil you clear this site's data
Keys starting with ph_ followed by our PostHog project keysessionStorageRandom IDs for the tab and the session, so the pages you open in that tab form one recording; written while recording is on; the IDs are sent to PostHog with the recordingUntil you close the tab
A key starting with ph_replay_pending_buffer_sessionStorageMasked recording data still unsent when you leave a page; sent from the next page you open in the same tab, then deletedUntil the next page in the tab sends it, or you close the tab

With page views on and recording off, PostHog stores nothing in your browser beyond the __ph_opt_in_out_ setting in the table. Each page load gets a new random ID, which is kept only in memory and deleted when you close or leave the page.

If you have an account

Accounts are for people 18 and over. You sign in with your email address and a 6-digit code we email to you. We refuse sign-ups with addresses from throwaway email services (addresses made to be used once).

For each account we store:

What we storeWhy
Your email address, display name, when the account was created, when you last signed in, and when the account was first and last active in our research toolsTo sign you in and contact you about your account
Your sign-in sessions (start, last activity, expiry), and the current sign-in code with the number of attempts, until the code expiresTo keep you signed in and stop people guessing codes
Requests to change your email addressTo make the change
The scans you submit, free scans saved to start later, and the email address to notify when a scan finishesTo run scans and tell you when they finish
The app files (builds) you upload, with the file name, size, SHA-256 fingerprint (a code computed from the file that identifies it), package ID (the app's unique name, such as com.example.app) and version, up to 10 GiB per accountTo scan them
Your projects, your questions and their answers, your scrutiny requests (asking the AI model to check a finding again), and your chats about a scan's findingsTo answer you and keep the history
For each question, the text you wrote, the wording our model suggested, and which version you choseTo show and keep the version you chose
The exports you create and each download of themTo deliver them
A record of each counted action, with its units and what the AI model cost us, and each time a plan limit appliedTo bill you and apply plan limits
A log of account events, such as uploads and scan submissionsFor your history and for support
Your team and your role in itTo give team members access
Your API and plugin tokens (keys that let the plugin or your own software sign in to your account): a hash of each secret (a one-way scramble we cannot turn back into the secret), the client name, and when each was created and last used; and the plugin's sign-in requestsTo let the plugin and API sign in
Your plan, its status and renewal date, your billing email, your customer and subscription IDs at Stripe (our payment company), and the messages Stripe sends us about your subscriptionFor billing
Changes our staff make to your plan, features or limits, with who made each one and why, and staff notes on the accountFor support

Who can see your work. Every scan you start is private, on every plan. A scan you start can be opened by your account, by the other accounts on your team or project, and by CanITrustThat staff. A free rule scan can be opened only by your account and by CanITrustThat staff. Your uploaded builds, your questions and their answers, and your chats are shown only to you, the other accounts on your team or project, and CanITrustThat staff.

Uploaded builds are stored on our servers at OVH in Virginia, US. An unfinished upload is deleted 24 hours after its last data arrives.

Questions, app code and AI models

Claude AI models from Anthropic PBC, a US company, write the answers to questions, scrutiny requests and chats about a scan's findings. They also write the findings of Deep scans (AI reviews of an app's code). We send Anthropic:

  • the text of your question or chat message, and for a chat, the findings it is about;
  • the files of an app's decompiled code (code turned back into a readable form) that the model reads to answer, including the code of a build you uploaded when you ask about it.

Before you submit a question, its text is also sent to a Claude model, which suggests clearer wording. We store your text, the suggestion and the version you chose.

Screenshots from our test phones. We test apps on real phones, signed in with our own test accounts. Screenshots of the tested app's screens may be sent through OpenRouter, an AI model service in the US, to outside AI models such as Google's Gemini, and to Anthropic's Claude models. The models describe the tested app's screens so the app can be operated during the test.

Store search. When you search for an app, we send your search text from our server to Google Play, Apple's App Store search service and SerpApi, a search service used when the first two fail. Your IP address stays on our server. We keep the search text and the results in a cache (a store of recent results) on our server. The cache contains the search text and results only, without your IP address or account.

Payments and donations

You pay for plans through Stripe, Inc. You enter your card on Stripe's own page, under Stripe's privacy policy. Your card number is sent to Stripe only. What we store about your plan is listed in If you have an account.

Donations are arranged by email to [email protected]. We handle those emails like any other email to us (see If you send a brief or write to us).

If you subscribe

We send our email subscription for new teardowns (our in-depth reports on single apps) and blog posts with newsletter software installed on our own server. For each subscriber, we store:

  • your email address and your newsletter choice;
  • when you subscribed, and each change to your subscription;
  • when you signed in to your subscription settings, and when you were last active.

When you subscribe or open your settings, we email you a sign-in link. The link's record contains your email address and IP address, and it is deleted after 24 hours. The newsletter software also uses your IP address to limit how many sign-up emails are requested from one network.

We have set the newsletter software so it skips looking up your location from your IP address and skips fetching a profile picture for your email address from Gravatar (a service that links pictures to email addresses).

Every subscription email has an unsubscribe link, and unsubscribing stops the emails. We keep your subscriber record until you ask us to delete it. We back up the subscriber database every night and keep the 14 newest backups on our server. Backups are also copied to a separate archive that we run.

Subscription emails and sign-in links are sent through Mailgun, an email delivery company in the US.

If you send a brief or write to us

The Work with us form. On the form at /work-with-us, you enter the type of request, your message, your organization if you choose to, and your email address. When you send it, we store a copy in our account database. We also email the brief to [email protected]. That email includes the address of the page you sent it from and, if you are signed in, your account's email address. Replies to it go to the email address you entered.

The stored copy contains your email address, organization, request type, message, the time, your account ID if you are signed in, and a keyed hash of your network address (a code made from the address with a secret key). Separately, we store your network and the email address you entered with the time, to limit how many briefs one network or one email address can send (see Request limits in When you visit the site).

Booking a call. The Book a call link opens a booking page on Proton Calendar, a scheduling service run by Proton AG with its own privacy notice. The details you enter there are sent to us so we can hold the call.

Email to [email protected]. Our mailbox is hosted by Proton AG in Switzerland. We keep briefs, emails you send us, and requests about your data there.

Companies that receive data

CompanyWhat it receivesWhyWhere
Cloudflare, Inc.Every request to our site, with your IP address; reports of failed page loadsProtects the site and delivers its pagesUS company; requests are handled on Cloudflare's network
OVH US LLCEverything stored on our server and file storage: databases, logs, uploaded builds, scan videos, subscriber data and backups; in the app, your IP address when your browser loads scan videos and images from our file storageHosts our server and file storageVirginia, US
PostHog, Inc.Page views and masked session recordings, without IP address, email or account IDAnalyticsUS
Anthropic PBCThe text of questions and chats, the findings a chat is about, and decompiled app code; it may also receive screenshots from our test phonesWrites answers and Deep scan findings; describes test phone screensUS
OpenRouter, Inc.May receive screenshots of tested apps from our test phones, passed on to outside AI models such as Google's GeminiDescribes test phone screensUS
Stripe, Inc.Your card and billing details, entered on Stripe's pageTakes payment for plansUS
Mailgun Technologies, Inc.Your email address and the content of sign-in codes, scan notices, subscription emails and briefsDelivers our emailUS
Proton AGBriefs and emails to [email protected]Hosts our mailboxSwitzerland
Google LLC, Apple Inc., SerpApi LLCThe text of a store search, sent from our serverFinds the app you searched forUS
Cal.com, Inc.What you enter when you book a callSchedules the callUS; Cal.com's own privacy notice applies

Apart from Proton, all of these companies are in the US, and our server is in the US. If you are outside the US, your data is processed in the US.

How long we keep it

DataHow long
Sign-in codesDeleted by an automatic cleanup, run every hour, after they expire
Sign-in sessionsDeleted by the same hourly cleanup after they expire (cookie lifetimes are on the Cookies page)
Subscription sign-in links, with your IP address24 hours
Request counts kept in memoryUntil the server restarts
Stored request-limit records (sign-in codes, plugin sign-in, email changes, briefs)Until you ask us to delete them
Account data and uploaded buildsWhile your account is open, or until you ask us to delete them
Unfinished uploads24 hours after their last data
Subscriber recordsUntil you ask us to delete them
Briefs, the stored copy and the emailUntil you ask us to delete them
Emails to [email protected]Until you ask us to delete them
Your analytics choice in your browserUntil you clear this site's data
Nightly backups of our databasesKept on our server and copied to a separate archive that we run; on our server, the 14 newest backups of the research and subscriber databases are kept
Cloudflare's logsSet by Cloudflare's own terms

Your rights

Wherever you live, you can ask us to:

  • send you a copy of the personal data we hold about you;
  • send it in a portable format (a common file format you can take to another service);
  • correct data that is wrong;
  • delete your data;
  • stop using your data for a purpose you object to;
  • limit how we use your data while we look into a question you raise.

Write to [email protected] from the email address your request is about, so we know the request comes from you. We answer within 30 days.

You can also:

  • withdraw your analytics consent at any time under Analytics choices at the bottom of any public page (for the app, see Changing your choice);
  • unsubscribe from our emails with the link in each email.

If you are in the European Economic Area or the UK, you can complain to your data protection authority, the government office that enforces privacy law where you live.

Children

CanITrustThat is made for adults who research apps: privacy researchers, journalists and lawyers. Accounts are for people 18 and over. If we learn we hold personal data of a child under 13, we delete it.

How we protect data

  • Every page is served over HTTPS (an encrypted connection), and browsers are told to use HTTPS for this site for one year.
  • Our server accepts connections only from Cloudflare, and checks Cloudflare's certificate (a digital proof of identity) on each one.
  • Sign-in cookies are hidden from scripts on the page.
  • API and plugin token secrets are stored only as hashes.
  • The admin side of our newsletter software is open only to our staff over a private connection.
  • On our public pages, browsers are allowed to load scripts, fonts and images only from our own site. In the app, images and videos are also allowed from one other address, our own file storage at OVH.

Changes to this page

When we change this page, we update the date at the top of the page.

Contact

Questions and requests about this page or your data: [email protected].