Privacy, thoughtfully.
Updated November 18, 2026
Aven is a private household service operated by Fizzify Inc., a division of Nourishing Inc., 30 N Gould St, Ste N, Sheridan, WY 82801, United States. This app-specific notice explains what the Aven service processes. It supplements the operator’s general notices and controls for Aven where they differ.
What you choose to share
We process your identity-provider subject, verified email, display name, household memberships and role, preferences, invitations and responses. Household plans include meal or event dates, counts, location, food requests and any dietary or allergy information you enter. Avoid adding medical details the household does not need to provide the requested service.
Managers can enter appointments, import one selected calendar occurrence, and save a house contact after reviewing it. We process the selected event’s title, time, timezone, location, notes and source identifiers. A selected contact can include a name, company, email, phone and extension, notes and field provenance. Calendar/contact files and device contact matching are handled locally before the selected fields are saved. Aven does not upload your complete device calendar or address book and does not modify device contacts.
Connected email
A manager deliberately selects a connection authorized for their identity. Appointment discovery processes bounded email metadata, message IDs and short excerpts, and proposes appointment/contact fields for that manager’s review. Dates and signatures can be wrong; nothing is imported, merged or sent automatically. Manager-composed email drafts include the From identity, recipients, subject, body, optional reply identifier, revision and delivery status. Sending requires a separate explicit action tied to the reviewed draft revision. Provider credentials are encrypted on the server and never returned to the client. Disconnecting removes Aven’s reusable credential and cached email content; reviewed imports remain.
The current connection adapter supports operator-provisioned, explicitly authorized Gmail IMAP/SMTP connections; self-service Google OAuth is not enabled. No email is sent to an external AI model. If Google API authorization is added, Google user data must be used only for the requested household email features, consistent with Google’s API Services User Data Policy and Limited Use requirements; this notice and consent will be updated before that integration is enabled.
Invitations and notifications
We process inviter/invitee identifiers or email addresses, offered household roles, invitation context, expiry and response, attendance, and delivery state. Existing-user invitations appear in an inbox. Email invitations use the operator’s existing Mailcow transactional sender; opening the link does not accept it. Invitation tokens are random, hashed for lookup, and briefly encrypted in the delivery queue. Meal attendance is separate from household membership.
The inbox persists changes even when push is disabled. Native remote push, when provisioned and allowed, processes Aven-specific device tokens and generic message content through Expo’s Push Service and Apple/Google notification delivery. Lock-screen payloads exclude dietary notes and mailbox excerpts. Timed reminders and immediate change alerts have separate preferences. Browser OS push is not enabled; the web inbox remains available.
Who sees what
Residents see their bookings and meal invitations they accept. Chefs see household dining and catering details, including dietary requests needed for service. Managers see household plans, memberships and the manager-only house directory. Appointments, mail suggestions and vendor contact details are restricted to managers. A manager’s mailbox and drafts remain restricted to that connection’s owner. Other residents do not receive household-wide meal broadcasts. Operator access is limited to running and supporting the service. We do not sell Aven data or use it for advertising, ad tracking or general AI training.
Service providers and security
Aven runs in the operator’s self-hosted Docker environment, using PostgreSQL and a dedicated realm in the existing Keycloak identity provider. Mailcow delivers invitations; Gmail handles an authorized manager’s mailbox; Expo, Apple and Google handle enabled push. Your browser/device receives the fields you are authorized to view. Public-site fonts are served locally. The architectural image on the public site is synthetic, not the private residence photograph.
We use HTTPS at the public reverse proxy, server-side role checks, encrypted connection credentials, secure native token storage in integrated mobile builds, short-lived sessions, rate limits and audit records. Browser access/refresh tokens stay in memory. No system can guarantee complete security. The public hostname’s HTTPS proxy must be configured before the service is used over the internet.
Retention and deletion
Aven’s worker clears cached suggestion content and completed/failed/cancelled draft content after 30 days, retains message identifiers needed for deduplication, and clears old delivery payloads/provider IDs after 30 days. The notification inbox and concise application audit records expire after 90 days. Idempotency responses expire after 30 days. Active household plans and reviewed shared contacts remain until changed or removed through the household’s authorized workflows. Uncertain deliveries are held for operator review instead of being resent automatically.
Deleting your Aven account disables all further Aven access, removes devices, connections, profile fields, preferences and your stored draft content, clears personal reservation notes and cancels future bookings you own. A nonreversible identity tombstone prevents a deleted session from silently recreating the account. Anonymized household reservation/attendance and security records can remain to preserve service history and integrity. Shared vendor contacts intentionally reviewed for household use and messages already delivered to other people are not automatically erased. The last manager must appoint another manager first.
The shared identity-provider account is separate from your Aven membership; deleting it may affect other services and requires a separate request. Historical backups and reverse-proxy infrastructure logs follow the operator’s existing retention, which has not yet been verified for an Aven-specific duration. Restricted backup copies may retain deleted data until their rotation; restored data must reapply deletion records.
Your choices and support
Calendar, contact and notification permissions are optional. You can change reminders, disconnect email or request account/data deletion. Use Account deletion or the operator’s existing contact form with “Aven” in the subject. Do not include passwords or sensitive dietary/mail content in a support request. We will verify ownership before disclosing or deleting account data. Material changes will be reflected in this notice.