How Relka uses your data

What Relka reads and why

With your permission, Relka uses read-only Gmail access to retrieve recruiting-related message headers and message content from your one connected Gmail account. It uses that evidence to identify job-search activity, build application timelines, and keep them current. Relka cannot send, change, or delete Gmail messages and does not fetch binary attachments.

What Relka stores

Relka stores collected message content and source metadata, job postings and records you add, derived interpretations and timelines, and your corrections. Data is stored in the Relka database and processed on the server. Gmail credentials stay server-side and are encrypted with a managed encryption key. This beta uses deterministic processing and does not send mailbox content to an AI model.

Retention and disconnect

Active account data is retained while you keep your Relka account. Disconnecting Gmail immediately stops future scans and asks Google to revoke Relka's grant. Your already saved applications, evidence, history, and corrections remain until you delete the account. Archiving or marking a record not relevant only changes its workspace view; it does not erase source evidence.

Account deletion

Settings provides a separate, irreversible account-deletion control. It stops scans, revokes Gmail access, and deletes your owned applications, evidence, events, interpretations, corrections, operational scan data, encrypted Gmail credentials, beta invitation, local user record, and Neon Auth sign-in identity. Each retry resumes the same deletion workflow after a recoverable provider failure. Relka uses a hashed subject only while a failed workflow can be retried. On completion that hash is cleared, leaving a non-identifying receipt with a random request ID, safe status, and timestamps. It contains no email address, mailbox content, evidence, or credential.

Managed infrastructure backups are not active product data and expire under the configured provider backup lifecycle. Before hosted invitations, the operator verifies that lifecycle and the published policy as part of the release privacy gate.