Privacy policy
Last updated October 27, 2026
RecipeScale has no account and no server of its own. Here is exactly what leaves your iPhone, and why.
What stays on your iPhone
Everything you put into RecipeScale is stored on your device: the ingredients you paste, your saved recipes, notes, favorites and settings. There is no RecipeScale account and no RecipeScale server. When you share or copy a scaled recipe, the text goes only where you send it.
From 1.0.1 on, a CSV export is first saved as a file in the app’s cache folder on your iPhone, then the share sheet opens. That file stays on the device, and the export goes only where you send it.
Your clipboard
In 1.0, when you open the Scale screen with an empty ingredient box, RecipeScale may check whether the text on your clipboard looks like a recipe, so it can offer a Paste button. iOS may ask you to allow this. From 1.0.1 on, RecipeScale reads the clipboard only when you tap Paste. Either way, this happens on your iPhone. The clipboard text isn’t sent anywhere, and it only goes into the ingredient box if you tap Paste.
iCloud
iCloud sync is on unless you turn it off in RecipeScale’s Settings. Your saved recipes and settings are then copied to your private iCloud database so they reach your other devices. Apple stores that copy under your Apple ID. I can’t see it. Apple’s privacy policy applies.
Purchases
Apple handles payment for RecipeScale Pro. To check whether Pro is active, the app asks RevenueCat when it starts. RevenueCat receives a random app user ID, your purchase receipts and basic device details such as the iOS version. RevenueCat does not get your name, email or payment details, and neither do I.
Fonts and icons
Versions before 1.0.1 load their typefaces and icons from Google Fonts when they start, which means Google receives your device’s IP address. Google’s privacy policy applies to that. From 1.0.1 on, the fonts and icons ship inside the app and nothing is loaded from Google.
No tracking
RecipeScale has no analytics, no ads, no tracking SDKs and no advertising identifier. It doesn’t send notifications, and it doesn’t use your camera, photos or location. After you’ve cooked a couple of recipes in cook mode, iOS may show Apple’s standard rating prompt.
Diagnostics
In 1.0, tapping the version number at the bottom of Settings seven times opens a diagnostics panel for support. It shows what RevenueCat reports about your purchase: a shortened form of the app’s public RevenueCat key, your anonymous user ID, the product names, prices and dates. It is only shown on your screen and nothing in it is sent anywhere. From 1.0.1 on, the App Store version has no such panel.
Deleting your data
From 1.0.1 on, open Settings in RecipeScale and tap Clear all data. That removes your saved recipes, settings and the recipe you have open from this iPhone. With iCloud sync on, it also clears them in iCloud, and your other devices with 1.0.1 or later drop the same recipes on their next sync.
In 1.0, Clear all data removes your saved recipes and settings from this iPhone. It doesn’t delete the copy in iCloud, and while sync is on, that copy comes back the next time the app opens. To delete it, open the iPhone’s Settings, tap your name, then iCloud, Manage Account Storage, RecipeScale, and delete the data there, then clear the data in the app. A few small things, like the recipe you last had open, stay on the device until you delete the app.
Deleting the app removes everything RecipeScale stored on that iPhone.
Children
RecipeScale doesn’t collect personal information from anyone, children included.
Your rights
Under the GDPR you can ask what data is held about you and have it corrected or deleted. Because RecipeScale keeps nothing on its own servers, most requests go to Apple or RevenueCat, but write to me and I’ll help.
This website
This site sets no cookies, runs no analytics and loads nothing from other servers. Its fonts are served from here.
Contact
Alex Galkin is responsible for RecipeScale and this policy (the controller under the GDPR). Write to alex.galkin.dev@gmail.com, or by post to Tristanstr. 2, 45473 Mülheim an der Ruhr, Germany. If this policy changes, the new version will be posted on this page with a new date.