Legal
Privacy Policy
Last updated: October 23, 2026
This Policy explains what personal information Anovel handles, why it is needed, where it goes, how long it is kept, and the choices available to you.
Start here
Privacy at a glance
Guest data can stay in your browser. Account data is saved to Anovel's private service.
Anovel does not sell personal information or use it for targeted advertising.
The current Service has no advertising pixels, analytics SDKs, or cross-site trackers.
Trips are not public by default. Invites and public links disclose only defined fields.
Documents reach a configured AI provider only after you choose extraction and acknowledge it.
Upload only information you are entitled to provide, and remove details you do not need.
1. Who we are and what this Policy covers
This Policy applies to the Anovel website, applications, account service, and related trip-planning features that link to it (the “Service”). The data controller is [TODO: insert the Operator's legal name, entity type, registration number, registered address, and country]. In this Policy, “Anovel,” “we,” “us,” and “our” mean that Operator.
This Policy does not govern a travel supplier, booking site, social network, map or media provider, AI provider acting for its own purposes, or another website you choose to visit. Their policies apply to their services. If you provide information about a travel companion or another person, you must be authorized to do so and should show them this Policy where required.
2. Information we handle
What Anovel handles depends on the features you choose and whether you use browser-only or account storage. We do not require every item below from every user.
| Category | Examples | Where it comes from |
|---|---|---|
| Account and profile | Name, email address, email-verification status, password hash, account identifiers, language, time zone, account status, Terms version and acceptance time, and a marketing preference that currently defaults to off. | You; or Google if you choose Google sign-in. |
| Authentication and security | Session and verification identifiers, session expiry, IP address, browser or user-agent information, sign-in method, OAuth identifiers and tokens where applicable, rate-limit records, and security events. | Your device, browser, authentication flow, and our systems. |
| Trip and traveler details | Origins, destinations, dates, traveler counts and child ages, flight preferences, passenger names, booking references, flight numbers and times, itinerary items, addresses, notes, saved places, packing items, and travel preferences. | You, a collaborator, a file you upload, or an item you import. |
| Files and extracted information | Travel confirmations, insurance policies, images, audio, video, documents, filenames, type, size, checksum, extracted text, structured fields, processing status, and error details. Files may contain identification, financial, health, accessibility, location, or other sensitive information that you chose to include. | You, your device, and the extraction feature you request. |
| Saved recommendations | Links, captions, creator or source labels, uploaded source media, notes, recommendations, evidence, confidence or issue labels, coordinates, priority, and schedule placement. | You, a public page you submit, or local analysis of an authorized upload. |
| Sharing and collaboration | Invitee email, role, membership, invitation and public-link status, expiry and revocation records, and the trip fields included in the selected sharing method. | You, the trip owner, collaborators, and recipients. |
| Communications | Verification, password-reset and invitation messages; delivery status; and information you include in a support, privacy, legal, or feedback request. | You and our email or support systems. |
| App and device activity | Recently viewed in-app pages, active-trip selection, temporary return paths and drafts, request identifiers, timestamps, service responses, and minimal operational diagnostics. The current Service does not use a product analytics or advertising SDK. | Your browser and our services when you use the relevant feature. |
| Provider responses | Weather results, geocoding results, map resources, and validated AI extraction output. Anovel does not currently process travel payments or receive full payment-card numbers. | Service providers responding to a feature you request. |
Some travel information can reveal sensitive facts by inference—for example, a precise itinerary can reveal where someone will be and when. Please avoid adding information that is not needed for planning.
3. Why we use information
Where European or UK data-protection law applies, the table also identifies the legal bases we expect to rely on. The final legal-basis assessment must be completed before public launch and may vary by feature and jurisdiction.
| Purpose | Information involved | Expected basis where required |
|---|---|---|
| Provide the Service | Account, trip, traveler, files, recommendations, preferences, and requested provider responses. | Perform our contract with you; take steps you request before entering it. |
| Authenticate and protect | Account, session, IP, user agent, verification, rate-limit, and security records. | Contract; legitimate interests in preventing abuse and securing users and the Service; legal obligations. |
| Process a chosen feature | Files, prompts, trip context, place queries, dates, or source links needed for extraction, maps, weather, or local analysis. | Contract or the action you request; consent where law or the sensitivity of a feature requires it. |
| Enable sharing | Trip projections, member roles, recipient email, invite and link records. | Contract and your instructions; legitimate interests in reliable permission and revocation records. |
| Communicate | Email address and message or request details. | Contract for service messages; legal obligations; consent for optional marketing. Anovel does not currently offer marketing enrollment. |
| Maintain and improve | Minimal diagnostics, feedback, and aggregated or de-identified information where lawful. | Legitimate interests in reliability and product improvement. This does not authorize activating analytics or using sensitive trip content for advertising. |
| Comply and resolve | Records reasonably needed for legal requests, disputes, audits, safety, fraud prevention, and rights requests. | Legal obligations and legitimate interests in establishing, exercising, or defending legal claims. |
You can browse public discovery content without an account. If required information is not provided, the related feature may not work—for example, an email is required for an account and a destination is required for a destination-specific forecast. Optional features remain optional.
4. Where information is stored
Browser-only mode
Trip plans and preferences can be stored in your browser using local storage and IndexedDB. Short-lived navigation state can use session storage. This information stays on that browser profile unless you explicitly import it into an account, share a snapshot, request a server feature such as weather or geocoding, or choose document extraction. Browser storage is not encrypted by Anovel, is available to anyone with sufficient access to that browser profile, does not automatically sync, and may be removed by browser or device cleanup.
Account mode
When account services are enabled and you sign in with a verified account, PostgreSQL is authoritative for account trips, permissions, private collections, and file metadata. Original private files are kept in private object storage or, in local development, a private local volume. An explicit import copies selected browser data to the displayed account and verifies records and file hashes; it does not silently delete the browser originals.
Local processing
My Finds analysis currently runs on the operator's configured local computer using a loopback service, local Ollama models, and local Whisper speech recognition. Completed, partial, failed, cancelled, or needs-input worker copies expire after seven days; saved browser or account records remain until removed separately. A public Instagram URL is contacted only when that acquisition provider is explicitly enabled and you submit the URL; it is disabled by default.
5. Uploaded documents and AI-assisted processing
Flight confirmations, insurance policies, and general travel documents can be sent to the configured extraction service after you choose the feature and acknowledge its disclosure. Depending on deployment configuration, the service uses either OpenAI or Google Gemini—not both for the same request—to receive the document or extracted text, a bounded prompt, a scoped trip reference, and technical request information. The provider returns structured fields that Anovel validates. You must review those fields; they do not change approved flight facts until you save them.
The extraction service keeps a separate working copy of the original, derived text, validated result, model name, status, timestamps, and limited error details. Deleting the related extraction for a trip removes those active extraction records and working files. Automatic expiry for this extraction workspace and production provider retention are not yet finalized and are launch blockers. [TODO: approve exact active, failure, provider, and backup retention periods and confirm contractual no-training controls for the selected provider.]
Anovel does not use an AI result to make a solely automated decision that produces a legal or similarly significant effect. Anovel will not permit a third-party provider to train a general-purpose model on User Content unless that use is specifically disclosed and any consent required by law is obtained.
7. Providers and external services
This register distinguishes current code paths from configurable or future production providers. A provider receives data only when its feature is configured and used.
| Provider or category | Purpose and data | Status |
|---|---|---|
| Supabase-hosted PostgreSQL | Hosts account, profile, consent, trip, permission, collection, file-metadata, and operational database records through Anovel's private direct database connection. Supabase Auth and browser Data APIs are not used. | Selected production database host; final region and public-launch configuration must be confirmed. |
| Private S3-compatible storage | Stores private original files and their object metadata; short-lived signed upload or download URLs can be used. | [TODO: identify the production provider, region, subprocessors, and deletion lifecycle.] |
| SMTP email delivery | Receives recipient address and verification, reset, email-change, or invitation message content. | Local development uses Mailpit. [TODO: identify and contract the production sender.] |
| Google OAuth | If enabled and chosen, exchanges sign-in requests and returns Google account identifiers, name, email, and provider tokens needed for authentication. | Optional; not active without operator configuration and your choice. |
| OpenAI or Google Gemini | Processes acknowledged document content, extracted text, bounded prompts, and scoped references to return structured extraction data. | One configured provider per deployment. Provider, model, region, terms, and retention must be confirmed before launch. |
| Open-Meteo | Receives destination coordinates, requested date range, units, and time-zone parameters for weather. Anovel does not send your account identity. | Used when you open or refresh trip weather and for limited itinerary weather summaries. |
| Photon / OpenStreetMap geocoding | Receives a place or address query and optional location, country, and language bias. The shared public Photon endpoint is permitted only for local preview; production requires an approved private endpoint. | Feature-dependent and server-mediated. |
| Map and image hosts | A configured map-style/tile host and some remote Unsplash or iStock image URLs receive ordinary web requests, which can include IP address, device and browser information, requested resource, and referrer information subject to browser policy. | OpenFreeMap is the keyless local-preview map style; production map host remains configurable. Most product images are bundled locally. |
| Instagram or another submitted source | May receive a request for a public URL you ask the local My Finds worker to acquire. No browser cookies are supplied by that worker. | Instagram acquisition is disabled by default and must be deliberately configured. |
| Hosting, CDN, monitoring, support, and advisers | May process request metadata, operational records, or information needed to provide their service. | [TODO: identify production hosts and any support or monitoring tools before they receive personal information.] No dedicated monitoring or analytics vendor is currently installed. |
9. When information is disclosed
Anovel may disclose information only as reasonably necessary:
- to processors and service providers in the register above, under appropriate restrictions;
- to collaborators, public-link viewers, invitees, or external apps when you direct the disclosure;
- to a travel or content provider whose website or feature you choose to open or use;
- to professional advisers, auditors, insurers, and financing parties subject to confidentiality duties;
- to authorities or other parties when reasonably necessary to comply with law, protect rights and safety, investigate abuse, or establish, exercise, or defend legal claims; or
- to a successor in a merger, financing, reorganization, insolvency, or sale, subject to applicable law and continued notice of materially different practices.
Anovel does not sell personal information. Anovel does not share it for cross-context behavioral advertising, use sensitive travel information to target ads, or disclose personal information to data brokers.
10. Retention and deletion
We aim to keep identifiable information only as long as needed for the purpose described, security, legal obligations, and claims. The current implementation has the concrete periods and controls below. Missing production periods are stated rather than guessed.
| Information | Current behavior |
|---|---|
| Browser records | Remain until you delete an item in the Service, use an available discard control, clear the site's browser data, or the browser or device removes them. Session storage normally ends with the browser session. |
| Guest trip draft | The app rejects a saved draft after seven days. The expired browser value may remain unread until replaced, discarded, or browser data is cleared. |
| Account session | Configured for up to seven days and may end earlier through sign-out, revocation, password reset, or account action. |
| Account, trip, and private files | Kept while the account or content is active. Deleting a trip removes active database records and queues its private objects for cleanup. An account-deletion request disables access immediately; final purge is currently an explicit operator action. [TODO: approve and automate an active-data deletion service level.] |
| Invitations and public links | Access ends on expiry or revocation. Operational records can remain until cleanup. [TODO: approve the record-cleanup period.] |
| Signup and operational records | The browser consent-intent cookie expires after one hour. Expired server intents, rate-limit buckets, sent email-outbox rows, and limited security records require an approved production cleanup schedule. |
| My Finds worker copies | Terminal local-worker copies expire after seven days. Saved sources and recommendations remain in browser or account storage until separately removed. |
| Document extraction workspace | Working originals, derived text, results, status, and errors remain until the trip-and-purpose deletion action or operator cleanup. [TODO: approve automatic expiry and confirm provider-side retention.] |
| Backups and legal holds | [TODO: approve backup locations, encryption, restoration controls, expiry, deletion-tombstone behavior, and legally required exceptions before launch.] |
Deletion cannot erase information that another person already copied, content retained independently by an external service, or records we must keep under applicable law. Where deletion is not possible, we will restrict use when required. Aggregated or irreversibly de-identified information may be retained where lawful.
11. How we protect information
Current safeguards include hashed passwords; secure, HttpOnly session cookies outside local preview; email verification; origin and authorization checks; request and file limits; private database access; hashed invitation and public-link tokens; short-lived signed private-file URLs; checksums; input and model-output validation; role-based trip permissions; private no-store responses; restricted logs; and separation of public trip fields from private collections and files.
No system is perfectly secure. Keep independent copies of critical travel information, use a unique password, protect your device, review trip members and links, and contact us promptly if you suspect unauthorized access. [TODO: publish the production security contact and incident-notification process, complete backup restoration testing, and confirm provider controls before launch.]
12. Your choices and privacy rights
Available product controls let you correct account and trip details, delete trips and files, revoke invitations or public links, remove members if you are the owner, sign out, clear browser data, and request account deletion. Account deletion does not silently transfer ownership of your trips. Browser originals preserved after an account import must be removed separately on the original device.
Depending on where you live and subject to legal exceptions, you may have rights to be informed; access and obtain a portable copy; correct; delete; restrict or object to processing; withdraw consent without affecting earlier lawful processing; opt out of sale, targeted advertising, certain sharing or profiling; appeal a denied request; and receive equal service without unlawful discrimination for exercising a right. You may also complain to your local data-protection or consumer-protection authority.
EEA and UK users may have the GDPR or UK GDPR rights listed above and the right to lodge a complaint with the authority where they live, work, or believe an infringement occurred. California and other eligible U.S. residents may request the applicable categories, sources, purposes, recipients, specific pieces, correction, deletion, and portability, and use an authorized agent where law permits. Anovel has not sold or shared personal information for cross-context behavioral advertising in the preceding 12 months. [TODO: counsel must confirm which jurisdiction-specific statutes and appeal processes apply to the Operator at launch.]
Send a request to [TODO: insert the privacy-request email or web form]. Describe the right you wish to exercise and the account email or browser-only context involved. We may request proportionate information to verify identity and authority, but will not ask for more than reasonably necessary. We will respond within the period required by applicable law and explain any refusal and available appeal. For data held only in your browser, we may not possess or be able to identify it; the browser controls described above remain the direct way to manage it.
13. Children
The Service is not directed to anyone under 21, and a person under 21 must not create an account or use the Service. We do not knowingly collect personal information directly from a person under 21. If we learn that we have done so, we will disable the account and take appropriate deletion steps. Contact [TODO: insert the privacy email] if you believe this has occurred.
An adult may include a child's age or other details while planning a family trip. The adult is responsible for having authority to provide that information, minimizing it, avoiding unnecessary sensitive details, and selecting safe sharing settings. Anovel does not use a child's information for advertising or profiling.
14. International transfers
Anovel and its providers may process information in countries other than the one where you live. Those countries can have different privacy laws. [TODO: identify the Operator's establishment, production database, object storage, email, AI, hosting, support, and backup locations before launch.]
Where law requires a transfer mechanism, the Operator will use an adequacy decision, approved standard contractual clauses and any required supplement, or another lawful safeguard, and will assess supplementary measures where required. You may request information about applicable safeguards through the privacy contact.
15. Changes, complaints, and contact
We will review this Policy whenever a feature, SDK, provider, data category, purpose, sharing path, or retention practice changes. The date at the top will change when the Policy changes. If a change materially affects how we use personal information, we will give reasonable advance notice through the Service or account email unless urgent legal or security circumstances require faster action. We will request consent again where required; continued use will not be treated as consent when law requires an affirmative choice.
Questions, complaints, and rights requests may be sent to [TODO: insert the Operator's legal name, privacy email, support email, and postal address]. [TODO: determine whether an EEA or UK representative or Data Protection Officer is required and publish their contact details if appointed.] You may contact an applicable supervisory authority at any time, although we welcome the opportunity to address a concern directly.
The Terms of Service govern use of Anovel. If this Policy and the Terms describe personal-information practices differently, this Policy controls for those practices unless applicable law requires otherwise.
