Privacy
Health data is personal. Our approach should be understandable.
This pre-launch privacy overview describes Quevro’s current website practices and intended product design as of August 13, 2026. The app is still in development. A final, app-specific privacy policy will be published and reviewed before any public beta or release.
1. Who we are
Quevro is a product of Transcndnce LLC. This notice uses “Quevro,” “we,” and “us” to refer to Transcndnce LLC in connection with the Quevro product and website. Contact: lenny@quevro.com.
2. This website
This public, pre-launch website does not offer Quevro accounts, accept health records, or use a contact form. If you choose to email us, your email provider and ours process the message, and we receive the address, content, and any information you include.
We have not added advertising trackers or behavioral analytics to this website. Hosting and security providers may process ordinary technical request data—such as IP address, browser information, request time, and requested page—to deliver and protect the site. Their retention and processing may be governed by their own terms and legal obligations.
3. Data the planned app may handle
Quevro is being designed to handle data needed for calorie, weight, and energy tracking. Depending on the features a person chooses, this may include:
- account identifiers, such as an email address;
- profile and goal inputs, such as age, sex, height, weight, unit preferences, and target direction;
- food logs, meal details, calorie and macronutrient values, and saved foods;
- weigh-ins, trend-weight calculations, progress history, and related notes;
- adaptive TDEE inputs, confidence, quality flags, estimates, and target history;
- optional Apple Health data described below; and
- support communications and limited device or diagnostic information needed to troubleshoot the app.
The final privacy policy will identify the actual categories collected, their purposes, storage, retention, service providers, and available rights before beta access begins.
4. Apple Health and health information
Apple Health access is planned to be optional. When implemented, Quevro expects to request specific permissions in context and explain why they are useful. Depending on permission and availability, the app may read steps, workouts, active energy, resting energy, and body weight. The core product is intended to remain useful without this connection.
Apple Health and related nutrition or weight information will be treated as sensitive. Quevro is not intended to use health data for advertising, sell it, or make it available to data brokers. Access can be changed through Apple’s controls. Revoking access stops future reads but may not automatically remove information previously imported into Quevro; deletion behavior will be clearly documented and tested before release.
5. AI-assisted food estimates
Natural-language or photo-based food estimation may send the content a person chooses to submit to a server-side provider. These features are planned as optional enhancements. Results will be presented as editable drafts because nutrition estimates can be incomplete or wrong.
Before launch, Quevro will disclose the providers used, the information sent, the purpose, and relevant retention controls. Secrets for these integrations will remain server-side and will not be embedded in the mobile app.
6. Intended uses
Planned uses include providing account access; storing and displaying logs; calculating trend weight, energy balance, and adaptive estimates; generating explained targets; importing user-authorized Apple Health data; maintaining security; troubleshooting; responding to support; and complying with law.
8. Retention, deletion, and choices
Account deletion, data export where appropriate, correction, Apple Health permission controls, and support-assisted privacy requests are planned product requirements. Specific retention periods have not been finalized. Quevro intends to retain information only as long as needed for the purposes described, account operation, security, legal obligations, or a person’s valid request.
9. Security
Quevro’s architecture is planned around authenticated access, row-level ownership controls, server-side secrets, reviewed database migrations, and least-privilege integrations. No technical system can guarantee absolute security. Security and privacy behavior will be tested before external beta access.
10. Changes and contact
This overview will change as product decisions and providers are finalized. Material updates will be reflected on this page with a revised date. Privacy questions or requests can be sent to lenny@quevro.com.