Privacy Policy
Last updated: 8 October 2026
Audiala Solutions SA ("Audiala", "we", "us"), Morges, Switzerland (UID CHE-248.062.756), runs the Audiala apps for iOS and Android, the website audiala.com, the trip planner at app.audiala.com and the Audiala connector for AI assistants. We are the controller of your personal data. This policy explains what we collect, why, who receives it, how long we keep it and what your rights are. The Swiss Federal Act on Data Protection (FADP) applies, and for people in the European Union or European Economic Area the General Data Protection Regulation (GDPR) applies too.
Questions or requests: [email protected].
1. What we collect
Information you give us
- Account: email address, display name, profile photo (optional), home country and city (optional), preferred language, and the identifier from Sign in with Apple or Google if you use them. On iOS the app can create an anonymous account before you sign in, so your chats and downloads are kept.
- Trips and plans you create, places you save and the people you invite to a trip.
- Chats with Audiala: your messages, Audiala's replies and the places and trips they relate to.
- Voice input: when you tap the microphone, your voice is sent to a speech-to-text provider (section 4) and turned into text. We do not keep the recording.
- Travel Profile: facts about how you travel, for example "vegetarian" or "travelling with children". Facts you tell Audiala in a chat can be saved directly; facts Audiala suggests from your chats stay pending until you confirm them. Diet, health and mobility details are saved only when you state them clearly yourself or confirm a suggestion. Each fact can record the situation it was learned in (city, trip, season, travel party, type of weather, time of day), never your GPS position.
- Purchases: in the apps, payments are handled by Apple or Google; on the website, by Stripe. We never see your card number. We receive your purchase and subscription status and, for web payments, your email address and the payment record.
- Messages to us: support requests, feedback, partnership or guest-post requests, and the details you give if you join the ambassador programme (including identity, tax and payout information).
- Email sign-ups on the website (trip briefs, newsletter), confirmed by a link in a confirmation email.
Information collected automatically
- App usage data: which screens you open, guides you play, searches, purchases, your device model, operating system and app version, an analytics identifier, and your IP address, from which our analytics provider derives an approximate location (city level). This data is linked to a random account ID. New analytics events and profiles carry no name or email address. Events recorded before October 2026 may contain your email address; we keep them until the end of the analytics retention period in section 9, or until you delete your account. See section 6 for how to turn usage data off.
- Crash reports: device and app state at the time of a crash. In app versions released after 7 October 2026, crash reports carry no account identifier and are sent only while usage data is on. Earlier versions send crash reports even when usage data is off, and the earlier iOS versions also attach your account ID, the domain of your email address and the city and place you were viewing.
- Location, only if you allow it on your device:
- to show places and stories around you and to play nearby stories during a walk (this happens on your device);
- with your chat messages: when your device has a recent position (less than 10 minutes old), it is sent with your message so Audiala can answer about where you are. It passes through our servers to the AI providers in section 4;
- to get weather, nearby places and walking directions: coordinates are sent to the weather and map providers in section 4;
- trip tracking, only if you turn it on: the route you walk is stored with your trip.
- Install attribution: when you install the app from one of our links, we match the install to the page you came from using a salted hash of your IP address and your device type, kept for at most 2 hours. On iOS the app checks once, on first launch, whether you copied an Audiala link; on Android we read the Google Play install referrer. Our subscription provider also receives identifiers used to attribute installs to our own advertising (details in section 6).
- Push notifications: a push token from Apple or Google, if you allow notifications.
- Consent and deletion records: when you record a privacy choice or request account deletion, we store it with the date, your IP address and your browser or device type.
- Website and trip planner: see section 6.
- Server logs: IP address, browser and requested address, used for security, rate limiting and debugging (section 9).
We do not sell your personal data.
2. Why we use your data, and on what legal basis
| Purpose | Data | Legal basis |
|---|---|---|
| Provide the apps, website, chat, trip planning, downloads and sync across your devices | account, trips, chats, Travel Profile, location when you use location features | contract |
| Answer your chat messages with AI | your message and its context: city, trip, Travel Profile, recent position if allowed | contract |
| Remember sensitive details in your Travel Profile (diet, health, mobility) | the facts you state or confirm | your explicit consent, which you can withdraw by deleting the fact or resetting the profile |
| Improve the quality of answers: automated and human review of a sample of real conversations | chats | legitimate interest (a reliable service); you can object (section 8) |
| Subscriptions and payments | purchase records | contract; legal obligations (accounting) |
| Product analytics and crash diagnostics | usage data, device data, crash reports | legitimate interest (improving the apps); you can turn it off (section 6) |
| Measure our own advertising and match installs to the page you came from | install attribution data, store and device identifiers, app events sent to Meta and, on Android, Google Ads conversion events (section 6) | legitimate interest; the events to Meta and Google follow the usage-data switch |
| Emails you asked for (trip briefs, pre-trip stories, newsletter) | email address, trip date and destination | consent |
| Service emails (sign-in codes, trip invitations, receipts) | email address | contract |
| Security, abuse prevention and rate limiting | IP address, logs | legitimate interest |
| Ambassador payouts and tax | identity, tax and payout details | contract; legal obligations |
| Website analytics (PostHog, Google Analytics) | page views, browser data | consent (section 6) |
3. Where your data is stored
Our main database, file storage and email service run in the EU: Frankfurt, Germany, and Stockholm, Sweden. Some of our database provider's functions run in the data centre nearest to you. Our own servers, which run the chat service, the trip planner and their logs, are in Switzerland. Some providers in section 4 process data in the United States or other countries; see section 5.
4. Who receives your data
Service providers that process data for us
| Provider | What for | Data | Location |
|---|---|---|---|
| Supabase | database, sign-in, file storage | account and app data | EU (Frankfurt); some functions run near you |
| Amazon Web Services | email sending (SES), file storage (S3) | email address and email content; content files | EU |
| Cloudflare | network, security, hosting of the AI-assistant connector, relays analytics events to PostHog | IP address, request data | worldwide network |
| OpenAI | AI chat (main chat model, called directly) | chat messages and their context, including your recent position if allowed | United States |
| OpenRouter, and through it the model providers OpenAI, Google, Anthropic and Cerebras and the cloud platforms that host their models (Microsoft Azure, Amazon Web Services, Google Cloud) | AI chat, trip planning, quality review, Travel Profile matching | chat messages and their context, Travel Profile facts | United States |
| TypeSafe | understanding requests and checking answers and Travel Profile facts | your latest messages (shortened), Travel Profile statements | not confirmed by the provider; may be outside Switzerland and the EU |
| Deepgram | speech-to-text | voice recordings | United States |
| PostHog | product analytics | usage data, device data, IP address | EU (Frankfurt) |
| Google Firebase | crash reports, app measurement, Google Ads conversion measurement (Android) | crash and device data, an app-instance ID, app events | United States |
| Google Analytics | website and trip-planner analytics | page views, browser data | United States |
| RevenueCat | subscriptions, install attribution | account ID, purchases, store and device identifiers, Meta and Firebase app IDs | United States |
| Mapbox | maps and place search in the trip planner | map area, searches, map-load and usage events | United States |
| Google Workspace | our email (support and privacy requests) | your messages | Google data centres (worldwide) |
Other recipients that use the data under their own terms and privacy policies
- Meta (Facebook SDK in the apps): while usage data is on, the apps send app events, including automatic ones such as app launches, with Meta's anonymous app ID (not your advertising ID). Meta uses this data to measure our ads and, under its own terms, for its own purposes.
- Google may also use some Google Analytics and Firebase data for its own services, as its terms allow.
- Apple and Google (App Store, Google Play, Sign in with Apple or Google, push notifications, Apple Maps and WeatherKit): purchases, sign-in, push tokens, map area and coordinates.
- Google Maps Platform: map area, nearby place searches and walking directions, using coordinates without any account information.
- Stripe: web payments. Stripe also acts on its own account for fraud prevention and legal duties.
- Weather services: MET Norway (Norway), Tomorrow.io (United States), Google, and, in app versions that fetch weather directly, Open-Meteo (iOS) and WeatherAPI.com (Android). They receive coordinates; services called directly by the app also see your IP address.
- Content served directly to your browser or app: map tiles from OpenFreeMap and CARTO; photos and facts from Pexels, Unsplash, Wikimedia Commons, Wikipedia and Wikidata; images from Tiqets, Tripadvisor and GetYourGuide; YouTube (Google) when you play a video. These services see your IP address and browser or device information.
- Ticket partners (GetYourGuide, Viator, Tiqets): if you follow a ticket link, the partner learns that the visit came from Audiala. We do not send your account details.
- PayPal and other payout providers: ambassador payouts.
- Authorities, where the law requires it.
Service providers that process data for us may use it only to provide their service to us, except where this section says otherwise. For AI:
- requests through OpenRouter are sent with zero data retention and with the providers' data collection denied, so the model providers are not allowed to store them or train on them;
- OpenAI, which we also call directly, does not use our API data to train its models and may keep it for up to 30 days to monitor abuse;
- Deepgram is told not to use your recordings to improve its models.
5. International transfers
Some recipients are in countries that Switzerland or the EU do not consider to have adequate data protection, such as the United States. For these transfers we rely on standard contractual clauses (with Swiss adaptations), or on the EU-US or Swiss-US Data Privacy Framework where the recipient is certified. You can ask us for more information about these safeguards.
6. Your choices: analytics, cookies and the website
Apps. Usage analytics are on by default. You can turn them off at any time in the app's privacy settings: "Share usage data" on iOS; "Share usage analytics" on Android (called "Share anonymous analytics" in earlier versions). If you turned usage data off on iOS before June 2026, an app update may have switched it back on, so please check the setting.
- When usage data is off, the app stops sending usage events to PostHog and app events to Meta, and the Android app stops sending Google Ads conversion events. App versions released after 7 October 2026 also stop sending crash reports. Basic app measurement by the Firebase SDK may continue.
- Identifiers for install attribution: on iOS, the identifier for vendor (IDFV) and the Apple Search Ads attribution token are sent to our subscription provider whether or not usage data is on. On Android, your device's advertising ID (if your device settings allow it) and Meta's app ID are sent only while usage data is on; the Firebase app-instance ID is always sent.
- The apps do not use cookies.
Website (audiala.com). Until you make a choice in the cookie banner, we set no cookies and load no analytics tools. Some photos on our pages do load before you choose: they come directly from other services (Pexels, Unsplash, Wikimedia Commons, Tiqets, Tripadvisor, GetYourGuide), and these image hosts see your IP address and browser details when your browser loads them.
With your consent to analytics we load PostHog (EU) and Google Analytics; Google's ad-personalisation and ad-data signals stay off. If you also accept marketing, Google Analytics may set advertising cookies. Videos (YouTube) and interactive maps (OpenFreeMap) load only when you tap them or if you have accepted the marketing category. Fonts are served from our own servers.
Your choice is stored in your browser as audiala.consent.v1 and in the audiala_consent cookie (up to 13 months). You can change it at any time with Cookie settings in the footer.
Trip planner (app.audiala.com). The trip planner asks for the same choice and works like the website:
- Google Analytics loads only after you accept analytics. Google's ad-personalisation and ad-data signals and Google signals stay off. If you also accept marketing, Google Analytics may set advertising cookies.
- Maps come from Mapbox and CARTO. Mapbox performance telemetry is off; Mapbox still receives map-load and usage events that it uses for billing, with a random identifier it stores in your browser.
- The trip planner stores your sign-in session and your language.
Email. Every newsletter or trip-brief email has an unsubscribe link.
Location. You can turn off location access in your phone's settings. Chat, weather and nearby features then use the city you choose instead.
7. Audiala in AI assistants (ChatGPT, Claude and others)
You can use Audiala inside AI assistants through our connector. No Audiala account is needed.
What we receive. Only what the assistant sends to use an Audiala tool, for example a city, a place or a language. We do not receive your conversation or your identity.
What we log. For each request we record which Audiala tool was used, the names (not the contents) of its parameters, whether it succeeded, the approximate country, the assistant's client name and user agent, and a technical request identifier. When a request fails, the error message we record may repeat a value you sent. We use this to measure usage and improve the service. Your IP address is used by our hosting provider (Cloudflare) to prevent abuse through rate limiting and is not stored with these usage records.
Contacting our team. If you ask the assistant to contact Audiala, it sends us the email address you provide and, if you choose, your name and organisation, so that we can reply. We store this request together with your IP address for up to 12 months, to prevent spam and to keep a record of your request, and we use it only to respond to you. You can ask us to delete it at any time.
Links to Audiala. Links opened from an Audiala card carry campaign tags (for example utm_source=chatgpt) so we know the visit came from an AI assistant. They do not identify you.
The assistant provider. The assistant's own handling of your conversation is governed by its provider's privacy policy (for example OpenAI or Anthropic), not this one.
8. Your rights
You have the right to access your data and receive a copy, to correct it, to have it deleted, to restrict or object to its processing, to receive it in a portable format, and to withdraw your consent at any time.
- Export your data: in the app ("Export My Data" in the Data & Privacy settings on iOS, "Export my data" under Profile → Account on Android), on app.audiala.com/account, or by email. The export includes your account, chats, Travel Profile and trips.
- Delete your account: on iOS with Delete Account on the Data & Privacy screen in Settings; on Android in Profile → Account → Delete account; on app.audiala.com/account; or by emailing [email protected]. Your account is then scheduled for permanent deletion after 30 days; signing in again during those 30 days cancels the deletion. When the deletion is carried out, we also delete your data held by our analytics provider (PostHog), our subscription provider (RevenueCat) and our payment provider (Stripe). Records we must keep by law are kept for the legal period. Copies in crash reports and server logs are deleted at the end of the periods in section 9.
- Travel Profile: edit or delete any fact, pause personalisation, or reset the whole profile from the Travel Profile screen.
- Anything else, including objecting to the review of your conversations: write to [email protected]. We reply within 30 days.
You can also complain to the Swiss Federal Data Protection and Information Commissioner (FDPIC) or to the data protection authority where you live or work.
9. How long we keep data
| Data | How long |
|---|---|
| Account, trips, saved places, Travel Profile, push tokens, AI usage counters (no message content) | while your account exists; deleted 30 days after you delete your account |
| Chat history | 12 months after the conversation's last message, or sooner if you delete it or your account; chats attached to a trip or guide are kept while that trip exists |
| AI service logs (requests, replies, tool results) | 180 days |
| Examples from real conversations collected to test answer quality | 180 days. A few may be kept longer as test cases, with contact details and account identifiers removed |
| Suggested Travel Profile facts you dismissed or that expired | 12 months |
| Install-matching data | 2 hours |
| App and website analytics events | up to 2 years |
| Crash reports | 90 days |
| Web server access logs | about 5 weeks |
| Other application logs on our servers (they do not contain chat messages) | up to 180 days, unless debugging is temporarily switched on |
| Consent records and closed account-deletion requests | 3 years |
| Ticket and pricing link click logs | 13 months |
| Email sign-ups | until you unsubscribe, then 30 days |
| Contact requests through AI assistants | 12 months |
| Support emails, partnership and guest-post requests | as long as needed to handle your request and any follow-up; the IP address stored with guest-post requests is deleted after 12 months |
| Payment, accounting and ambassador tax records | as long as the law requires (up to 10 years in Switzerland) |
10. Children
Audiala is not intended for children under 16, and we do not knowingly collect their data. If you tell Audiala you travel with children, it may remember their age group to suggest suitable places; you can delete this in your Travel Profile. If you believe a child under 16 has given us personal data, write to [email protected] and we will delete it.
11. Security
Data is encrypted in transit. Our database and storage providers encrypt it at rest. Access to personal data is limited to the people who need it to run the service.
12. Changes to this policy
We update this policy when our practices change and show the date at the top. We announce important changes in the app or on the website.
13. Contact
Audiala Solutions SA, Morges, Switzerland Email: [email protected]