Alyrea
Privacy
A plain-language draft of what the current beta website and app actually do with data.
Your budget stays local by default
Budget plans, expenses, household labels, payment-method labels, goals, and related app settings are stored on your device in the default local mode. They are not sent to this marketing website. Platform backups may still include app data according to your Apple or Google backup settings.
Ori and outside providers
When Apple’s on-device model is available and selected, Ori’s reasoning stays on the device. If you configure OpenAI, Gemini, Anthropic, or another compatible provider, the prompt and the context needed to answer can be sent directly to that provider under its own terms. Alyrea can also send a neutral public search query for optional web grounding; the design excludes household balances, transactions, names, and other private financial data from that query.
Optional remote storage
The app includes an optional remote-storage mode for configured deployments. If you enable it, budget data is sent to the server you configure so it can store and return that household state. The release policy must identify any hosted service offered to ordinary users before that service is launched.
Beta and Pro interest forms
The beta form stores your email address, language, testing platform, and timestamps. The Pro form stores your email address, language, optional feature preference, optional short answer, and timestamps. Random session identifiers record whether a visitor viewed or completed these flows. The site does not use advertising cookies or collect financial records. The hosting provider may process ordinary network and security logs, such as IP address and request metadata.
Diagnostics
Operational diagnostics stay on the device, are limited to the most recent 500 events and 14 days, and can be cleared. A report leaves the device only when you choose to share it. The report is designed to exclude financial records, amounts, names, credentials, and household data.
Your choices
The app can export its budget data and clear local storage. You must also be able to request access, correction, cancellation or deletion, and objection where applicable—including Mexico’s ARCO rights—and withdraw from beta or Pro emails. The final policy needs one working contact and a documented response process for those requests.
Retention still needs an operational decision
Before deployment, choose and implement how long beta signups, Pro-interest signups, and anonymous funnel events are kept, how deletion requests are processed, and when old records are purged. The published policy should promise only the schedule the system will actually follow.