Crizzy Development / SousCard / Privacy policy

SousCard Privacy Policy

This policy applies to the SousCard app for Android and iOS, published by an independent developer. Crizzy Development is the name the apps on this site are published under; it is not a separate legal entity.

Effective September 14, 2026. Last updated September 28, 2026.

The short version. Your recipes, photos and notes are stored on your device. They are yours, and they never leave it unless you send them somewhere yourself. There is no advertising, no collection of your personal information or any personally identifiable information, and no information about you is sold or shared.

SousCard sends anonymous usage analytics. These record which features are used and whether they worked, never what you put into them. This interaction data is collected for the sole purpose of improving the features and usability of SousCard. Analytics are on by default, and you can turn them off at any time in the app's Settings.

The only other thing that can reach us is a Support Export. It exists only if you deliberately create one and send it to us. Both are described in full below.

Information we collect

We collect fully anonymous usage analytics, described in the next section, and nothing else. SousCard has no user accounts, no sign-in and no registration. We do not collect, store, sell or share any personal information, and we have no ability to identify you.

SousCard contains no advertising software and no third-party tracking software. In fact, significant efforts have been made to explicitly avoid such capabilities.

Usage analytics

To learn which parts of SousCard are used and where they fall short, the app sends short, anonymous messages about how it is used. They go to TelemetryDeck, a privacy-first analytics service that processes them on our behalf and stores them in the European Union. TelemetryDeck does not log or store the IP address they arrive from, and keeps these messages for no longer than 12 months. No one else sees this analytics data, for any purpose, advertising included.

What is never sent:

The contents of anything you write, clip or photograph: recipe titles, ingredients, method steps, notes, tags and photos.
Anything you type or search for within the app.
Any part of a web address, including the name of a website you clip from.
File names, and the text of any error message.
Your name, email address or contacts, anything from your device's location services, and any advertising identifier.

What is sent:

Which features are used and how they turn out. For example: that a recipe was clipped from a photo and saved, that a clip did not succeed and at which stage, or that Cook Mode was opened.
Technical details of your device and the app, which help in supporting the variety of devices SousCard is installed on:
- the device model and manufacturer, and its type of processor
- the operating system and its version, the app's version, and where it was installed from (eg. App Store)
- screen size, pixel density and orientation
- language, region and time zone settings, and the direction text is read in
- display and accessibility settings: text size and weight, bold text, dark mode, and various visual accessibility settings
- the local hour and date when a message is recorded
- when the app was first used, how often and for how long it is used, and on how many days
The language a recipe you clip is written in, if it's a language the app supports.
How many recipes your recipe box holds when a clip succeeds.
When you share a recipe, the kind of app you shared it through, such as email, a messaging app, or AirDrop. Never who you sent it to.
The language options you choose under Language Preferences in Settings, sent when the app starts and when you change one.
A random identifier for this installation of the app, so that usage can be counted without knowing who you are. It is created for SousCard alone, so no other app, including any other app of ours, can match it. It is scrambled on your device before it is sent, and scrambled again by TelemetryDeck.

Turning it off. Usage analytics are on by default. To turn them off, open Settings in SousCard and switch off SousCard Telemetry Data. This takes effect straight away:

One last message is sent to record that analytics were turned off. If your device is offline at that moment, this message is not sent at all.
After that, nothing more is sent.

If you turn analytics back on, a message records that too. The rest of the app works exactly the same either way.

Information stored only on your device

The app stores the things you put into it: recipe titles, descriptions, ingredients, method steps, personal notes, tags, and any photos you add. This information is held in the app's private storage on your device. It is not transmitted to us and it is not accessible to us.

Deleting a recipe removes it. Uninstalling SousCard removes all of it, subject to the backup section below.

Camera, photos and documents

Reading text from an image, recognising the layout of a page, and reading a PDF all happen on your device, on both platforms (Android and iOS). No image, page or document is uploaded anywhere. Text recognition uses Google's ML Kit on Android and Apple's Vision framework on iOS; both run offline, on the device, as part of the app.

How the app reaches your camera and photos differs between the two platforms, because the platforms differ:

On Android, SousCard requests no camera or photo permissions at all. Scanning is handled by the document scanner built into Google Play services, which runs outside the app under its own permissions, and attaching a photo goes through the Android system photo picker, which hands the app the single image you chose and nothing else.
On iOS, the app asks for camera access when you scan a page and for photo library access when you attach a picture. iOS will prompt you, and you can decline or change your mind later in Settings. The access is used only for the action you asked for.

When SousCard uses the network

SousCard uses the internet in two situations.

When you clip a web page. If you paste a recipe link into the app or share a web page to it, the app fetches that page directly from the website you named, in order to read the recipe from it. That request goes to that website much as it would if you had browsed to it. The request does not pass through any system of ours, and we receive nothing from it — no shared cookies, no ad revenue, nothing.
When it sends usage analytics, while that setting is on. SousCard does not include your IP address within what it sends, and TelemetryDeck neither logs nor stores it.

Every other part of SousCard works with the network switched off. Nothing in the app waits for analytics to be sent: without a connection, they are held on your device and sent later.

Backup to your own cloud account

Your device's own backup may copy the app's data to your personal cloud account, so that your recipe box returns when you set up a new device. This is a feature of the operating system, not of SousCard. The data goes to your account, not to us, and your platform's terms and privacy policy govern it.

On Android, this is Auto Backup to your Google account. Android caps how much data an app may back up, so on a large library some photos may deliberately stay on the device only rather than push the whole backup over that cap. The app tells you when (and if) that happens.
On iOS, this is iCloud Backup, which has no comparable per-app cap, so the recipe box and its photos are included when iCloud Backup is switched on.

Either can be turned off in your device settings. Neither is controlled by SousCard.

Files you export and share

SousCard can write your recipe box out as a file that you keep or hand to someone else. That file is created by you, goes wherever you send it, and never comes to us. It deliberately contains nothing about your device — no model, no operating system version, no identifiers — because a file you might share with a friend need not carry those things.

When you share a recipe, usage analytics may record that you did and the kind of app you chose, as described above. Neither the file itself, nor the recipient's details, ever reaches us.

Support Exports

Apart from the anonymous usage analytics described above, this is the one way anything reaches us, and it happens only if you choose it.

A Support Export is a separate, clearly labelled action. It produces the same kind of file as an ordinary export, plus a description of your situation that makes a support conversation possible without several rounds of questions. The app shows you what the file contains before it creates it.

The added description contains facts about the software and the device model, and nothing that identifies you:

Device model and manufacturer, operating system version and build, screen size, text size setting, language and time zone.
App version and build, database and file-format versions, and the store region.
How many recipes and photos your library holds, and how many photos are outside your platform's backup.
Your recipes, because a Support Export is built on an ordinary backup export, and that is what a backup contains.
Your photos only if you switch them on. They are excluded by default, and are only worth including when the problem is with photos themselves.

It contains no advertising identifier, no vendor or device identifier, no account and no serial number. Nothing in it distinguishes two people using the same model of phone.

A Support Export is never sent automatically. You create the file, you look at it if you wish, and you send it to us yourself. When you do, we use it only to answer your support request, and we delete it once that conversation is finished.

Crash reports

SousCard contains no crash-reporting software. Usage analytics may record that something did not succeed, and at which stage, but never an error message or a crash log.

If you have turned on your platform's own diagnostics sharing ("usage and diagnostics" on Android, "share with app developers" on iOS), your platform may make anonymous, aggregated crash and performance information available to us through Google Play or App Store Connect. That reporting is a function of the operating system and the store, is controlled by your device settings, and does not identify you to us.

Children

SousCard is not directed to children under 13, and we do not knowingly collect personal information from anyone, children included.

Your choices

Usage analytics can be turned off at any time in SousCard's Settings, as described above. The analytics identifier is scrambled on your device before it is sent, so neither we nor TelemetryDeck can tell which analytics came from you, and there is nothing we could find to disclose or delete upon request.

Otherwise, we hold no information about you. Everything the app holds is on your device and under your control: delete individual recipes in the app, or uninstall the app to remove all of it. To remove a copy held by your platform's backup, use your Google or iCloud account's backup settings.

If you have sent us a Support Export and would like it deleted before the support conversation ends, ask and we will delete it.

Changes to this policy

If this policy changes, the updated version will be posted at this address with a new effective date. Material changes will also be noted in the app's release notes.

Contact

Questions about this policy: crizzydevelopment@gmail.com.