← Back to Tarc
Privacy & Security

Security

Last updated 2026-07-09 1 min read

Tarc's security model leans on well-established providers for the hardest parts (authentication, data storage) rather than building custom, harder-to-audit systems.

No passwords stored, ever

Tarc never asks you to create a password. Google sign-in is handled entirely by Google; email sign-in uses one-time codes and magic links verified through Tarc's backend (Supabase) — there's no password field or password database to compromise.

Encrypted connections

All data sent between your device and Tarc's servers is encrypted in transit (HTTPS/TLS) — nothing is transmitted over an unencrypted connection.

Backend and data storage

Account data, progress, and uploaded avatars are stored via Supabase, which handles authentication and database access under Tarc's direction — Supabase doesn't use your data for its own independent purposes.

Account deletion is immediate and complete

See Account Deletion — deletion runs as a single, transactional server-side operation, so it can't partially complete and leave orphaned data behind.

What you control

The public profile toggle controls what other users can see about you; sign-out on any device returns it to Guest Mode without affecting your account's stored data.

Frequently asked questions

Does Tarc store my password?

No — Tarc has no password field at all. Google sign-in is handled by Google directly, and email sign-in uses one-time codes/magic links instead of a password.

Is my data encrypted when it's sent to Tarc?

Yes — all data between your device and Tarc's servers is encrypted in transit via HTTPS/TLS.

What happens if account deletion fails partway through?

It can't partially complete — deletion runs as a single transactional database operation, so either everything is deleted or (on error) nothing is, with no orphaned data left behind.