SumiliUpdated 21 October 2026. This policy covers the native Sumili app for iOS and Android. Not all app storage consists of browser cookies: this notice also explains preferences, caches and technical SDK identifiers.
1. Who manages the data
OpenTrentuno di Corsini Niccolò · VAT IT02078540479. For information, rights requests and support: support@sumili.it. The privacy notice explains the purposes and legal bases for personal-data processing.
2. Preferences and device registration
Sumili uses AsyncStorage, the app’s local storage, for operating preferences, including language, and the technical token of the device registered for notifications. This token manages registration and removal of the device from the push service; it is not an advertising identifier. Preferences remain until changed or local data is removed; the registered token is removed locally by the sign-out/disable flow and may be replaced when the push service refreshes it. To display the last session immediately, a local account-scoped cache also retains the signed-in profile’s name and email and minimal collaborator references, such as names and identifiers, already obtained for shared sheets. This cache contains no passwords or sign-in credentials, does not download a global directory and is not used for advertising. It is refreshed during synchronisation and removed by the app on sign-out, an account-deletion request or an account change; it can also be cleared by removing local app data. Sheets and expenses instead use the native Firestore cache described below.
3. Sign-in, synchronisation and notifications
Firebase Authentication stores the session and technical credentials needed to keep you signed in; Google Sign-In and, on iOS only, Sign in with Apple may use their own storage and sessions. Duration depends on credential renewal, sign-out and provider rules. Firestore may retain a local cache of synchronised data, including expenses, for operation and synchronisation. Firebase Cloud Messaging and, on iOS, APNs use installation identifiers and tokens to deliver notifications. Storage is managed by the app, SDKs and operating system; some identifiers may be created when the relevant SDK initialises, even before visible notifications are enabled.
4. No advertising or behavioural analytics
The described version does not integrate advertising SDKs, Google Analytics, marketing pixels or commercial profiling. We do not use technical storage to follow browsing across apps and websites. Necessary provider service and security data are not thereby absent: they are described in the privacy notice.
5. Your controls
You can change the language in the app, sign out and revoke camera and notification permissions in iOS or Android settings. Use available operating-system controls to remove local data; reinstalling or signing out does not guarantee removal of every system- or provider-held credential. Disabling notifications does not delete your account, and clearing local data does not delete server data. For server deletion, use Settings → Delete user or contact the controller. Refusing optional permissions does not prevent manual expense management.
6. Informational pages in the WebView
The slim versions of these notices load no analytics, advertising, sign-in forms or website-banner storage. Opening a policy does not authorise tracking. External websites, such as providers’ pages, have their own notices and settings.
7. Changes
If we introduce features requiring non-technical tools, we will update this notice and, where required, collect a prior, revocable choice before activating them. Website consent does not automatically extend to the app.