Aevia Beta Terms

BETA DRAFT — requires legal review before broad commercial launch.

These terms describe the closed-beta product as it works today. By activating Aevia, you agree to these Terms and the Privacy Policy.

1. Beta product

Aevia is early-stage software. Its output may be incomplete, delayed, inaccurate, misunderstood, or incorrect. Review important information and decisions before relying on them.

2. What Aevia does

Aevia can store household context, schedule agreed routines, create meal plans, send provider-based messages, interpret replies, and keep task records. CARE handles everyday senior routines. HOPS handles meal planning and kitchen coordination.

3. Important limits

Aevia is not a medical, health, emergency, nutrition, financial, or legal professional service.
A message saying a person completed a task is a self-report unless an independent verified source is explicitly shown.
Automated language interpretation may misunderstand a reply.
WhatsApp, internet, scheduling, or provider failures may delay or prevent a message.
You remain responsible for important household decisions and for verifying material actions and information.

4. CARE safety

CARE is an everyday routine assistant, not a doctor, healthcare provider, medical monitor, or emergency service. Verify medication names, timing, and instructions. Aevia must not be used to start, stop, change dosage, or materially change treatment based only on conversation or extracted information. Contact the appropriate local emergency or medical service for emergencies.

5. HOPS safety

HOPS’s calories, macros, TDEE, portions, and meal suggestions are planning estimates, not medical nutrition advice. Independently verify allergies, intolerances, religious restrictions, medically required diets, and ingredient substitutions.

6. Third-party recipients

If you configure Aevia to message a parent, senior, cooking person, or family member, you must introduce the product and make sure the recipient has agreed before recurring messages begin. Your acceptance does not replace their consent.

7. Responsible use

Provide accurate context, keep contact details current, review important changes, and do not use Aevia for unlawful, harmful, deceptive, or emergency activity. Do not treat provider acceptance as proof that a person read or acted on a message.

8. Beta operations

Authorized Aevia beta operators may access controlled product and agent data for debugging, support, exception resolution, safety review, evaluation, and product improvement. Sensitive data should be minimized and masked by default in operator tools where implemented.

9. Availability and changes

The beta may change, pause, or stop. Features may be added or removed. If these terms materially change, Aevia should request acceptance of the updated version before continued activation where the product supports it.

10. Leaving the beta

You may pause configured routines or ask to leave the beta. Data handling requests are addressed according to the implemented product capability and Privacy Policy. This beta does not yet promise self-serve export or deletion tools.