Skip to content

Privacy Policy

This policy explains how Shiny handles personal data across the mobile app, website, and API for account access, shared-home collaboration, notifications, diagnostics, analytics, support, and subscription management.

Last updated: 13 November 2026

Controller, scope, and audience

The controller of personal data processed for Shiny is PROAF SOCIETA' A RESPONSABILITA' LIMITATA SEMPLIFICATA, referred to as PROAF. Registered office: Via Genova 7, 52100 Arezzo, Italy. Italian tax code and VAT number: 02541950511. Companies Register: Arezzo-Siena, REA AR-228035. Privacy contact: goshinyapp@gmail.com. Certified email, PEC: proaf@pec.it.

Shiny is distributed through personal Apple and Google developer accounts. The publisher or seller shown by a store is distinct from the controller identified in this policy. Apple and Google process their own store-account and payment data under their respective privacy policies.

This policy applies to the Shiny mobile app, the related website, and the API that powers account access, shared-home features, notifications, and support workflows.

Shiny is intended for a general audience aged 16 and older and is not directed to children under 16.

Data Shiny collects

Shiny collects the data needed to create and run your account, synchronize your homes and chores, protect the service, and support the mobile experience.

  • Account and profile data such as your name, email address, locale, avatar URL, account identifiers, linked sign-in providers, and onboarding or subscription state.
  • Shared-home content such as homes, rooms, devices, chores, assignments, schedules, completions, activity history, invitation codes, and other content you create or join inside the service.
  • Authentication and security records such as session tokens, session timestamps, email sign-in and verification records, IP addresses, user agents, and abuse-prevention metadata handled by the backend.
  • Apple or Google sign-in provides identifiers, email and available profile fields. Shiny processes authorization codes and temporary sign-in security data. For Apple, it stores an encrypted refresh token, including a temporary copy during registration, to support revocation. Account deletion removes the stored token and attempts revocation with Apple; this can fail. You can also revoke Shiny access in your Apple account settings, including for older accounts without a stored token.
  • Notification data include category preferences, delivery time and time zone, installation ID, Expo push token, permission status, platform and device name. Shiny stores notification titles and bodies, delivery attempts and receipts. Messages may contain chore, home or member names and may appear on your lock screen according to device settings.
  • Subscription data include a separate billing identifier linked to your Shiny account, RevenueCat customer identifiers, store, product and transaction identifiers, purchase tokens, access and renewal status, and billing-event payloads received from RevenueCat, Apple and Google. Shiny does not receive full payment card details from the stores.
  • When you submit a bug report, Linear receives your report, selected image or video attachments, name, email, internal user and session identifiers, and technical context such as app/build version, locale, routes, device brand/model and operating system. Attachments are uploaded to Linear file storage. Do not include unnecessary personal data or secrets.
  • Diagnostics and product-analytics data such as app version, screen names, event metadata, route context, device metadata, and crash information generated while the app is being used.

How Shiny uses personal data and legal bases

Shiny uses personal data to provide the service, secure accounts, operate shared homes, support notifications, verify subscriptions, review support issues, understand product usage, and comply with legal obligations.

For processing subject to the GDPR, the bases below depend on the purpose. A device permission is a technical authorization and is not, by itself, a separate GDPR legal basis.

Account and authentication data are needed to provide an account; without them, Shiny cannot provide account-based features. Avatars, report attachments and notification permissions are optional. Shiny does not use solely automated decision-making with legal or similarly significant effects on you.

  • Contract, Article 6(1)(b): accounts, authentication including your chosen Apple or Google sign-in, shared-home synchronization, requested notifications and avatar uploads, requested support and subscription access.
  • Legitimate interests, Article 6(1)(f): security, abuse prevention, fraud checks and reliability diagnostics. You may object to these purposes.
  • Optional permissions: Shiny requests the operating-system permissions needed for notifications and selected media. Where processing requires consent under applicable law, consent must be freely given and can be withdrawn without affecting earlier lawful processing.
  • Consent, Article 6(1)(a): optional ad measurement with Meta, which you can withdraw at any time: on iOS in the iOS Settings, on Android in Settings > Legal.
  • Legal obligations, Article 6(1)(c): respond to lawful requests and keep records required by applicable law.

Shared homes and account visibility

Members of a shared home can see your name, avatar and email, assignments, completions and shared content. Leaving, removal or account deletion removes your profile attribution from that home’s history; facts and dates remain for remaining members while the home exists. This does not erase personal details typed into names, notes or other shared free text. Rejoining does not restore old attribution.

If you invite other people into a home, you are responsible for deciding what information you share there.

Mobile permissions and data stored on your device

The app uses secure device storage for session and refresh tokens, expiry timestamps and a cached account snapshot. Other local app storage holds preferences, selected-home and invitation state, drafts, pending verification state and an offline completion queue with account, home, chore and occurrence identifiers and timestamps. That queue uses ordinary app storage, not the secure token store.

  • Shiny opens the system media picker for an avatar or a report attachment and requests media-library permission where required by the platform. It uses only the media you select for these flows.
  • Signing out clears stored session credentials and the cached profile, but some preferences and pending completions can remain. Account deletion does not currently wipe every device’s offline queue. Clear app data on Android or uninstall the app to remove remaining ordinary local app data; credentials in iOS Keychain may survive uninstall, so sign out first when possible.
  • When you accept the Terms and Privacy Policy at sign-up, iOS asks whether Shiny may track you (App Tracking Transparency). If iOS does not allow tracking, the Meta SDK sends no events from iOS; Meta can then only count installs in aggregate through Apple's SKAdNetwork.

Website and account utilities

The website and account-link utilities use necessary cookies or equivalent storage for language, authentication, security and invitations where applicable. The public marketing site does not embed third-party advertising trackers; store-link clicks are counted through aggregate server events. Infrastructure may process IP addresses and request metadata to serve and secure requests.

Notifications, analytics, and diagnostics

If you allow notifications, Shiny registers your device with the backend and uses Expo's push service together with Apple Push Notification service or Firebase Cloud Messaging to deliver reminders, assignments, and recap updates.

Shiny measures usage through aggregate counters without visitor identifiers to improve screens, onboarding, subscriptions and task creation. The app sends only predefined action categories and counts to Shiny’s backend, without account, device or session identifiers, names, emails, home content or free text. The backend forwards these counters to PostHog in the EU without the visitor’s IP address or request headers. No analytics cookies, persistent analytics identifiers, fingerprinting, individual profiles, session replay or cross-session histories are used. Reports show counts and percentages of visits and attempts, not identifiable people or unique users. Counters are retained for up to one year under the current free plan. Ordinary technical security logs and Sentry diagnostics remain separate. For the first-party receipt and protection of these counters, Shiny relies on its legitimate interests in statistical service improvement and abuse prevention, Article 6(1)(f) GDPR. The incoming IP is used transiently to derive a hashed abuse-limit bucket, is not an analytics dimension and is not forwarded to PostHog. You may object by contacting us.

Sentry provides crash reporting and diagnostics for the mobile app and backend, including server and edge execution. Default personal-data collection is disabled. Account context is limited to an internal user ID, with no profile name or email and the IP address field explicitly set to null in diagnostic user context. Reports can include technical traces, breadcrumbs, routes, locale, app version and device information; they remain potentially linkable to an account.

Ad measurement with Meta is optional. On iOS it is on only if you allow tracking when iOS asks, after you accept the Terms and Privacy Policy at sign-up. On Android it is off by default and you can turn it on, on the last sign-up page or in Settings > Legal. When it is on, the Meta SDK sends Meta Platforms Ireland the app install and launch events and the completed sign-up with its sign-in method, together with technical device data and the advertising identifier (IDFA on iOS, advertising ID on Android). Shiny uses them only to see which of its own ads lead to installs and sign-ups; it does not send your name, email, purchases or home content. Meta acts as an independent controller under its own privacy policy, https://www.facebook.com/privacy/policy. Without your consent the SDK sends no events and no advertising identifier, but it can still download its own configuration from Meta. You can withdraw at any time, on iOS in Settings > Privacy & Security > Tracking and on Android in Settings > Legal: new events stop, but what Meta has already received is not deleted.

Processors, partners, and recipients

Shiny does not sell personal data. Personal data is shared only when needed to operate the service, process your requests, protect the platform, or comply with law.

Authorized personnel and service providers may access data only as needed for operation, security and support. Apple and Google may act as independent controllers for their own authentication, store and payment services.

  • Hosting, database, and infrastructure providers chosen by Shiny to run the website, API, and related systems.
  • Apple and Google for sign-in, app-store billing, and core mobile platform services.
  • RevenueCat for mobile subscription status, customer management, and webhook delivery.
  • Expo and the relevant mobile push providers for notification token handling and push delivery.
  • PostHog (EU): Usage statistics.
  • Meta Platforms Ireland, as an independent controller, for the optional measurement of Shiny's ads.
  • Sentry for mobile and backend crash reporting, error monitoring and diagnostics.
  • Backblaze B2-compatible object storage used for avatar uploads and delivery.
  • Linear for mobile bug-report intake and any attachments you choose to upload with a report.
  • Resend for transactional email delivery, including sign-in codes, account verification, and email changes.
  • Authorities, courts, advisors, or counterparties where disclosure is required by law or reasonably necessary to establish, exercise, or defend legal claims.

International transfers and retention

Providers may process data outside the EEA. Transfers of personal data subject to the GDPR require an applicable adequacy decision or appropriate safeguards, such as standard contractual clauses and any necessary supplementary measures. Contact PROAF for information about destinations and the safeguards applicable to your data, or to request a copy.

Shiny keeps personal data for as long as needed to provide the service, maintain shared-home records, verify subscriptions, investigate incidents, resolve disputes, and meet legal obligations.

  • Account, identity, session and membership records are removed by account deletion. Removal of a managed avatar is attempted. Homes with no remaining members are deleted; surviving shared homes keep their content and history for the lifetime of the home, with profile attribution removed as described above. Ownership passes to a remaining member where needed.
  • Technical sign-in and notification records are deleted on a fixed schedule: sessions, with their IP address and device user agent, 30 days after they expire or are revoked, or 60 days after their last use if they are no longer used; used, revoked or expired renewal tokens after 7 days; sign-in attempt counters when they expire; Google and Apple sign-in flows and emailed sign-in and email-change codes one day after they expire; sent push notifications, with their title, text and delivery records, 90 days after sending. Push registrations can be deactivated or deleted on sign-out, permission changes or account deletion; deactivation alone is not erasure.
  • Billing-event payloads, other security records, diagnostics, analytics, support tickets and attachments, and backups can remain after account deletion. The app does not automatically erase all copies held by external providers. No uniform fixed retention period is currently specified for these categories or backups; contact PROAF for the applicable criteria and an individual review or erasure request.

Your rights and choices

For GDPR requests, contact goshinyapp@gmail.com or proaf@pec.it to access, correct, erase, restrict or receive portable data where applicable, object to legitimate-interest processing, or withdraw consent where used. We may verify your identity and normally respond within one month, with any lawful extension explained to you. Device permissions can be revoked in system settings.

  • Access and correction: update profile details, avatar, locale, and connected sign-in methods from the app where those controls are available.
  • Delete your account in the app or request deletion at goshinyapp@gmail.com. The public instructions are at https://goshiny.app/en/delete-account. External-provider records and local data require the separate handling described above. Deleting an account does not cancel a store subscription.
  • Notifications: change notification preferences in the app and revoke push permission in your device settings at any time.
  • Ad measurement: on iOS, allow or stop tracking in the iOS Settings; on Android, turn Meta ad measurement on or off in Settings > Legal.
  • Subscriptions: manage cancellation, renewal, or refunds through Apple or Google according to the store you used for the purchase.
  • Support data: avoid uploading sensitive personal data in bug reports unless it is necessary to explain the issue you want reviewed.

Controller details, complaints, updates, and contact

The controller of personal data processed for Shiny is PROAF SOCIETA' A RESPONSABILITA' LIMITATA SEMPLIFICATA, referred to as PROAF. Registered office: Via Genova 7, 52100 Arezzo, Italy. Italian tax code and VAT number: 02541950511. Companies Register: Arezzo-Siena, REA AR-228035. Privacy contact: goshinyapp@gmail.com. Certified email, PEC: proaf@pec.it.

You can complain directly to the Italian Garante per la protezione dei dati personali, https://www.garanteprivacy.it, or the competent supervisory authority in your country. Contacting PROAF first is optional.

Shiny may update this policy when features, legal requirements, or processors change. The latest version date is shown at the top of the document, and material changes may also be highlighted inside the product or on the website.