Private betaRenewal reminders, billing, and review-first tracking are live.
Sign in

Welcome back

Track and manage your subscriptions.

Google sign-in creates your Rellio account and returns you here. Read our privacy policy and terms.

or
Don't have an account?
Create account

Create account

Know exactly what you're paying for, every month.

Google sign-in creates your account and brings you back to Rellio. Read our privacy policy and terms.

or
Auto-detects subscriptions from your Gmail inbox
Tracks renewals, costs, and cancellations automatically
Read-only access - Rellio never sends or deletes email
Already have an account?

Trust & security

Rellio is built so security, privacy, and reliability stay visible.

Trust is not a side page for us. It is the operating model: read-only Gmail access, tenant-isolated records, idempotent ingestion, and explainable states that do not hide uncertainty.
Start freeRead the FAQ

Built for trust

Financial software earns trust by keeping provenance close to the decision.

Rellio favors a smaller, defensible list over a larger, noisier one. Every design decision flows from that principle.

Security

Read-only access, always.

Rellio uses Google OAuth with read-only Gmail scope. It cannot send, edit, or delete emails. Access tokens are never stored in plaintext and are revocable from your Google account at any time.

No write permissions · OAuth 2.0 · Revocable at any time

Privacy

Your data is never sold or shared.

Email content is processed to extract billing signals and immediately discarded. Rellio stores structured subscription records, not raw email bodies. Your inbox data belongs to you.

No email storage · No data resale · Tenant-isolated records

Reliability

Idempotent ingestion, no duplicate records.

Every signal is processed through an idempotency check before ingestion. Resyncing an inbox will not create duplicate subscriptions. The pipeline is deterministic — the same input always produces the same result.

Idempotency keys · Deterministic pipeline · No silent state drift

Transparency

Every state is explainable.

Rellio never hides why a subscription is uncertain or why a record is in review. Confidence scores, evidence signals, and data provenance are visible on every record — not locked behind an audit log.

Visible provenance · Confidence on every record · No black boxes

Operational safeguards

The product is designed to fail in understandable ways.

When subscription data is uncertain, Rellio should make that uncertainty obvious instead of quietly overfitting a guess.

Access

Read-only Gmail access keeps the attack surface narrow.

The service can inspect billing messages, but it cannot write to the mailbox or take destructive actions on your behalf.

Isolation

Records are tenant-scoped and only expose what the user needs.

Subscription state is stored as structured data so the app can explain itself without surfacing unnecessary raw email history.

Reliability

Repeated syncs should not change the story.

Idempotent processing keeps records stable across rescans and makes review output easier to trust.

Need the short version?

If you cannot explain the state, Rellio should not pretend it is certain.

That is why the review queue exists, why AI enrichment is asynchronous, and why user overrides always win when the system and the person disagree.
Start freeRead the FAQ
Trust & Security | Rellio