Privacy Policy

Data We Use

Raivora stores account details, settings, weight entries, calorie entries, cycle data, goals, and product events needed to provide the app experience, keep sessions secure, and improve reliability.

Sensitive progress data is used to power your private app views and calculations. We do not sell personal progress data.

If you use detailed nutrition logging or the nutrition assistant, meal text, food names, calories, macros, dates, and correction preferences may be processed to create or improve your food entries. A structured meal estimate may be retained briefly so you can ask a follow-up portion question; raw recipe messages are not retained in production assistant audit records. When a dedicated nutrition model is enabled, Raivora sends the meal text needed for parsing to the configured model service.

Transactional email providers may receive your email address and the verification or password-reset messages needed for account security. Payment providers may receive checkout, subscription, tax, and billing metadata needed to process paid plans.

Security

Authenticated app routes require a valid session. Mutating requests use CSRF protection, and administrative surfaces remain restricted to authorized accounts.

Passwords and session tokens are not stored in plain text. Security controls include request-size limits, rate limiting, email verification, account-recovery tokens with expiry windows, and audit records for administrative and billing actions.

Your Choices

You can update account settings, export available account data, and request deletion from the profile and data-management areas inside the app.

Account deletion requests are processed according to the configured retention policy. Some operational, security, billing, or legal records may be retained when needed to protect the service, prevent abuse, complete transactions, or satisfy compliance obligations.