Skip to content
Previously. Back to Previously
Privacy PolicyTerms of UseSupportAccount Deletion

PREVIOUSLY. / THE DETAILS

Privacy Policy.

How Previously. handles your account, watching activity and information you choose to share.

Working draft · not yet effective

On this page
01Who this policy covers02Information used to run Previously.03Why this information is used04Services that receive information05Retention and deletion06Your controls and requests07Security, location and audience08Changes and contact

ON THIS PAGE

01Who this policy covers02Information used to run Previously.03Why this information is used04Services that receive information05Retention and deletion06Your controls and requests07Security, location and audience08Changes and contact

A real person.
An open inbox.

Previously. is made by
Shantanu Sinha.

shantanusinha95@gmail.com
GitHubLinkedIn
About this draft

Your contact route is ready. Retention practices and complete account deletion still need to be resolved before these pages can support a store submission.

01

Who this policy covers

This policy covers the Previously. iPhone app, its supporting service, and this website. Previously. is operated by Shantanu Sinha. For privacy questions, contact shantanusinha95@gmail.com.

02

Information used to run Previously.

Previously. uses information you provide and information generated when you use the service. The exact information available depends on the features and sign-in methods you use.

  • Account information: your authentication identifier, an internal account identifier, email address when supplied, and account creation and last-opened timestamps. Clerk handles sign-in and authentication.
  • Watching activity: saved shows, library statuses, watched episode counts, and the dates those records are changed.
  • Preferences: selected country, language and streaming-provider preferences when those settings are used. A selected country is a preference; it is not a GPS reading.
  • Updates: notification content and its creation and read status.
  • On-device information: recent searches, cached show details and images, rewatch records, settings, and any exports you create.
  • Service requests: searches, requested pages and technical connection information processed by the app service, authentication provider and hosting infrastructure.
03

Why this information is used

Information is used to sign you in, maintain your library and progress, show relevant schedules and updates, honor your settings, respond to support requests, and operate and protect the service.

  • Notifications require your permission and are scheduled on the device by the current iPhone app.
  • The website’s interactive example keeps sample progress in the page session. It does not create an app account or update your library.
  • The reviewed app and website do not contain an advertising SDK or an app-owned analytics integration. Provider and infrastructure data practices must still be verified before making broader claims about tracking or collection.
04

Services that receive information

Previously. uses external services for specific functions. Their actual configuration and applicable data-processing terms must be verified before publication.

  • Clerk receives information needed for authentication and session management.
  • AniList and TMDB may receive search terms when the backend searches their catalogs. These catalog requests do not deliberately include your Previously. account identifier or watched-episode history.
  • If AI search correction is enabled, Cerebras receives the search text to suggest a corrected title. Avoid entering private information into a show search.
  • Catalog enrichment can use Cerebras, OpenRouter and its selected model providers, and Anthropic-powered research. The reviewed enrichment inputs contain show metadata and public announcements, rather than account identifiers or personal episode progress.
  • Your device loads artwork from the image hosts referenced by the catalog. Those hosts receive ordinary image requests, which can expose network information such as an IP address.
  • Opening a trailer or another external link involves the destination service and its own privacy practices.
  • Network and hosting providers process requests to deliver and protect the app service and this website. Confirm the deployed providers, logging settings and processing locations before publication.
05

Retention and deletion

The app database currently stores account information and watching records until they are changed or deleted. Removing an individual show from the library does not necessarily erase its episode progress.

The current in-app deletion flow removes the primary Previously. database records and signs you out. It does not yet remove the Clerk identity, and some on-device history and cache files remain. Complete account deletion must be implemented and verified before this policy is published as a store-ready policy.

The operator must define the retention and deletion treatment of support correspondence, service logs, backups and processor-held data. This draft intentionally makes no unverified retention deadline or immediate-backup-erasure promise.

06

Your controls and requests

You can change your library and supported preferences, control notifications in iPhone settings, and export library information from Profile. A library export is not an export of every category of personal information.

The Account Deletion page describes the intended request channels and the current publication blockers. For privacy requests, contact Shantanu Sinha at shantanusinha95@gmail.com.

Depending on where you live, applicable law may give you rights to access, correct, erase or restrict use of personal information, object to processing, withdraw consent, or complain to a relevant authority. Identity verification may be needed to protect your account when handling a request.

07

Security, location and audience

The configured public app API uses HTTPS. Access to account endpoints requires authentication. No method of transmission or storage can be guaranteed to eliminate every risk.

The operator must confirm processing locations, applicable legal bases, the intended audience and any child-privacy requirements for the regions where the app will be offered. No age threshold or international-transfer guarantee has been assumed in this draft.

08

Changes and contact

When the published policy changes, its effective date will be updated and any notice required by applicable law will be provided. This draft has no effective date. The operator is Shantanu Sinha. Privacy questions can be sent to shantanusinha95@gmail.com.

PREVIOUSLY. / PRIVACY POLICYBack to top ↑
Previously.
PrivacyTermsAccount deletionSupport
© 2026 · Shantanu Sinha
GitHubLinkedIn
Artwork © respective owners.