Sinkly

Privacy Policy

Effective date: October 19, 2026

Sinkly locks the apps you choose after your meals and unlocks them when you show a photo of a clean sink. We built it so that almost everything stays on your phone. There are no accounts, no ads and no tracking.

This policy explains what the Sinkly app (iOS and Android) processes, why, and the choices you have. "We", "us" and "our" mean Osama Fahd, the developer of Sinkly, who is responsible for this processing. Contact: osamadeveloper0@gmail.com.

In short: your name, meal plan, chosen apps and cleaning history live only on your phone. A photo of your sink is sent for a few seconds to be checked and is not stored by us. Purchases are handled by Apple or Google. We never sell your data.

1. Information that stays on your phone

The following is stored only on your device and is never sent to us:

Deleting the app deletes this information.

App blocking permissions

2. The photo of your sink

To unlock your apps, you take a photo of your sink with the camera. The photo is resized and sent over an encrypted connection to our server (a function hosted by Supabase), which asks Google's Gemini AI model one question: is this a clean kitchen sink? The answer (clean / not clean and a short reason) comes back to the app.

To keep the service fair and affordable, each phone can run 15 photo checks per day. For this, the first time you use the photo check (or send feedback), the app creates a random, anonymous identifier with Supabase (no name, email or phone number). We store the time of each check against that identifier and delete these records automatically after a few days.

3. Feedback you send

If you use "Help build Sinkly", we receive the text you write, the category you picked, the app language, the app version and the platform (iOS or Android), linked to the anonymous identifier above. Please do not include personal information in your message. We use feedback only to improve Sinkly and keep it while it is useful for planning features; you can ask us to delete it.

4. Purchases and subscriptions

Subscriptions are sold and billed by Apple (App Store) or Google (Google Play). We never receive your card or payment details. We use RevenueCat to confirm whether your subscription is active. RevenueCat receives the purchase information from the store (product, dates, renewal status), an anonymous app user ID, and basic device data such as the store country and OS version. Our server also asks RevenueCat whether that anonymous ID has an active subscription before running a photo check.

5. Crash reports

If the app crashes, it sends a crash report to Firebase Crashlytics (Google): the technical error, device model, OS version, app version and a random installation identifier. Crash reports never contain your photos, name or plan, and we use them only to fix bugs.

6. Notifications

Reminders (for example "Apps lock at 2:00 PM" or "Your free trial ends tomorrow") are scheduled on your phone. No push token or personal data is sent to us for them. You can turn reminders off in Sinkly's settings or in your phone's settings.

7. What we do not do

8. Service providers

ProviderWhat forData
SupabaseAnonymous identifier, daily limits, feedbackRandom ID, check times, feedback text
Google (Gemini API)Checking the sink photoThe photo, during the check
RevenueCatSubscription statusPurchase info, anonymous user ID, device basics
Apple / GooglePayments, app distributionHandled under their own privacy policies
Firebase Crashlytics (Google)Crash reportsCrash trace, device and app version

These providers may process data in the United States, the European Union or other countries, with safeguards required by law.

9. Legal bases (EEA and UK)

We process the photo, the anonymous identifier and subscription status to provide the service you request (performance of a contract). We process crash reports and feedback based on our legitimate interest in keeping Sinkly reliable and improving it.

10. Your choices and rights

11. Children

Sinkly is not directed to children under 13 (under 16 in the European Economic Area), and we do not knowingly collect their data.

12. Security

Data in transit is encrypted (HTTPS). Server access is restricted, and the AI provider key is kept only on the server, never in the app.

13. Changes

If we change this policy, we will update the date above and, for significant changes, tell you in the app.

14. Contact

Osama Fahd · osamadeveloper0@gmail.com