Timeback SoluPRIVACY + AI DATA PRACTICES

Your collection should remain yours.

MVP informational notice · Updated August 13, 2026

What we store

When you sign in, the hosting platform provides an account identifier, email address, and sometimes a display name. Timeback Solu stores the collections, card details, manually entered purchase and estimated-value records, import history, and notes that you choose to add. Uploaded front, back, and cover images are stored in private object storage with owner-scoped metadata.

How records are used

Private vault records are used to provide catalog, search, dashboard, report, import, export, and image features. Records are scoped to the signed-in owner. The separate public demo uses fictional, read-only data and cannot read private vaults. We do not claim that collection records are professional appraisals.

AI is optional

Card-image assistance runs only when you explicitly invoke it and a provider is configured. Only the selected owner-scoped card images are sent for that request. Collection summaries send de-identified aggregates rather than card names, record IDs, images, notes, email addresses, or raw account identifiers. AI output can be wrong and never silently saves over verified information.

Demo requests and operations

A demo request stores the name, email, collection-size range, category, and optional message that you submit so the team can follow up. Operational systems may retain limited timestamps, structured error events, usage counts, and one-way hashed abuse-prevention identifiers. Secrets, raw authentication tokens, and image payloads should not be logged.

Storage, retention, and deletion

Managed database and object-storage providers process data to operate the service. Automated backups and retention must be configured with those providers. Users can export card data as CSV. Self-service account deletion is not yet available; a verified support process should remove or anonymize collections, cards, images, imports, AI records, and account-linked data before broader scale.

Your choices

This is plain-English MVP product information, not a final legal policy. It requires professional legal review, provider-specific disclosures, a support contact, and final retention/deletion terms before broader commercial rollout.