Countcall

Countcall privacy policy

Last updated: 7 November 2026

Who is responsible: The Sjöstrand Project AB, Tallhedsvägen 23b, 141 42 Huddinge, Sweden Contact: hello@sjostrand.ai

The short version

  • Your workouts, settings and workout history stay on your phone. There is no sign-up. The app does create an anonymous user ID for you automatically (see below).
  • Your voice is turned into text on your phone. The sound is never sent anywhere.
  • When you change a workout by voice, the resulting text and the workout go to our server and to Anthropic, which interprets it.
  • If you use the free version, Google shows ads and, depending on where you are and what you choose, may use an advertising identifier.
  • On every launch, even if you never use voice or buy anything, the app creates or reuses a random anonymous Firebase user ID and tells RevenueCat that ID. Google (Firebase) and RevenueCat therefore receive technical data from every user.
  • We have not added our own analytics or crash-reporting service. The third-party SDKs we use (Google ads, Firebase, RevenueCat) collect some technical and diagnostic data as described below.

What Countcall collects, why, and who gets it

Kept only on your phone

Your workouts, your settings, your workout history and the date of the last ad. We do not send these to our server, except the workout you are editing by voice (below). The app does, on its own, contact Firebase and RevenueCat with your anonymous user ID at every launch (below). Deleting the app deletes this data.

Voice edits

You hold the microphone button and speak. Countcall asks for microphone and speech-recognition permission. Recognition runs on your phone only; if your phone cannot do that, Countcall does not use the microphone and offers typing instead.

When you send a voice edit, the app sends:

  • the text of what you said (or typed),
  • the workout you are editing (or nothing, when you are creating one),
  • your phone’s language setting.

This goes to our server (Google Firebase Cloud Functions, region europe-west1, Belgium). The server passes the same text to Anthropic’s API (model Claude Haiku 5.5), which returns the new workout. We use Anthropic only to carry out your request.

Our server does not save your text or workout, and our own code’s log lines do not include them. If a provider (Anthropic, Google) returns an error, its error message may be written to the server’s logs by the platform; we have not verified what those messages can contain. The server keeps small counters per anonymous user (see “Anonymous account” below) so it can apply the free-tries limit and daily limits.

How long Anthropic keeps what we send is set by Anthropic. Anthropic says it deletes inputs and outputs from its systems within 30 days of receiving or generating them. There are exceptions: it keeps them longer where the law requires, where it needs them to enforce its usage policy (for up to 2 years if its automated safety systems flag a request as a policy violation, and the safety scores for up to 7 years), and where a customer has agreed other terms with it.

Anonymous account, Firebase and app check

On first launch, and again on every launch, the app signs you in anonymously with Firebase Authentication (reusing the same ID after the first time) and tells RevenueCat that ID. This happens whether or not you ever use voice, feedback or a purchase. There is no name, email or password. Firebase App Check (Play Integrity on Android, App Attest or DeviceCheck on iOS) proves to our server that the request comes from the real app. All of this is provided by Google.

When these Google services run, Google receives your IP address, the anonymous user ID, Firebase installation identifiers and device and app attestation data, and our server (Cloud Functions, which runs on Google Cloud) receives your IP address, user agent and user ID with each request, which Google’s platform request logs can record. Google says it uses this to run the service and prevent abuse (provider documentation, not verified by us).

Our own server stores, per user ID: how many free voice edits you have used, the time of in-progress ones, today’s date, and counters for free tries and daily limits (voice edits, feedback messages, and a daily count of studio voice names, used once studio voices launch). It also stores a server-wide daily count of feedback messages. No other data is stored with the ID.

We keep these counters while you use the app. They are deleted when you tap Delete my data in Settings, and automatically 12 months after you last used the app.

Feedback you send

Settings, then Feedback. You write a message (up to 4,000 characters) and pick Bug, Idea or Other. Optionally you add your email address, so we can reply. A switch, on by default, adds your device details: operating system, OS version (on Android, the API level number), app version and phone model (on iPhone, only “phone” or “tablet”). Turn the switch off and none are sent.

The message goes through our server and is emailed by Resend (an email sending service) to hello@sjostrand.ai. We use it to read and answer feedback. Our server does not store the message. It remains in the mailbox and at Resend; Resend keeps sent email content and logs for 30 days on the plan we use (Resend’s documentation: 30 days on all its plans), and we delete feedback emails when we no longer need them to answer you, and at the latest 12 months after we receive them.

Purchases

RevenueCat, our purchase-management service, is active for every user: it is set up at launch and receives your anonymous user ID, plus the technical data its SDK collects (such as IP address and device data) as described in its own policy. If you buy a subscription or the one-time purchase, the store (Apple or Google) handles payment; we never see your card, and RevenueCat also receives your purchase and entitlement status. Our server asks RevenueCat which plan a user ID has, to decide whether you get unlimited voice edits. RevenueCat’s data processing agreement with us gives no fixed retention period: it keeps the data until our agreement with it ends. After that, we have 30 days to ask it to return or destroy the data, and it may then delete it from its live systems, subject to its standard backups and archives. Its own privacy policy says it keeps personal data for as long as the account relationship lasts and for six years after that.

Ads (free version)

Free users see a banner ad and sometimes a video ad, supplied by Google AdMob. Paid users see none.

  • Ads are requested only after Google’s consent form (shown by Google’s User Messaging Platform) allows it. Where the law requires a consent form, you see it after your first finished workout. You can reopen it from Settings, Privacy and terms.
  • Android: if you allow, Google may use your Android advertising ID to personalise ads. You can reset or delete that ID in Android settings.
  • iPhone/iPad: Countcall does not ask to track you and asks Google for non-personalised ads. It does not use the iOS advertising identifier (IDFA).
  • Whatever the platform, the Google Mobile Ads SDK itself collects some data, which Google lists as: IP address (and from it approximate location), ad and app interactions (launches, taps, video views), diagnostic and performance information, and device identifiers. Google uses this for advertising, analytics and fraud prevention. See Google’s AdMob data-disclosure pages for the current list.

Google’s retention: set by Google, see its privacy policy.

What we do not collect

We have not added our own analytics or crash-reporting service to Countcall; see the technical data collected by Google and RevenueCat above. We do not collect your contacts, photos or precise location. We do not sell your data.

Your choices

  • Skip the voice feature, the feedback form and purchases: Firebase (anonymous ID, app check) and RevenueCat still receive data at every launch, and so do the ad services if you are on the free version. You cannot turn the anonymous ID off.
  • Answer or change your ad consent in the Google form (Settings, Privacy and terms, where offered).
  • Switch off “device details” before sending feedback; leave the email field empty.
  • Reset your Android advertising ID in Android settings.
  • Delete the app: removes everything on your phone. The anonymous user ID and counters on our server remain unless you ask us to delete them (see below).
  • Delete your data in the app: Settings, then Delete my data. This deletes what our server holds under your anonymous ID (the free-tries and daily counters) and resets the app on your phone. You can also email hello@sjostrand.ai and ask us to delete that data, or ask what we hold. Tell us your user ID if you can find it; if you cannot, we may not be able to match your request to any data.
  • What we cannot delete: purchase records that Apple or Google and RevenueCat keep under their own terms, and data that Google’s services collect on their own (see above). Feedback emails we have already received are not removed by the app; we delete them on request if you email hello@sjostrand.ai.

Where data goes

Our server runs in Belgium (europe-west1). Anthropic, Google (AdMob and Firebase, including Authentication and App Check, which are not limited to the function region), RevenueCat, Resend and Vercel may process data in other countries, including the United States. When data leaves the EU, each provider relies on the following, according to its own published terms:

  • Anthropic: Standard Contractual Clauses (and the UK Addendum) in its data processing addendum, which is part of its commercial terms. Its addendum does not mention the EU-US Data Privacy Framework.
  • Google (Firebase and Cloud Functions): Google states that it is certified under the EU-US Data Privacy Framework; its processor terms add Standard Contractual Clauses as a fallback.
  • Google (AdMob): AdMob is a Google LLC service. Google states that Google LLC has certified under the EU-US Data Privacy Framework (and its UK extension).
  • RevenueCat: Standard Contractual Clauses (and the UK Addendum) in its data processing addendum. We found no mention of the Data Privacy Framework.
  • Resend: Resend states in its data processing addendum that it is certified under the EU-US Data Privacy Framework; the addendum also includes Standard Contractual Clauses. Our sending domain is set up in Resend’s EU region (Ireland), but Resend says its primary processing takes place in the United States.
  • Vercel: Vercel states that it complies with the EU-US Data Privacy Framework; its data processing addendum includes Standard Contractual Clauses.

Children

Countcall is not directed at children. The app is for adults and teenagers.

Changes

If this policy changes, we will update the date at the top and, for material changes, tell you in the app.

This website

This is about the website, not the app. The website has no sign-in.

  • Hosting. The site is a static site served by Vercel Inc. (United States), our processor. To serve a page, Vercel receives each visitor’s IP address and browser details, and derives a city and country from the IP address. Vercel’s runtime logs, which cover requests handled by its functions, rewrites and cache, are kept for one day on the plan we use (Vercel Pro); Vercel gives no fixed period for its other service data and says it keeps it for the minimum necessary period. When you submit the sign-up form, your request passes through Vercel, which forwards it to our Google Cloud function in Belgium (europe-west1). Our function does not read your IP address, but Google’s infrastructure still receives the request. Our legal basis is our legitimate interest in running a working, secure site (GDPR Art. 6(1)(f)). We keep no logs of our own. For transfers outside the EU, see “Where data goes”.
  • No cookies, no analytics, no third-party requests. The site sets no cookies, has no analytics and loads nothing from other companies. Its fonts are served from our own site.
  • The waitlist. We store your email address, the page you signed up on, when you signed up and when you confirmed, and which version of the sign-up text you saw. We use it to send you one email when the app launches. The legal basis is your consent, which you give by clicking the confirmation link we email you. Google (Firebase) stores the data and Resend sends the emails. Resend keeps the sent email and its logs for 30 days on our plan. An address you do not confirm is deleted automatically about a week after our last email to it. A confirmed address is deleted after the launch email, and at the latest about 12 months after you confirmed. To leave the list, email hello@sjostrand.ai or reply to the launch email.

Contact

hello@sjostrand.ai