Privacy Policy

Who handles your data #

PT Langit Cerah Teknologi, under the brand Just Another Simple App, provides TastePatch and is responsible for the personal data in this policy.

TastePatch is local-first. Your Journal, photos, Patches and Stickers live on your device. You don’t need an account, nothing is public, and signing in alone uploads no memories.

Your photos and memories #

You pick the photos you use. TastePatch doesn’t scan your photo library. Dish and subject detection run on your device.

Your memories can include dish names, Reactions, dates, Places, Companion names, Tags, prices, notes and photos. These can involve other people, so please keep their privacy in mind.

Sign-in and account details #

Apple or Google sign-in goes through Firebase Authentication. We receive your email and account identifier, and your provider’s name may be saved as your display name, which you can change. Birth date and self-described gender are optional. Firebase App Check helps protect the service from abuse.

For signed-in accounts we also store when the account was first and last active, its platform and its app version.

Cloud backup and sync #

If you turn on a Sync Journal, its contents are stored with Cloudflare, linked to your account: dish names, notes, prices, Reactions, Tags, Companion names, Books, Places, coordinates and photos. Journals you don’t sync stay on your phone.

Sync Journals are not end-to-end encrypted. Your memories and photos are stored in a form our service can read, because it needs that to sync them. We don’t use them for advertising and we don’t sell them.

Location #

Location access is optional and only used while the app is open. It helps sort nearby Places, and you can turn it off in your phone’s settings.

When you create a Place, its coordinates may be saved from your photo or device. A photo’s location may be saved with its memory. If you turn on a Sync Journal, these coordinates are stored in the cloud with it. We remove embedded location data from the photo files themselves when we prepare them, but the coordinates we save stay in your Journal.

Purchases #

Payments go through the App Store or Google Play. They handle your payment details under their own privacy policies, and we never see your card. RevenueCat manages subscription status and receives your account identifier, when signed in, and purchase information.

Crash reports, usage data and service protection #

Firebase Crashlytics collects crash reports to help us fix failures. Reports from the app’s code include the error type, a known error code, stack details, recent actions and screens, device and app version, but not the error’s message. Crashes in the phone’s system or native components may include technical text we don’t control.

Firebase Analytics records how the app is used: actions and screens, counts, the Reaction level chosen, sign-in provider, plan, language and appearance. It may also process device and connection information, such as the device model and approximate region. Both use a random app ID rather than your account. Neither includes dish names, photos, Place names, notes or names you enter. We don’t use advertising IDs or track you for advertising.

Both are on by default unless your phone’s region is set to a country in the EEA, the UK or Switzerland, where they stay off until you turn them on. This uses your phone’s region setting, not your location. You can change this in Settings under Usage and crash data. Usage events and app errors stop right away, and native crash collection stops the next time the app opens. This doesn’t remove data already sent.

Who receives information #

We use these providers: Google Firebase (sign-in, abuse protection, crash reports), Google Analytics and BigQuery (usage data), Cloudflare (cloud storage and service), RevenueCat (subscriptions), Expo (app updates, which involve a random installation ID, platform and connection information), and Apple or Google (purchases and sign-in you choose).

There are no ads, no sale of data and no public profiles. Sharing is an image you export through your phone’s share sheet, and where you send it applies its own terms.

We may disclose data where the law requires it, or where needed to protect rights and the security of the service.

Why we use data #

We use data to provide what you ask for, such as sign-in, sync and subscriptions; to keep the service secure and fix failures; to understand how the app is used so we can improve it; and to meet legal duties.

Where the GDPR applies, we rely on contract, consent, our legitimate interests or legal obligations, depending on the purpose. Under Indonesia’s Personal Data Protection Law (UU 27/2022), we rely on the legal bases it provides, including your consent. You can withdraw consent at any time, which doesn’t affect earlier lawful processing.

How long we keep data #

Memories on your phone stay until you remove them. Cloud data stays until you delete it or your account. After a paid plan ends or is refunded, cloud copies of photos above the Free allowance may be removed after 90 days.

Deleting your account in the app erases its cloud records and photos, and you choose whether to keep your Journals on your phone. We keep a record of the deleted account’s identifier, so a late sync can’t recreate it. Purchase records stay with RevenueCat, Apple and Google after deletion, because they are needed for billing, tax and legal records.

Crash reports and usage data aren’t linked to your account and are kept for limited periods under the settings of those services. Providers may keep security and service logs for short periods.

International processing and security #

Our providers may process data in countries other than yours, including outside Indonesia and the EEA. We rely on the safeguards they offer and those the law requires.

We use sign-in, encrypted connections and abuse protection, but no method is completely secure.

Your rights #

Depending on the law where you live, you may have rights to access, correct, export or delete your data, withdraw consent, object to processing or complain to a data-protection authority.

You can export an Archive and delete your account in the app, or contact support@thetastepatch.com. We may need to confirm your identity first.

Children #

TastePatch is for people aged 13 or older, and isn’t directed at children under 13. If you believe a child has given us personal data without the consent the law requires, contact support@thetastepatch.com and we’ll review and delete it where appropriate.

This website #

This website has no account forms, advertising trackers or analytics scripts. Our hosting provider, Cloudflare, processes connection information such as IP addresses to serve pages and protect the site.

Your appearance choice is stored in your browser. The sample scrapbook stays in memory, isn’t uploaded and clears when you reload. Store links, when available, take you to Apple or Google.

Updates and contact #

If this policy changes, we’ll publish the new version here and update the date. We’ll tell you about important changes where the law requires it.

Contact: support@thetastepatch.com. Data controller: PT Langit Cerah Teknologi (Just Another Simple App).