Privacy Policy

1. Who we are

Piccola is developed and operated by I.E. BLANKET BYTE (individual entrepreneur), registration ID 305834292, University Street N.17a, Floor 10, Vake district, Tbilisi, Georgia. We are the data controller for the personal data described in this policy.

You can reach us at contact@blanketbyte.com for anything privacy-related. We answer in English or Italian.

2. The short version

• We store what you type into Piccola so we can show it back to you, on every device you sign in on.
• No ads, no advertising networks, no analytics or telemetry SDKs, no crash-reporting services, no tracking of any kind.
• The app sets no cookies. It keeps a handful of settings and your sign-in session in your browser or phone storage (see section 6).
• We never sell your data and never share it for marketing.
• You can export everything and delete your account yourself, from Settings, at any time.

3. What we store

Everything below is stored only because you chose to enter it or enable it.

• Account: your email address and a password. The password is stored only as a secure hash by our authentication provider (Supabase) — we never see it. The only emails we send are the ones needed to run your account: signup confirmation, password reset, and a confirmation when you change your email address.
• Profile and preferences: a display name (by default, the part of your email before the "@"), an optional avatar picture, your locale, time zone, currency, first day of the week, date format, interface language, theme, "reduce motion" preference, and the date you completed onboarding.
• Routine: your routines (title, description, icon, color, time), their repeat rules, the individual occurrences generated from them, and which ones you marked as done or skipped.
• Groceries: your lists and their items (name, category, quantity, unit, note, and whether you bought it).
• Budget: your spending categories, monthly limits, expenses (amount, currency, date, merchant, note), and any receipt files you attach (PNG, JPEG, WebP or PDF, up to 25 MiB each).
• Reminders: your reminder categories (Piccola starts you with "Medicine" and "Nuts", and you can add your own), the items in them, the log entries you record (time, optional amount and unit, note), and the reminders you schedule (label, time, repeat rule, snooze). See section 4 about health-related entries.
• Devices and notifications: for each device you enable notifications on — its platform, a push token (an Expo push token on iOS/Android; a push subscription endpoint and keys on the web), a device name (on the web, the first part of your browser's user agent string; on mobile, your device's name), your per-category notification toggles, and when it was last seen. We also keep your in-app notification inbox and a log of which notifications were sent to which device.
• Technical records: short-lived request identifiers that stop the same action from being applied twice if your connection drops; these are deleted after about 48 hours. Hosting providers may also keep brief technical logs (such as IP address and request time) to keep the service running securely.

4. A note on health-related entries

Piccola is not a medical device and the Reminders module is not a medical record. By design it stores factual log entries only — there are no dosage, prescription or exposure-plan fields, and nothing in the app instructs you to take, eat or avoid anything. As the app itself puts it: "No records for this day — that's not a health claim, just no log."

If you choose to log medicines, allergens such as nuts, or similar items, you are giving us information that relates to your health. We treat those entries like everything else you type into Piccola: we store them solely so we can show them back to you, we never analyze them, we never share them, and you can delete them individually or by deleting your account. By using Reminders for this purpose you explicitly agree to us storing those entries for you.

5. Why we process your data

We rely on the following grounds:

• To provide the service you signed up for (performance of our contract with you): storing your data, syncing it between your devices, and keeping your account working.
• Your consent: for push notifications (opt-in per device, revocable at any time in Settings) and for any health-related entries you decide to log (section 4).
• Our legitimate interest in keeping Piccola secure and reliable: protecting accounts, preventing abuse, and fixing problems.
• Legal obligations, where they apply to us.

6. Cookies and on-device storage

Piccola sets no cookies. To work as an app, it keeps a few things in your browser or on your phone:

• On the web: your theme (piccola.theme), reduce-motion preference (piccola.reducedMotion), interface language (piccola.language), a queue of changes you made while offline (piccola.offlineQueue.v1.<your user id>), and your sign-in session with its refresh token (sb-<project>-auth-token), plus a temporary verifier while you sign in.
• The web app's service worker caches only the app shell (the code and images needed to open the app). It never caches your data, API responses or files, and it is what displays push notifications when you enable them.
• On iOS and Android: your sign-in session is stored in the operating system's secure storage (Keychain on iOS, encrypted storage on Android). The app also keeps a device identifier and the offline change queue in its own app storage.

Clearing your browser data or uninstalling the app removes these; it does not delete your account or the data stored on our servers (see section 11 for that).

7. Where your data lives and who helps us run Piccola

We run Piccola on a small number of infrastructure providers, each of which processes data only on our instructions and only as needed to provide their service to us:

• Supabase — hosts our database, authentication and file storage.
• A virtual private server hosting our API and background worker.
• Expo Push Service, together with Apple Push Notification service and Google Firebase Cloud Messaging — to deliver notifications to the iOS and Android apps.
• Your browser vendor's push service (Apple, Google, Mozilla or Microsoft, depending on your browser) — to deliver web push notifications.
• An email delivery provider — for the account emails listed in section 3.
• Let's Encrypt — to issue the TLS certificates that keep your connection encrypted.

Some of these providers may store or process data outside the country you live in. Where that happens, transfers rely on the provider's contractual safeguards. We do not use any provider for advertising or analytics.

8. Your files (receipts and avatars)

Receipts and avatar pictures are stored in two private storage buckets (up to 25 MiB per receipt and 5 MiB per avatar). Files are uploaded directly from your device to storage, are kept under a path that belongs only to your account, and are never reachable through a permanent public link: the app opens them through short-lived signed links (about 5 minutes for receipts and 1 hour for avatars). Deleting an expense's receipt, replacing your avatar, or deleting your account removes the files.

9. Notifications

Notifications are off until you turn them on, per device and per category. When we send one, the label you gave the routine or reminder travels through the push services listed in section 7 — we deliberately never include other content (amounts, notes, entries) in a notification. Delivery is best-effort: push services can delay or drop messages, so please don't rely on Piccola for anything time-critical. You can remove a device or switch categories off at any time in Settings.

10. How long we keep your data

We keep your data for as long as you keep it: until you delete an item, or delete your account. There is no automatic expiry, apart from the short-lived technical records mentioned in section 3 (deleted after about 48 hours). Backups of the database are kept for a limited period, after which data you deleted also disappears from backups.

11. Export and deletion

• Export: in Settings you can download a JSON export of everything in your account. The mobile apps also offer a CSV export of your expenses.
• Deletion: in Settings, "Delete account" asks you to type DELETE MY ACCOUNT and your password. It then cancels any pending notifications, deletes all your files, and deletes your account together with every routine, list, expense, entry, reminder, device and notification record. This is immediate and cannot be undone.

12. Security

We designed Piccola so that your data is isolated to your account: the database enforces per-user row-level security (covered by automated tests), every API request is verified against your session token, all traffic is encrypted with TLS (with HSTS), passwords are hashed by our authentication provider and must be at least 10 characters with upper and lower case letters and a digit, and server-side keys are never shipped to the app. We are not certified under SOC 2, HIPAA, PCI DSS or similar schemes, and no system is perfectly secure — please use a unique password and keep your devices protected.

13. Your rights

Depending on where you live (for example under the EU or UK GDPR), you have the right to access, correct, delete and export your data, to restrict or object to certain processing, to withdraw consent, and to lodge a complaint with your local data-protection authority. You can exercise most of these yourself in Settings (edit, export, delete). For anything else, email contact@blanketbyte.com and we will respond within a reasonable time, normally within 30 days.

14. Age

Piccola is for people aged 16 and over. We do not knowingly keep accounts of younger users; if you believe someone under 16 has created one, write to contact@blanketbyte.com and we will remove it.

15. Changes to this policy

When we change this policy we publish the new version here with a new date at the top. If a change materially affects how we use your data, we will let you know in the app before it takes effect.

16. Contact

I.E. BLANKET BYTE · University Street N.17a, Floor 10, Vake district, Tbilisi, Georgia · contact@blanketbyte.com · blanketbyte.com