How Revora handles your data

Information you provide

• a meal description and your latest A1C;
• an email address when you create an account or buy a report;
• optional meal-check photos;
• Pantry Review photos, notes, and corrections;
• reminder preferences and actions you mark complete;
• messages you send to support.

How a meal check works

Revora sends the submitted meal description and A1C to OpenAI's Responses API to generate a response. Calls set store: false, which disables default API response storage. OpenAI may still retain limited abuse-monitoring records under its service terms. Meal-check photos are used in memory to draft text for your review and are not saved as meal-check history.

Guest use

Revora does not create server-side meal history for a guest. Recent checks and onboarding settings may remain in that browser's local storage until you clear the site data. Request data still passes through Revora's hosting provider and OpenAI to answer the check.

Account use and explicit consent

With explicit health-data consent, Revora saves your email, encrypted A1C, encrypted meal text, general result category, dates, history, progress, and optional reminder registration, plus derived pattern summaries. The purposes are to provide saved checks, cross-device history, progress, personalized pattern summaries, reminders, support, security, and subscription access. Revora does not use this information for ads or sell it.

Pantry Review

Pantry Review uploads photos to a public but unlisted, long random URL while the report is prepared. OpenAI helps turn the photos into an item list that you review and correct. Photos are deleted after extraction or delivery according to the report workflow. Item names, notes, A1C range, and the finished report are encrypted at rest until deletion.

Pantry Review photos

If you buy a Pantry Review, the photos you upload are held by Revora's storage provider at a long, random, unlisted address. They are never linked to, listed, or indexed anywhere — but the address itself is the only thing protecting them, so Revora handles it as a secret. The photo is deleted when the report is delivered; within the hour if the order is canceled, refunded, or sent for manual review; when you delete your account; and otherwise no later than seven days after upload.

A vision model through OpenAI's API, with store: false, reads food items into a list that you review and correct. Item names, notes, A1C range, and the finished report are encrypted at rest.

Meal-check photos are processed in memory to draft text for your review and are never stored as history. Only confirmed text is checked and, for a consenting signed-in account, saved.

Service providers and recipients

Revora uses these provider categories for the stated purposes:

• OpenAI for meal-check responses and Pantry Review extraction, plus meal photo-draft generation;
• Vercel for application hosting and delivery;
• Railway-hosted Postgres for encrypted account data;
• Resend for sign-in, reminder, and service email;
• Google Play and Stripe for purchases and subscription status;
• Sentry for scrubbed error reporting;
• Umami for coarse, non-identifying product analytics;
• browser and push-delivery services when you enable reminders.

These providers may process information in the United States or other countries where they operate. Revora limits each provider to the information needed for its role and does not send raw meal text, exact A1C, or email to analytics or Sentry.

Security

Exact A1C, saved meal text, Pantry Review item details, notes, and reports use AES-256-GCM encryption at rest. Account routes require an authenticated session and scope reads to the account owner. Payment card numbers stay with Google Play or Stripe. No security measure can eliminate every risk.

What Revora never does

• sell or share your personal data,
• show ads,
• store your health data without your explicit consent,
• keep health data after the applicable erasure or account-deletion flow completes, except for the identity-free completion record and transaction records that must remain with payment providers.

Retention and deletion

• Guest server input is dropped after the request completes.
• Account health data remains until you erase it or delete the account.
• Meal-check photos are not retained as history.
• Pantry photos are removed by the report workflow after use.
• A non-identifying hash and timestamps may remain after deletion to prove that a deletion completed.
• Payment providers may retain transaction records under their own legal and accounting obligations.
• Billing event records (from our payment providers) are kept for up to 30 days for payment reliability and dispute handling. Buyer contact details are removed from these records as soon as the event is processed.

Your choices and rights

From Account, you can turn reminders off, withdraw saved-health-data consent and erase the saved A1C/history while keeping your login and subscription, or delete the whole account. Account deletion is also available at /account/delete.

You may ask to access, correct, export, or delete personal information and may appeal a denied request by replying with “Privacy appeal” to support@revora.plus. Revora will verify the request using the existing account or another reasonable method. Rights vary by location; Revora will honor mandatory rights that apply to you.

Health-data incidents

Revora investigates unauthorized access or disclosure and will notify affected people and authorities when applicable law requires it. A notice may arrive by email together with an in-app or website notice.

Children

Revora is for adults 18 and older and is not directed to children. If you believe a child submitted information, contact support@revora.plus.

Changes and contact

Material changes will appear here with a new effective date and, when appropriate, an account notice. Privacy questions and requests: support@revora.plus.

Revora is informational only and is not medical advice. Talk with a doctor or registered dietitian for guidance that is specific to you.