Aevia Beta Privacy Policy

This policy explains the information Aevia Beta V1 may process, why it is used, and the controls that exist today.

Aevia is an early-stage beta service operated from India. For support, privacy and data requests, contact support@helloaevia.com. The beta is for users aged 18 or older.

1. Information Aevia may process

Account and profile details, including name, email, time zone, and beta acceptance.
Household members, roles, preferences, language, routines, schedules, and communication endpoints.
Food preferences, allergies, dietary rules, meal plans, nutrition estimates, cooking-person setup, inventory, and shopping-needed items.
Routine and medication-reminder context supplied by users, including familiar labels, exact names when provided, schedules, notes, replies, and stated source or certainty.
WhatsApp or development-transport messages, replies, reactions, delivery state, and provider identifiers.
Agent runs, ordered steps, corrections, feedback, exceptions, and operator-review information.
Privacy-safe product usage events such as landing views, onboarding progress, activation, and task outcomes.

2. Why this information is used

Aevia uses information for personalization, scheduling, task execution, communication, memory and context, safety and exception handling, debugging, user support, evaluation, beta improvement, and product analytics.

3. Source and certainty

Aevia should distinguish user-provided facts, another person’s self-report, extracted candidate information, and agent inference. A self-report is not independent verification. An estimate is not professional advice.

4. Service providers

The current product uses Convex for application data/runtime and can use messaging providers behind a replaceable transport layer. Development transport remains available. Meta WhatsApp Cloud API is the current real test provider. Provider services process data under their own terms and policies.

5. Beta operator access

Authorized Aevia operators may need controlled access for debugging, exception resolution, safety review, support, evaluation, and product improvement. Operator tools should mask sensitive fields by default and require deliberate reveal where that control is implemented. M5 adds a household-scoped run viewer; a complete access-controlled admin system is not yet built.

6. Analytics limits

Aevia uses PostHog for limited product analytics when it is configured. Only approved events and route paths should be sent. Phone numbers, household messages, form values, names, medical information, secrets, URL query values, and unnecessary personal information must not be sent to PostHog.

7. Your choices and data requests

Where currently supported, you can review setup, correct active context, update preferences, and pause or change routines. Correction or supersession updates what Aevia should use while preserving the history needed to understand the change.

To request removal of specific private context, email support@helloaevia.com. Where applicable, the requested context is removed or suppressed from future Aevia use while your account, unrelated context, household relationships, and continued use remain.

Explicit account closure is a separate, manual operator-assisted request. After identity verification, it may deactivate access, disable applicable Aevia activity, routing, reminders and eligibility, and remove, suppress or de-identify applicable active personal information.

Sending STOP on WhatsApp only withdraws consent for proactive WhatsApp messages. It does not close your account or delete your personal information, household membership, or history. A later inbound message does not restore proactive consent; explicit re-consent is required.

Aevia does not currently provide self-service account closure or a full self-service export tool. Read Data requests and account closure for the current process and limits.

8. Third-party information

Only provide another person’s information when appropriate, and introduce Aevia before automated messages begin. A parent, senior, cooking person, or family member should not receive surprise recurring messages.

9. Medication information

Aevia may store medication names, reminder labels, times, notes, and replies that a user provides for reminder and context purposes. User-provided information is not treated as independently verified. Aevia does not interpret prescriptions, recommend treatment, or confirm adherence. Medical-document processing is not part of the current beta.

10. Security and retention

Aevia uses application ownership checks and provider webhook validation in the current beta. No system is perfectly secure. We do not claim security, retention, deletion, or compliance guarantees beyond what is actually implemented.

After explicit account closure, minimum records may remain where needed for safety or security, consent and audit history, provider execution, fraud or abuse prevention, legal obligations, and backup or recovery integrity. Account closure does not promise immediate deletion, complete physical erasure, deletion from every backup, zero retained records, or a completion timeline. Restored data must remain subject to the completed suppression or closure state.