Privacy Policy

Riqatiq collects account profile data such as email address, display name, authentication provider, and security settings needed to operate your account.

When you use the product, Riqatiq may store identity statements, selected identity status, release moments, image attachments, awareness entries, reflection notes, and related timestamps or metadata that help the platform provide continuity.

We also process operational data such as session cookies, refresh tokens, rate-limit signals, and delivery records for transactional emails and twice-weekly identity reminders.

Sensitive private entries, including release text and awareness records, are symmetrically encrypted before they are written to PostgreSQL. This field-level encryption is designed so stored database text is unreadable without the server-side encryption material.

Image references and metadata may be stored to render attachments and manage deletion workflows. Where an image is removed, its Cloudinary reference can be queued for cleanup through the asset deletion ledger.

Encryption reduces exposure if a database record is accessed without authorization, but no internet-connected system can be described as risk-free. Riqatiq is designed to minimize unnecessary data access and keep sensitive text protected at rest.

Riqatiq includes a 6-digit PIN vault layer for sensitive areas such as Release and Awareness Base. The PIN barrier is designed to prevent casual or internal platform access to private records unless the user unlocks the vault.

Security question answers are used for recovery checks and are handled as protected verification material. If you lose your PIN and cannot pass the configured security questions, the protected data can become permanently inaccessible as a defense against unauthorized recovery.

Because this design prioritizes user defense over convenience, Riqatiq cannot simply reveal or bypass your private vault data on request.

For allowed users who enable the reminder workflow, Riqatiq may use selected identity statements and awareness entries to generate personalized reminder emails twice a week.

The system is instructed to preserve chosen identity statements verbatim when referencing them and to synthesize awareness entries into a coherent reminder rather than exposing them as a mechanical list.

AI processing is used to produce the reminder text. Riqatiq aims to pass only the context needed for the reminder experience and to avoid unnecessary disclosure.

Riqatiq uses secure HTTP-only cookies for authentication across the Riqatiq service family. Access tokens are short-lived and refresh tokens are used to maintain continuity without repeatedly requiring sign-in.

Vault access uses additional short-lived session controls that are intended to lock private data after inactivity or tab closure.

You can end your authenticated session by logging out, and the system may invalidate sessions after password resets, account security events, or suspected token misuse.

Riqatiq retains account and product data while your account remains active and while the data is needed to provide the product experience.

You may delete certain records inside the application. Some deletion workflows may queue external asset references for later cleanup.

If you request a security reset after losing vault access, the wipe protocol described in the Terms of Service may permanently delete corresponding release logs and awareness records from live databases.