Privacy policy

Effective October 26, 2026.

Nutritiono is operated by Big Leap LLC. Contact hello@bigleap.app for privacy or data requests.

Information we collect

We collect your account email, a random account identifier, a salted password hash, account creation information, and the version and time of your sensitive-data consent. Your password is entered on our secure sign-in pages, not supplied to plugin tools. Email verification and password recovery are not available.

We store the intake facts you choose to record: descriptions, categories, amounts and units, intake times, reported or estimated calories, macronutrients, micronutrients and compounds, plus record identifiers and creation times. Food, beverages, supplements, alcohol, cannabis, medication and other intake can be recorded. Medication and substance-use history may reveal sensitive health information.

Use Nutritiono only for your own personal diary. Do not provide protected health information, clinical records, diagnoses, treatment details, another person's health information, or information you have no right to provide.

We store connection permissions, client registration metadata, sessions and security credentials. Essential cookies support sign-in, sessions and protection against forged requests. We use no advertising cookies or website analytics.

Abuse-prevention counters use keyed hashes derived from IP addresses or account emails, with attempt counts and expiration times. The counters do not store the raw IP or email. Hosting providers process network metadata needed to serve requests. We receive correspondence and information you send to support.

Purpose and consent

We use these data to authenticate you, enforce account permissions, prevent abuse, save and retrieve your history, calculate totals from reported facts, and handle support and verified data requests. We do not sell personal data, serve advertising, profile you for advertising, or use your entries to train models.

Our connection consent page prominently discloses sensitive intake processing. Read permission allows retrieving your own profile, entries and summaries; write permission allows adding and deleting your own individual entries. You can decline connection or choose not to enter a record.

Recipients and hosting

Google Cloud hosts the application and live database in the United States, and provides backups and other infrastructure. Authorized operators may access information when necessary for support, security or verified data requests. We may disclose information when legally required.

When you invoke Nutritiono, the profile, entries and summaries needed for your request are returned to your OpenAI product and processed under its policies and your account settings. Nutritiono cannot delete copies in OpenAI conversations; manage them through that product. Support correspondence also passes through the email services used by you and us.

Retention and security records

Entries remain in the live database until you delete them or a verified account-deletion request is completed. Account and consent records remain while your account exists. Client registration metadata remains while the registration exists; shared client registrations are not removed just because one user deletes an account.

Access and ID tokens expire after 15 minutes, authorization codes after one minute, pending sign-in interactions after ten minutes, login sessions after 24 hours, and connection grants and refresh tokens after 30 days. Refreshing can renew the credential lifetime. Abuse-counter windows expire after 15 minutes. Expired records become unusable immediately but are physically removed in bounded batches on later authentication activity; cleanup is not guaranteed at the expiry instant.

The shared database retains seven standard backup copies and seven days of point-in-time recovery transaction logs. Seven backups is a count, not a seven-day deletion guarantee. Deleted information can remain until an older backup is replaced. Operators must reapply completed deletion requests before resuming service after a backup restore. A protected deletion ledger holds the minimum account identifier, email and request reference needed to enforce those requests on recoverable backups and document the response; it contains no intake history or credentials and is retained only while needed for those purposes or applicable legal obligations.

Operational application logs retain data for 30 days; required infrastructure audit logs retain data for 400 days. Nutritiono's automatic Cloud Run HTTP request logs are excluded from storage in current logging sinks. Our application does not log intake contents, passwords or access/refresh tokens. Support correspondence is retained as necessary to handle requests and document responses or applicable legal obligations.

Your choices and rights

You can retrieve your own structured history through the API or plugin, following pagination for a complete history. Correct an entry by deleting it and adding corrected facts. Confirm the exact entry before deletion.

To request account deletion, withdraw consent or ask about your data, contact hello@bigleap.app with your Nutritiono account email. Do not send passwords, tokens or sensitive intake details. We verify account control and explicit confirmation before manually removing the account, live entries and account-linked connection records. Minimized abuse counters and backups follow the retention rules above. There is no automatic account-deletion interface.

Disconnecting the plugin does not delete Nutritiono's stored records. Depending on applicable law, you may have rights to access, correction, deletion, restriction, portability, withdrawal of consent or a complaint to a data-protection authority.

Children and updates

Nutritiono does not target children under 13. Users must be at least 13 and meet any higher applicable minimum age. Users under 18 need a parent or legal guardian's permission. Nutritiono must not be used to encourage underage alcohol, cannabis or other substance use.

We publish changes here with a new effective date. Material changes to processing purposes or permissions require updated disclosures and any required consent before they take effect.