SolidSoft

Do Not Sell or Share My Personal Information

Settly does not sell personal information for money. When applicable Google privacy choices permit personalized ads, identifiers, app or ad interactions, SDK diagnostics, and IP-derived approximate location may be disclosed to Google or configured advertising partners. That disclosure may be considered sharing for cross-context behavioral advertising under the California Consumer Privacy Act or targeted advertising under another U.S. state law.

Settly never shares settlement titles, participant names, item descriptions, or amounts for advertising.

Opt out through the app

When Ad privacy choices appears in Settly Settings, a user may open it and submit an opt-out through Google's U.S. state regulations message without creating a Settly account. Applicable Google consent, opt-out, restricted-data-processing, or GPC signals control ad treatment.

Submit a request by email

Users or their authorized agents may also contact corp@solidsoft.team · +82-10-2615-3559 with the subject Do Not Sell or Share. Include only the information needed to identify the affected record or device. Settly does not require an account or identity verification for an advertising opt-out.

Settly has no user-facing signup. It does receive synced settlement content, but email addresses are not the identifiers used by Firebase authentication, Analytics or RevenueCat. Email alone may therefore be insufficient to locate the relevant installation or provider-held record. We explain the minimum information needed, use available provider tools and respond under applicable law. Settlement content is not provided for advertising.

Global Privacy Control

The Settly policy website does not load advertising, analytics, or tracking scripts. It therefore does not sell or share browser data regardless of whether a Global Privacy Control (GPC) signal is present.

This website cannot associate a browser signal with every Android installation. Use Ad privacy choices in the app where available, or contact us about the affected device. A website GPC signal does not automatically disable Android Firebase/Meta analytics or delete subscription records.

Effect of an opt-out

An opt-out stops future sale, sharing, or targeted-advertising processing within the scope of the selected control. Non-personalized ads may still process data for delivery, frequency capping, measurement, and fraud prevention. Information already transferred remains subject to the recipient's retention rules. The choice does not remove access to otherwise available settlement features or a verified Pro entitlement.

App usage and ad performance analytics

The October 17, 2026 revision describes the behavior of supporting app versions. Older versions may retain their previous privacy screens, analytics choices or settings until updated; this page does not update an installed app.

Supporting release builds automatically collect Google/Firebase and Meta analytics from app startup when their SDKs are ready. The Privacy Policy discloses the processing; it and the Terms of Use are accessible from Settings. There is no app-specific analytics consent screen, settings menu or on/off switch. Earlier app analytics consent choices and stop settings no longer control collection.

Google UMP handles advertising privacy choices and required regional advertising messages. Those choices do not disable Firebase Analytics or Meta measurement. Firebase Analytics advertising-ID collection, ad storage, ad user data and ad personalization remain disabled.

Contact corp@solidsoft.team · +82-10-2615-3559 for an applicable access, deletion, restriction, sale/sharing opt-out or other request concerning analytics records. We explain the information needed to identify the relevant records and process requests under applicable law. A request is not confirmation of immediate deletion of all data or cancellation of SDK requests already in progress.

Meta Platforms, Inc. in the United States can receive SDK installation and repeated app-activation/foreground signals, the three custom events settly_settlement_created, settly_expense_added and settly_result_viewed without app-supplied custom parameters, and SDK/network metadata including IP, app/device information and available device/advertising identifiers subject to device controls. The app does not add settlement content, names, participants, amounts, notes, photos, support/Firebase/purchase IDs or links to those custom events and does not implement Meta purchase/subscription-revenue or AdMob ad-revenue reporting. Meta retention is separate from the Firebase two-month setting.

Meta SDK data can persist or queue for later transmission. The SDK has no public shutdown or queue-deletion API that guarantees erasure of these records or cancellation of requests already in flight. Such records or requests may continue to be processed, and later SDK initialization may process persisted data. The app requests that automatic event logging be off, but Meta server settings can affect SDK behavior, so every automatic event cannot be guaranteed to be disabled.

Firebase data and other processing

Firebase Analytics uses the installation support ID to link analytics with support, server logs, RevenueCat attributes and Crashlytics, and processes installation/SDK metadata and automatic events. These records are not anonymous just because they lack a name. Deleting settlement data does not itself delete uploaded analytics data. Firebase's two-month detail-retention setting does not apply to Meta. Operational diagnostics, subscription verification and separate shared-viewer web choices are distinct processes.

For all other rights and details, read the Settly Privacy Policy.