Crizzy Development / SousCard / Support
How to reach a person, and answers to the questions that come up most.
Email crizzydevelopment@gmail.com — a real person reads it. If you are reporting a problem, a Support Export saves a great deal of back and forth; see the last section.
Two ways. Paste the link into the app with "Clip a link", or use your browser's share button and pick SousCard. The app reads the recipe out of the page's own structured data, so it gets the ingredients and steps rather than the article around them.
SousCard reads the machine-readable recipe that most cooking sites publish inside their pages. A site that does not publish one cannot be clipped this way. Photographing the page or saving it as a PDF and importing that will usually still work.
Yes. "Clip a photo" opens a scanner and the text is read on your device. Handwriting is harder than print, so expect to correct more of it — which is why every import stops at a review screen before saving.
They mark a field the app was not confident about. Nothing is wrong; it is asking you to confirm rather than guessing silently. Once you confirm a field it stays confirmed, and a later re-import will not overwrite it.
It should not — Cook Mode holds the screen awake while it is open. If your device turns it off anyway, check whether a battery saver is overriding the app.
In landscape, ingredients pin to a column beside the steps. In portrait they collapse into a drawer above them. It follows the orientation rather than the device, so rotating a phone gives you the wide layout too.
On your device, in the app's private storage. There is no account and no server. See the privacy policy.
Your device's own backup carries them — Auto Backup to your Google account on Android, iCloud Backup on iOS — and restores them when you set up a new device, provided backup is switched on in your device settings.
On Android there is one wrinkle worth knowing: the operating system caps how much data an app may back up. Photos are large, so on a big library SousCard keeps some photos on the device only rather than push the whole backup past that cap, and tells you when that happens. Exporting your recipe box to a file is the way to keep a copy of everything. iOS has no equivalent cap.
Yes, apart from clipping a web link — that needs to fetch the page. Scanning, reading PDFs, editing and cooking all work with the network off.
Yes. Export writes your recipe box to a file you can send however you like, and the other person imports it. The file carries your recipes and photos and nothing about your device.
In Backup & Sharing there is a Support section with a Support Export. It produces a single file containing your recipe box plus a short description of your device and app version — the things we would otherwise have to ask you for one at a time.
The app shows you exactly what the file contains before it creates it. Photos are left out by default; include them only if the problem is with photos themselves. Nothing is sent automatically — you create the file and email it to us.
What it does not contain: any identifier, account or serial number. The privacy policy lists the contents in full, and says what happens to a Support Export after your question is answered.
Email crizzydevelopment@gmail.com with what you were doing and what happened. Screenshots help more than descriptions, and the app version — shown at the bottom of the Backup & Sharing screen — helps more than either.