Privacy, made clear.

Account and wallet data

When you sign in, Slices processes verified identity references, linked wallet addresses and authentication/session records to identify your account and protect private data. Privy handles the configured authentication methods. The development wallet sign-in mode is a separately labeled testing feature.

Campaign participation may involve recipient eligibility evidence, allocations and transaction receipts. Account activity and balances are shown only within the account scope authorized by the server. Email, phone and wallet identifiers supplied for eligibility or sign-in are personal data; they are not anonymous merely because a wallet address is public.

Sessions and device storage

The web application uses a server session cookie for authenticated access where applicable. Authentication providers manage their own sign-in state. Account views keep fetched private records in memory and clear them when signed out or switched.

The native application uses its authentication SDK and platform storage for sign-in. No account deletion flow should remove the only recovery path to a funded wallet without resolving continued access.

Rewards, public chains and service providers

The service reads supported token registries, prices and blockchain data and records campaign delivery evidence. Onchain addresses and transactions are public; deleting a Slices account cannot erase blockchain history.

Configured authentication, infrastructure and RPC providers process requests needed to run the application. The final processor inventory, hosting/log configuration, international transfer arrangements and retention periods must be documented before public release. Do not assume provider requests or operational logs contain no identifiers.

Purposes and limits

The implemented purposes are account access, wallet association, reward/holdings presentation, eligibility enforcement, privacy requests and service security/operations. Missing prices, unsupported actions and incomplete verification remain explicit.

Advertising, cross-service tracking and marketing enrollment are not part of this consumer milestone. Any future analytics or notification integration needs a configuration-specific privacy review and accurate store disclosures.

Deletion and your requests

You can initiate an authenticated deletion request and check its status from Account. Retained financial/security records and funded-wallet access are assessed separately. Until the production policy is configured, the application records the request and explains any blocked processing; it does not falsely confirm completion.