Privacy should feel like a boundary, not a puzzle.

1. Information we collect

What we collect depends on which parts of Aeolus you use.

• Account information: email address, display name, authentication-provider identifiers, account state, and preferences. Guest use creates an anonymous service account so saved work can remain isolated from other users.
• Planning and memory content: time windows, starting places, destinations, constraints, preferences, chat messages, itineraries, saved activities, invitations and responses, logged visits, private notes, ratings, photos, reviews, and story settings.
• Location information: place names, activity coordinates, a browser location when you request nearby results, and device position updates while an explicitly opened offline-navigation feature is active. Aeolus is not designed for continuous background movement tracking.
• Communication and safety information: notification subscriptions, email preferences, phone number, and an emergency contact's name and phone number if you choose to configure features that require them. Feature availability depends on system configuration.
• Technical and usage information: browser/device details, IP address and request logs, security signals, errors, and a small allow-list of first-party product events such as whether a landing CTA was selected or a Side Quest result was used. These events reject precise coordinates, free text, invitation tokens, and names.

2. How information reaches us

We receive information directly from you, from your device after a permissioned action, from people responding to an invitation you created, from an authentication provider you select, and from service or data providers needed to answer a request. We do not trigger the browser location prompt when the landing page loads.

3. Why we use information

• Provide, personalize, save, and synchronize plans, recommendations, invitations, memories, and settings.
• Resolve places, calculate travel constraints, retrieve forecasts, classify weather windows, and generate relevant fallbacks or packing guidance.
• Deliver requested emails, push notifications, or messages and operate configured check-in workflows.
• Secure the service, prevent abuse, enforce limits, debug failures, and understand whether core workflows succeed.
• Comply with law, protect rights and safety, and communicate material service or policy changes.

4. AI-assisted features

Aeolus uses configured language-model providers to understand planning requests, arrange itineraries, explain recommendations, and extract structured memories. The content necessary to answer a request may be sent to those providers. Deterministic weather guardrails are applied separately from model prose. Do not include highly sensitive information that is not needed for travel planning.

5. When information is shared

We share information only as needed for the following purposes:

• Service providers: infrastructure, hosting, database/authentication/storage, AI, weather, map/place, email/SMS/push, background-job, caching, and security providers process data for us. Current integrations can include Vercel, Supabase, configured language-model providers, NOAA/NWS, Tomorrow.io, OpenWeatherMap, Mapbox, OpenStreetMap/Nominatim, Resend, Twilio, Inngest, and Upstash, depending on configuration and location.
• People you choose: invitation recipients see the bounded plan plus the sender name and any note chosen for that invitation. Response totals and names or replies that guests opt to show may also appear to other recipients. A story file is shared only through the destination you choose after export.
• Public contributions: a place review or associated media appears publicly only after you deliberately enable its public state. Private note text is not automatically converted into a public review.
• Legal and organizational events: we may disclose information when required by law, to protect rights or safety, investigate abuse, or as part of a merger, financing, acquisition, or sale, subject to appropriate protections.

We do not sell personal information and do not use it for third-party targeted advertising.

6. Cookies, local storage, and analytics

Aeolus uses essential session cookies for authentication and security. It also uses browser storage for choices such as theme, motion, a last-used starting place, local UI state, and hidden memory resurfacing. Signing out clears the saved starting place and private offline trip downloads from that browser. Our product analytics are first-party and limited to declared event names and constrained properties; we do not place third-party advertising cookies on the landing page.

If you explicitly download a trip for offline use, its itinerary and route package remains on that browser until you remove the download, sign out, clear site data, or the browser evicts it. Shared map assets expire automatically and may be reused across nearby downloads.

7. Photos and metadata

Uploaded memory photos are validated, re-encoded, resized, and stripped of EXIF metadata before permanent storage. This reduces accidental disclosure from embedded camera and location metadata, but the visible image itself may still reveal people, places, or other sensitive details. Only upload media you have the right to use.

8. Retention and deletion

We retain information while an account is active and as reasonably needed to provide the service, resolve disputes, maintain security, comply with law, and enforce agreements. Different records can have different operational lifetimes. Deletion from active systems may not immediately remove limited backup, fraud-prevention, or legal records.

Signed-in users can download a structured copy of their account data or permanently delete their account and active-system data from Account / Privacy. Permanent accounts must have authenticated within the previous 30 minutes before deletion. Relational deletion is atomic; uploaded-photo removal is durably queued and retried if object storage is temporarily unavailable. For correction, other rights requests, or help when those controls are unavailable, email founders@aeolustravel.com from the address associated with your account when possible. We may need to verify identity before fulfilling a request.

9. Your choices and rights

• Use a manually entered place instead of browser location.
• Decline or revoke browser, push, or other device permissions through device settings.
• Use the unsubscribe link in a marketing or alert email where provided.
• Keep a memory private, retract a public review, or choose the fields included in a story export.
• Request access, correction, deletion, portability, restriction, or objection where applicable law provides those rights.

10. Children

Aeolus is not directed to children under 13, and we do not knowingly collect their personal information. If you believe a child has provided information, contact us so we can investigate and take appropriate action.

11. Security and international processing

We use administrative, technical, and organizational safeguards appropriate to the service, but no storage or transmission method is perfectly secure. Providers may process information in the United States and other countries whose laws differ from yours. If applicable law requires safeguards for a particular transfer, we will put those safeguards in place before making that transfer; contact us for information relevant to your request.

12. Changes and contact

We may update this policy as Aeolus changes. We will revise the date above and provide additional notice when required. Questions or complaints can be sent to founders@aeolustravel.com.

Aeolus Labs LLC
Illinois, United States