Last updated November 20, 2026 · Mariwave, LLC
1. Who is responsible for your data
Mariwave, LLC, a Delaware limited liability company, is the controller of the personal data described here.
The pre-release is offered by invitation in the European Union, the rest of the European Economic Area and the United Kingdom as it is everywhere else, so the GDPR and the UK GDPR may apply to what we do with your data. Mariwave, LLC has no establishment in the EU or the UK, and has not appointed a representative there under Article 27 of the GDPR or of the UK GDPR. Write to us directly at the addresses above; the EU address is our own privacy mailbox, not a representative's.
This policy covers mariwave.com, web.mariwave.com, what the Mariwave Mac app sends to them, the Mariwave Earth app for iPhone and iPad, and Mariwave's templates, the globe on mariwave.com among them (section 4). It is the one privacy policy for all of them.
2. What we collect, why, and our legal basis
A request to join. The email address you type into the request form or give with the macOS app prerelease ticked after signing in on mariwave.com, or the address you prove at sign-in if you are not yet admitted, with the name and note you add, the date, the decision and the administrator who made it. We use it to review and answer your request. Legal basis: steps you ask us to take before a contract (Article 6(1)(b)).
Your account and sign-in. You sign in with Apple. Apple gives us an identifier for you, your email address (or, if you choose Hide My Email, a private relay address at privaterelay.appleid.com that forwards to you), and your name if you choose to share it the first time; we keep your email address, your display name if you have one, that identifier and your sign-in times. If your organisation has an Enterprise agreement with us, you may instead sign in through your organisation's own identity provider, which gives us the same kinds of identifier and email address. We use them to create your account and sign you in. We keep no password. Legal basis: performing our contract with you (Article 6(1)(b)).
A mariwave.com account. You can also sign in on mariwave.com with Apple, in a browser or in the Mariwave Earth app, where Apple asks you on your device and the app passes Apple's answer to mariwave.com; it is the same account either way. That account is for mariwave.com only: it is not a web.mariwave.com account, and it does not sign you in to the Mac app. For it we keep Apple's identifier for you, so you sign in to the same account each time; the email address Apple gives us (yours, or the private relay address at privaterelay.appleid.com if you choose Hide My Email), to which we send nothing unless you give it to us to keep you posted; your name, only if you choose to share it with Apple the first time; and when the account was made and when you last signed in. After your first sign-in we ask once whether to keep you posted: if you say yes we keep the address you give us to keep you posted and when you answered, and we send that address one welcome email and keep when we sent it, so it is sent only once; if you choose Not now we keep only when you answered, so we do not ask again. We write to that address only with news of Mariwave and its releases, and stop when you ask, when you use the link to stop in any of those emails (it needs no sign-in and clears that address), or when you delete the account. If you also tick the macOS app prerelease, that address is filed as a request to join, as the request form files it. Before the account is made we check the address against the banned addresses on the access list. A session on mariwave.com is kept only as a hash of its token, for 30 days. We do not sell this data, show advertising with it or use it for analytics. You can delete the account at any time from its window on mariwave.com, and the account, its sessions and the links you sent are erased at once. Legal basis: performing our contract with you (Article 6(1)(b)); for keeping you posted, your consent (Article 6(1)(a)).
Short links to a view. When you make a short link to a view, we keep its picture, the view (the place on the map, the zoom, the time and the layers) and the nearest city's name with your account, until you delete the link or your account. Anyone with the link can see them. Legal basis: performing our contract with you (Article 6(1)(b)).
Short links made without an account. When you make a short link to a view without signing in, we keep only the view (the place on the map, the zoom, the time and the layers), the nearest city's name and when you made it: no picture and nothing about you. Anyone with the link can see them, and we keep them for as long as the link may be opened. Legal basis: our legitimate interest in letting you share a view (Article 6(1)(f)).
How often Share is used. We count how many times Share is used: a total, nothing about you or what you shared. Legal basis: our legitimate interest in knowing how the site is used (Article 6(1)(f)).
Mariwave Earth subscriptions. Apple sells the Mariwave Earth app's subscription and processes the payment under its own terms; we receive no payment details, and the app checks whether your subscription is active on your device with Apple, without sending it to us. Apple gives us only the sales and subscription reports it gives every developer, which do not identify you to us.
Links you send from a mariwave.com account. For each link you create to a post on mariwave.com's blog we keep the post it points to, your note (at most 280 characters), the name it shows, when you made it, whether you revoked it, and how many times it was opened: a count, and nothing about who opened it, when or from where. Anyone with the link sees the post, your note and that name. A revoked link stops working at once. Legal basis: performing our contract with you (Article 6(1)(b)).
Sessions. A browser session is stored as a hash of its token, with its times. A Mac session is stored the same way, with the Mac's label and when it last renewed. We use them to keep you signed in and to let you and an administrator end a session. Legal basis: performing our contract with you, and our legitimate interest in keeping accounts secure (Article 6(1)(f)).
The access list. Which addresses may sign in, who changed that and when, and for a banned address the reason. We use it to run a closed pre-release safely. Legal basis: our legitimate interest in deciding who uses a pre-release product and in preventing abuse.
Local safety warnings. The Mac app checks text-bearing requests to Mariwave's own GPU with a local classifier. For a blocked policy request, it reports only a random submission identifier under your authenticated account; our server records the account address, identifier and time, and counts distinct reports. It does not receive the prompt, output, flagged category or classifier score for moderation, and it does not send that content to Groq or another moderation provider. The report can be omitted or fabricated by a modified client, so it is not conclusive evidence about the content. Our legitimate interest is protecting the service and other people from misuse (Article 6(1)(f)).
Legal acceptance. Which version of the Terms of Service and Confidentiality Agreement you accepted, its digest and the time. Legal basis: performing our contract with you, and our legitimate interest in being able to prove what was accepted.
Billing. Stripe collects your payment details on its own pages; we do not receive card numbers. We keep your Stripe customer identifier, your subscription and its status, trial codes, complimentary marks, and whether a payment was refunded or disputed. Legal basis: performing our contract with you, and our legal obligations for accounting records (Article 6(1)(c)).
Referrals. If you ask to join through a member's invite link, we keep your address, the member whose link it was, when you asked and when your first payment went through; for you and for that member, the months at no charge it earned and whether each was applied to a subscription, as a one-time discount at Stripe. The member sees how many people they invited and how many subscribed, never who; an administrator sees both. Legal basis: performing our contract with you, which includes the referral offer you accepted (Article 6(1)(b)).
Metered usage. For each model request or job on Mariwave's engine: the account, the service or model, the tokens or GPU seconds used, the price and the time. It holds counts, not your words. Legal basis: performing our contract with you.
Content you send to models on Mariwave's engine. Chat requests, music prompts and audio to transcribe pass through our Worker to Modal, which runs the models, and the answer comes back the same way. Our Worker does not store this content. The Terms of Service ask you to use only sample, test or non-sensitive data during the pre-release. Legal basis: performing our contract with you.
Your held OpenRouter key, only if you turn it on. You can let web.mariwave.com hold your own OpenRouter key so that your cloud machine keeps working while neither your Mac nor your signed-in iPhone is connected. It is off until you turn it on. While it is on, we store the key encrypted (AES-256-GCM under a key only our Worker holds, bound to your account), use it only to send your cloud machine's model requests to OpenRouter in that case, never place it in the machine and never log it. Those requests, and their answers, pass through our Worker to OpenRouter under OpenRouter's terms and your OpenRouter account's settings, and our Worker does not store them. Settings shows whether it is on and since when, never the key. Legal basis: performing our contract with you, at your request (Article 6(1)(b)).
Support reports. If you press the Mac app's button to report a first-run failure, we receive the app, macOS and hardware versions, the failing step, the error and log text, your note and your reply address if you give them, and a hash of your network address. Email addresses, tokens and home folder names in the error and log text are removed before storing. The report is emailed to our support address. Legal basis: our legitimate interest in fixing faults and answering you.
Email. We send letters about your request, account, trial, subscription and policy changes, through Cloudflare Email Service. Legal basis: performing our contract with you, and our legal obligation to inform you where one applies.
Product analytics. On web.mariwave.com and eyzaguirre.co we use PostHog to learn how people use the sites. A banner asks you first. On mariwave.com, and in the Mariwave Earth app, which shows mariwave.com, we use PostHog only without cookies: no banner and no analytics cookie. There we count visits and see which pages, windows and buttons are used, which site or link brought you, and what you do on the globe: the places you choose, the layers and sound you turn on or off, what you share, and each place the tour moves to. With each of these we record the country, region and city you visit from, as our host Cloudflare reads them from your connection; neither we nor PostHog keep your network address. PostHog tells visits apart with a hash of your network address and browser that changes every day, so it keeps no identifier of you and does not link visits to your account. Your browser's Do Not Track setting turns it off for you there. Legal basis: our legitimate interest in knowing how the site is used (Article 6(1)(f)). We do not track you across other companies' apps or sites.
- If you accept, PostHog sets its cookies and records the pages you view, what you click and, if we turn them on, recordings of your session. On web.mariwave.com it links them to your account's identifier, never your email address. Legal basis: your consent (Article 6(1)(a)).
- If you decline, or have not chosen, we still count visits, without cookies. PostHog tells visits apart with a hash of your network address and browser that changes every day, and keeps no identifier of you. Your browser keeps only your choice, if you made one. Legal basis: our legitimate interest in knowing how the sites are used (Article 6(1)(f)).
Your network address and browser reach PostHog through our own servers; PostHog uses them for that daily hash and does not keep the address. On every site we attach the country, region and city Cloudflare reads from your connection to what we count, and never the address itself. You can change your choice at any time with "Cookie settings" at the foot of every page on those sites. We do not use analytics for advertising, and we do not sell it.
Security and abuse limits. Your network address is used at the edge to limit repeated attempts. We do not store it, apart from the hash on a support report. Cloudflare keeps request logs for the Worker. Administrators' actions on accounts are recorded. Legal basis: our legitimate interest in keeping the service available and secure.
We do not sell your data, show advertising, or use your content to train models.
3. Data we get from others
- Apple, through Sign in with Apple, confirms your email address (or gives a private relay address) and the identifier above; your organisation's identity provider does so instead if you sign in through it.
- Stripe tells us about your customer record, subscription and payments.
- An administrator may add your address to the access list.
- Anyone can type an address into the public request form. An address typed there stays unproven until its owner signs in, and we write nothing to it unless an administrator admits it.
4. The Mac app, the globe and templates
The Mac app runs on your Mac. Your provider keys stay in your Mac's Keychain and are never sent to Mariwave. The one exception is the OpenRouter key you choose to let us hold for your cloud machine (section 2); our Worker stores no other credential of yours. Chats on a local model stay on your Mac. A chat on a cloud model you connect with your own key goes to that provider under its terms, not through Mariwave.
Mariwave may check text sent to its own hosted models for harmful content. If you turn the check on in the Mac app, it runs locally before the submission leaves the Mac. This check is distinct from the ordinary processing of an allowed request by Mariwave's Worker and Modal described in section 2. Upload-only jobs are not screened by this text check.
The atlas on mariwave.com is the Mariwave atlas app running in your browser: the globe draws on your own computer's graphics processor, and nothing you do in it is sent to us. Until you press OK on the welcome window, it asks no one for data. After you press OK, your browser fetches public data directly from these sources, each of which receives your IP address and the place or area you asked about: Open-Meteo (weather and place search), NASA (satellite imagery), CelesTrak and The Space Devs (orbits and launches), the US Geological Survey (earthquakes), RainViewer (radar), NOAA (storms and forecast maps), OpenStreetMap (map tiles), Wikipedia (articles and pictures near a place), the publishers whose pictures and pages you open, and OpenRouter only if you connect it. News feeds, flights, ship traffic, cloud imagery, forecast models and service status come through Mariwave's servers on Cloudflare (section 5), which fetch and may cache them without passing on anything about you. What you save in the atlas (places, briefings, feeds, the time you pressed OK, where you left each window, and an OpenRouter key if you connect one) stays in your browser's storage, and none of it is sent to us. If you press Locate, your browser or device gives the atlas your position to center the map, only after you allow it; it is used on your device and not stored by us.
The Mariwave Earth app shows mariwave.com and does what this section says of the atlas; what you save stays in the app's own web storage on your device, and deleting the app deletes it. The app itself sends us nothing else: it has no advertising, no tracking across other companies' apps or sites, and no analytics of its own.
Templates you run yourself, on your Mac or your own deployment, fetch the public sources you turn on from your own browser or machine, under those sources' terms, and keep what you save on your device or in your own database. They send Mariwave nothing about it.
5. Who receives your data
Subprocessors. These companies process personal data for us. Each acts under the terms linked to its name. We list every new one here, and change the date at the top, before it receives any data.
- Cloudflare, Inc. (United States; its network worldwide). Hosts mariwave.com and web.mariwave.com, our database and file storage, the sign-in, and email routing and sending. Data: everything our Worker stores (section 2), sign-in identity, letters to you, request logs.
- Stripe, Inc. (United States). Payments, subscriptions and tax. Data: your email address, payment details on its own pages, your subscription and invoices.
- Modal Labs, Inc. (United States). Runs the models on Mariwave's engine and your cloud machine. Data: what you send to those models and what they answer, and your account identifier.
- OpenRouter, Inc. (United States; trust center). Only if you turn on the held key: your cloud machine's model requests, sent with your own key while none of your devices is connected. Data: those requests and their answers, under your own OpenRouter account.
- GitHub, Inc. (United States). Access tokens the Mac app asks for. Data: the repository and the installation the token is for.
- PostHog, Inc. (held in its EU cloud, Frankfurt, Germany). Product analytics on web.mariwave.com, eyzaguirre.co and mariwave.com. Data: as section 2 describes, with your consent or without cookies.
- Google LLC (United States). Hosts the mailbox that receives support reports and mail to us. Data: those reports and letters.
- Apple Inc. (United States). Delivers notifications to your paired iPhone, and checks Free's once-per-Mac allowance through DeviceCheck. Data: your iPhone's push token and the notification, and two bits Apple keeps for your Mac.
Others who may receive your data.
- Apple, through Sign in with Apple, confirms your address under Apple's own terms, and so does your organisation's identity provider if you sign in through it. Apple also sells and bills the Mariwave Earth app's subscription, as the seller, under its own privacy policy.
- Mariwave's administrators, who decide requests and manage accounts.
- Authorities, where the law requires it.
6. International transfers
Mariwave, LLC is in the United States, and Cloudflare, Stripe, Modal, GitHub, OpenRouter, Google and Apple are based there. Modal's model endpoints we use are in the United States. Your data is processed there and wherever those providers operate. PostHog, Inc. is based in the United States too, but our analytics are held in its EU cloud, in Frankfurt.
When your data comes from the European Economic Area or the United Kingdom, its transfer to the United States rests on the EU-US Data Privacy Framework (for the UK, its UK Extension) where the recipient is certified under it, and otherwise on the European Commission's standard contractual clauses (for the UK, with the UK's International Data Transfer Addendum), as each provider's terms linked in section 5 set out. Cloudflare and Stripe rely on the Data Privacy Framework and on standard contractual clauses. Modal, GitHub, Google, PostHog and Apple act under the terms linked in section 5. OpenRouter receives your cloud machine's requests only under your own OpenRouter account and its terms. Write to us for a copy of what applies.
We set no fixed region for our Cloudflare database and storage, so Cloudflare chooses where they are held.
7. Cookies and similar storage
The service needs only the cookies below. They are first-party and cannot be read by page scripts. We use no advertising or cross-site tracking.
- __Host-mari_session: keeps you signed in on one site, for up to 24 hours.
- __Host-mari_apple_state, or __Host-mari_sso_state when you sign in through your organisation: protects a sign-in in progress, for up to 1 hour.
- __Host-mari_request: lets your browser fill in your own waiting request, for 30 minutes.
- __Host-mariwave_site: keeps you signed in to your mariwave.com account, for up to 30 days.
- __Host-mariwave_site_start: ties a mariwave.com sign-in in progress to your browser, for up to 15 minutes.
If you press the appearance button, your light or dark choice is saved in your browser's local storage under mari-appearance. The atlas on mariwave.com keeps what you save in it there too (section 4). None of it is sent to us.
Analytics, only with your consent. If you accept the banner, PostHog sets its own first-party cookies and local storage, under names that contain ph_, to recognize your browser on later visits. If you decline, PostHog sets no cookie and keeps only your choice in your browser's local storage; if you have not chosen, it stores nothing. "Cookie settings" at the foot of every page on web.mariwave.com and eyzaguirre.co shows the banner again, so you can withdraw your consent or give it at any time. Once you withdraw it, PostHog's cookies are no longer used and visits are counted without them.
Apple's sign-in page, your organisation's sign-in page and Stripe's payment pages set their own cookies on their own sites, under their own policies.
8. Data retention
- Requests to join: one year from the request, or sooner if you ask.
- Referrals: one year from the request when the invited person never paid; otherwise until either person's account is deleted, with the months at no charge it earned.
- Your account and what belongs to it: until the account is deleted. This includes sign-in identifiers and legal acceptances.
- Model usage records: 761 days, or until the account is deleted if that is sooner.
- Held OpenRouter key: until you turn it off, sign out of any Mac or the web, lose admission, or delete your account, whichever comes first; then it is deleted at once.
- Sign-in in progress: deleted within a day of its short expiry.
- Browser sessions: 24 hours, then deleted within a day.
- Your mariwave.com account: until you delete it. Its sessions: 30 days, then deleted within a day.
- Links you send: until you delete your account, revoked or not.
- Mac sessions: 90 days after the last renewal.
- Song and transcription usage records: 761 days, so that the current and last full year can be answered for.
- Stripe event records: 90 days.
- Support reports: 90 days in our database. The emailed copy stays in the support mailbox for one year.
- Billing records at Stripe: Stripe keeps your customer record and invoices after your account is deleted, for as long as Stripe's own policy and the record-keeping laws that apply to it require.
- Content sent to Modal: Modal publishes no fixed period for prompts, audio and results.
- Cloudflare request logs: up to 7 days.
- Local safety warning events: active warnings remain until an administrator clears them or the account is deleted. After an administrator clears them, their identifiers and timestamps remain for up to 761 days as an audit trail. Deleting the account removes its warning events.
- Analytics at PostHog: PostHog keeps events for the retention period set in our PostHog project, and then deletes them. You can ask us to delete the events linked to your account sooner.
- Records kept after deletion: the history of access list changes, the record of administrators' actions and the record that a policy notice was sent stay for 761 days, to show what was done. A ban stays until it is lifted, to keep a banned address out.
9. Your rights
If the GDPR or the UK GDPR applies to you, you have the right to:
- access your data and get a copy (Article 15);
- correct data that is wrong (Article 16);
- erase your data (Article 17);
- restrict how we process it (Article 18);
- receive data you gave us in a portable format, or have it sent to another controller (Article 20);
- object to processing based on our legitimate interests (Article 21);
- complain to a supervisory authority, in particular where you live, work, or where you think the law was broken (Article 77). The EU's authorities are listed at edpb.europa.eu. In the UK that is the Information Commissioner's Office, ico.org.uk.
To use a right, write to privacy@mariwave.com. We answer within one month, and it costs nothing. We may ask you to prove the address is yours.
To delete your account, write to that address and an administrator carries it out. It removes your account and what belongs to it. A live subscription is cancelled first and unbilled usage is billed first. We keep what we must keep for accounting or to defend a legal claim. Section 8 lists what stays.
A mariwave.com account, in a browser or in the Mariwave Earth app, is deleted at once from its own window, with no need to write to us. Deleting it does not cancel a Mariwave Earth subscription, which belongs to your Apple Account: cancel it in your Apple Account's subscription settings.
We rely on your consent only for analytics with cookies (section 7) and for keeping you posted from a mariwave.com account (section 2). You may withdraw it at any time, through "Cookie settings" for analytics and by writing to us or deleting the account for the updates, without affecting what was done before.
California residents have the rights set out in section 3.2 of the Terms of Service. We do not sell or share personal information.
10. Do you have to give us your data?
No law requires it. An email address is needed to answer a request, and an account needs a proven address and acceptance of the Terms of Service: without them we cannot admit you or give you an account. A name, a note and a support report are optional. A paid plan needs payment details at Stripe.
11. Automated decisions
The Mac's local classifier can refuse a text request to Mariwave's own GPU. Four distinct blocked submissions reported by that Mac automatically suspend the account across Mariwave, including access from the web, without a person reviewing the requests first. The report contains no request content. Outages, malformed classifier decisions and retries of the same reported submission are not counted. The classifier and client can make mistakes; a modified client may omit or fabricate reports. To contest a warning or suspension, ask for human review at legal@mariwave.com. An administrator can restore access and clear active warnings without deleting your account, while keeping the limited audit history described in section 8. A person still decides every request to join.
Fixed rules do act without a person: limits on repeated attempts, the caps on waiting requests, a stop on metered work when prepaid credit runs out, and a stop on metered work while a payment stands refunded or disputed. Lifting a payment stop is done by a person.
12. Security
Connections use TLS. Session tokens are stored only as hashes, and session cookies are Secure and HttpOnly. Forms that change an account are checked to come from our own site. Access to accounts by administrators is limited to named people and recorded.
No system is perfectly secure. Report a vulnerability to security@mariwave.com.
13. Age
You must be at least 18 to use Mariwave (Terms of Service, section 1.3), and at least 13 to use Mariwave Earth (Terms of Service, section 6.1). We do not knowingly collect information from children under 13. If you think we hold data about a child under 13, or about someone under 18 in Mariwave's application or cloud accounts, write to us and we will delete it.
14. Changes to this policy
The date above moves with every change. We tell you by email before a material change takes effect.
15. Contact
Privacy questions and requests: privacy@mariwave.com