Last updated: August 2026
Privacy Policy
This Policy explains what PreciselyMaybe processes, what it intentionally does not retain, where information is handled and the choices available to account holders.
1. Data minimization
PreciselyMaybe is designed to work without client identities, documents or confidential matter files. We collect only data needed for authentication, product operation, security, diagnostics, saved features and, when later enabled, billing. The raw matter description is treated as transient input rather than stored product content.
2. Account and profile data
If you create an account, Supabase Auth and the PreciselyMaybe profile may process your email, display name, interface language, location/profile fields provided at signup, pricing country and jurisdiction, currency, target hourly rate, plan and credit state, beta status and records of acceptance of applicable beta Terms and Privacy versions.
3. Browser storage
Supabase Auth may store session credentials in browser local storage so you remain signed in. The analysis flow may store structured in-progress state in browser session storage for the life of the browser session, including selected activities, structured answers, pricing inputs and calculated result state. The raw matter description is explicitly excluded from that saved flow snapshot.
4. Raw matter descriptions
The description you type is processed transiently to interpret scope. PreciselyMaybe does not intentionally write the raw description to its Supabase database, saved analyses, templates, calibration records, first-party analytics, AI-usage telemetry, billing tables, Paddle metadata or browser flow snapshot. Because it may be sent to an external AI provider for interpretation, do not include personal, privileged or confidential information.
5. AI providers
Authenticated scope interpretation and result explanation may be sent from the PreciselyMaybe server to hosted AI providers through an AI gateway. Prompt payloads are designed not to include your PreciselyMaybe account identity. PreciselyMaybe configures the gateway to disallow prompt training. Zero Data Retention is not claimed unless a supported zero-retention route is actually active. Upstream providers may otherwise keep operational records under their own terms.
6. Structured analysis, templates and feedback
When you use a feature that saves data, PreciselyMaybe may retain structured and sanitized fields such as area, work type, mode, language, jurisdiction, activity IDs, assumptions, effort ranges, risk, pricing figures, Price Fit, public-reference metadata, saved-result summaries and reusable templates. Calibration and feedback records may also contain ratings, comments, actual-hours fields and structured commercial figures. They are not designed to include the raw matter description.
7. Community
Community topics and replies are intentionally stored so registered users can participate in product-support discussions. They may include the author name shown in the Community and the text the user chooses to publish. Community fields must not be used for confidential matters, legal advice requests or client-identifying information.
8. Product analytics and AI telemetry
PreciselyMaybe may store first-party events such as analysis started or completed, step reached, mode, area, locale and technical outcome. AI-usage telemetry may record user ID, call type, model/provider, provider generation ID, token counts, latency, cost, success status and timestamp. These telemetry records are designed not to contain prompts, raw matter descriptions, answers or model output. PreciselyMaybe does not use third-party advertising cookies.
9. Future billing and Paddle
When commercial billing is enabled, Paddle acts as Merchant of Record for checkout. PreciselyMaybe may send Paddle the account email and the minimum commercial metadata required for customer and transaction creation, such as an internal account identifier, product key, purchase type and quantity. PreciselyMaybe stores Paddle customer, subscription and transaction identifiers and commercial status. Matter descriptions, client identities and analysis content are not intentionally sent in Paddle metadata.
10. Retention
Different data serves different purposes. Account and profile data is generally kept for the account lifetime. Saved subscription analyses and templates remain until deletion by the user or account deletion. A standalone result is commercially reopenable for 90 days from activation of its purchased unit and may later be removed under operational cleanup. Product analytics, AI telemetry and calibration data follow data-minimization and operational-retention controls. Infrastructure providers may maintain security or operational logs under their own settings.
11. Delete stored data
The Account page offers controls for stored product data. Depending on the action selected, saved analyses, templates, user-linked calibration and feedback, first-party events and AI-usage records may be removed while the account remains active. Community content and minimum financial records follow their separate retention rules.
12. Delete account
Account deletion removes the Supabase Auth user and account-linked product data. Community discussions are preserved where possible while the former author's identity is anonymized. Minimum financial or transaction records may be retained after deletion when needed for reconciliation, tax, fraud prevention, refunds, disputes or other legal obligations. Matter descriptions and analysis content are not retained as payment metadata.
13. Security
Traffic is encrypted in transit and access to operational systems is restricted. Authentication, row-level database rules and server-side authorization are used to separate user data and protect commercial state. No system is perfectly secure, so users must still avoid submitting confidential or identifying matter information.
14. Your choices and rights
Subject to applicable law, you may request access to, correction of or deletion of information associated with your account, or ask that processing stop where applicable. Signed-in users can use the Account page for available deletion controls. Other requests can be made through the contact channel below.
15. Changes to this Policy
This Policy may change as the product, billing, retention controls and infrastructure evolve. Material changes will be reflected with a new date or policy version. Public copy will not claim zero retention, automatic deletion or another safeguard unless it is actually active.
16. Account deletion, Community anonymization and payment retention
Deleting the account removes account-linked analysis data and makes unused credits, unused one-off units and remaining product access unavailable. Community topics and replies are preserved where possible while the former author's identity is anonymized. When paid billing is active, PreciselyMaybe' working policy is to retain only the minimum financial/payment records needed after account deletion for 90 days; if applicable accounting, tax, fraud, refund, chargeback or other legal obligations require a longer period, the legally required minimum period prevails. Matter descriptions and analysis content are not retained as payment metadata.
Contact
Privacy questions or data requests may be submitted through the product contact channel made available by PreciselyMaybe. Signed-in users can also use the data controls available in Account.
PreciselyMaybe minimizes stored matter data by design and does not use third-party advertising cookies.