Privacy Policy

This Privacy Policy describes how L&L France SAS, operating under the trade name Webyss ("we", "us", "our"), collects, uses, and protects your personal information when you use the Solane mobile application (the "App") or its web version at app.solane.app (the "web app"). Unless a section says otherwise, what it says about the App applies to the web app too (see §13).

1. Who we are

1.1 Distribution scope

Solane is distributed worldwide via the Apple App Store and Google Play, and as a web app at app.solane.app (§13). For users in the European Economic Area, the United Kingdom, and Switzerland, the data-protection rights described in this policy (GDPR and equivalent laws) apply in full, and L&L France SAS acts as data controller.

2. Information we collect

2.1 Information you provide directly

• Birth data — date, time, and city of birth, used solely to compute your natal chart and forecasts.
• City where you live now (optional) — used only to compute how the sky falls over your current location, which is a different calculation from your birth chart. It is a city name you type, never a GPS position.
• First name (optional) — used to personalise readings.
• Profiling answers — voluntary multiple-choice questions used to tailor how Solane writes to you: what you are drawn to (love, career, growth), your relationship situation, how you describe your gender, and an age range derived from your birth date (for example “25–34”, never your exact date). Every one of these is optional and can be skipped. They are recorded on our own server against a random install identifier, and the gender and age range are never sent to Google. Like the rest of what you told us, they are part of the request when a reading or a reply is written by OpenAI (§4).
• Email address (web app only) — on app.solane.app, once your chart is drawn, you are asked for your email address and cannot continue without it (if our sign-in email cannot be sent, the web app lets you continue for that visit and asks again later): it is how you sign in, with no password. §13.4 says exactly what is kept with it.

2.2 Information collected automatically

• Device identifiers — anonymous device ID for purchase verification (Apple/Google, and RevenueCat on the web app).
• Crash reports and diagnostics — anonymised technical data to fix bugs.
• Notification token — if, and only if, you allow notifications, your device gives us a delivery token. We store it on our own server with a random install identifier so we can send the cosmic alerts you asked for. It carries no name, no birth data and no message content, it is never shared, and turning notifications off in your device settings stops it being used. It is deleted when you use Delete My Account & Data. The web app sends no push notifications; it can email you one line from your chart each day (§13.4).
• App usage events — feature open events used in aggregate to improve the App, tied only to a random install identifier (never your name or birth data). Each event carries its name and properties, that identifier, a session number, the platform (iOS, Android or web), the App's version, the country of your device's language setting, the size of your window (and your text-size setting, if you changed it) and the test group you were placed in; properties can include your sun sign at sign-up and the profiling answers of §2.1. Our server adds the time and a two-letter country derived from your IP address (§13.8). These events are recorded on our own server. In the App they are also sent to Google Firebase Analytics, which we use to understand which parts of the App people reach; the web app sends them to no other company. Firebase receives the event name, its non-personal properties and an app-instance identifier. From September 4, 2026, these events are also shared with Google Ads together with your device advertising identifier, for one purpose only: measuring which of our own adverts led someone to install and use the App. This never happens if your device is set to the European Economic Area, the United Kingdom or Switzerland — there, the advertising identifier is never read at all, because doing so would require asking your consent first, and the App does not ask. We keep ad personalisation switched off, so this data is not used to build an advertising profile of you, to target you, or to follow you into other apps (Firebase privacy). The content of your conversations with Solane is never sent to Firebase.
• Chat conversations with Solane — the questions you type, Solane's replies and the text of your paid readings (forecasts, compatibility, cards, studies) are stored on our own private server, in pseudonymised form, to improve how Solane answers. Before anything leaves your device, the App removes your name, birth date, birth place and city of residence from the text, as best it can on free text; entries are tied only to a random install identifier, kept for at most 90 days, then deleted automatically. Conversations touching health, pregnancy, a death, substances or personal crisis are never stored; a usage event then records that such a topic came up — the kind of topic, never what was said. Using Delete My Account & Data in the App erases your stored chat history immediately. The copies of readings written by OpenAI are kept separately — see §5.

2.3 Information we do not collect

• We do not collect your real-time GPS location. On the web app, our server's policy for the page switches the browser's geolocation off.
• We do not access your contacts, photos, microphone, or camera.
• We do not sell or rent your data to third parties.
• We do not display advertising inside the App or the web app, and we host no third-party advertising or tracking SDK in the App. Outside the EEA, the UK and Switzerland, from October 18, 2026, the web app loads Google's advertising tag and OpenAI's advertising pixel to measure our own adverts (§13.7).
• We do not use your data for personalised advertising. From September 4, 2026 your advertising identifier is used solely to measure the effectiveness of adverts we ourselves buy — never to target you. This never happens if your device is set to the European Economic Area, the United Kingdom or Switzerland — there, the advertising identifier is never read at all, because doing so would require asking your consent first, and the App does not ask. You can reset or delete it at any time in your device settings (Android: Settings › Privacy › Ads · iOS: Settings › Privacy & Security › Tracking).
• We do not track you across other apps or websites.

3. How we use your information

Apart from the notifications you may allow (§2.2), we rely on your consent for nothing in this Policy: where consent would be required — reading an advertising identifier or loading an advertising tag in the European Economic Area, the United Kingdom or Switzerland — we do not do the processing at all.

4. Where your data is processed

• Birth data and forecast generation: our own server (astral.webini.tech).
• Reading and forecast generation: Solane's replies in the chat, and the studies you order, are written by a language model that runs on our own hardware; that is where your data is processed in normal operation. If our own server is unreachable, or too busy to answer (more than fourteen requests in flight), the request falls back to OpenAI so that what you asked for still arrives instead of failing; a study that our own hardware cannot finish in time is rescued the same way. Compatibility readings are written by OpenAI's models, and so are the paid readings of versions of the App older than 1.10.30. In every one of these cases the request is forwarded as it stands. It carries your date, time (if you gave it) and place of birth, your first name, the astrological positions computed from them, the profiling answers you chose to fill in, and what Solane remembers of your conversations. For a chat it also carries the message you typed; for a compatibility reading, the same details for the other person. OpenAI does not use API content to train its models (OpenAI privacy policy). We use no other third-party AI provider. We keep a copy of the readings written by OpenAI — compatibility readings and, for versions of the App older than 1.10.30, paid readings — but not of chat replies (§5).
• Place search: when you type a place — where you were born or where you live — the App and the web app look it up with Open-Meteo's place-search service as you type, straight from your device, and only then. When you create your chart, if Open-Meteo finds nothing they also ask Photon (by komoot), and if Open-Meteo cannot be reached our own server relays that search to the same two services, which then see our server's address rather than yours. The place where the other person in a compatibility reading was born is looked up once, with Open-Meteo, when the reading is prepared. These services receive what you typed and your device's IP address — never your name, your birth date or your identifier. Our server keeps relayed results in memory for 7 days, under the text typed, and does not write the place you typed to its log.
• Purchase processing: handled by Apple App Store and Google Play in the App, and by Stripe through RevenueCat on the web app (§13.5). Their own privacy policies apply.
• Purchase validation: receipts are verified by RevenueCat, our subscription-infrastructure provider. RevenueCat receives an anonymous app user ID and transaction data — never your birth data, name, or readings (RevenueCat privacy policy). On the web app, RevenueCat is contacted each time the web app opens, to read your purchases (§13.5).

5. Data retention

• Birth data: stored on your device. It is sent to our servers (astral.webini.tech) only to compute your chart and forecasts, and held in a temporary cache for at most 24 hours. It is written to a database only if you sign in on the web app, where it is kept with your account until you delete it (§13.4); it also appears in the copies of readings written by OpenAI (below). It is shared only with the place-search and language-model providers named in §4.
• Paid readings: a copy is kept on our server for up to 7 days so that it can be delivered again if your connection drops; forecasts are cached for 24 hours. With a web account, your readings are kept with your account until you delete it.
• Pseudonymised chat conversations and readings: kept for at most 90 days, then automatically deleted. Erased immediately when you use Delete My Account & Data in the App. Conversations touching health, pregnancy, a death, substances or personal crisis are never stored at all.
• Usage events (§2.2): kept for 180 days, in the App and on the web app, and erased immediately by Delete My Account & Data. A copy of each event also goes to our server's application log, kept for 14 days, which Delete My Account & Data does not rewrite.
• Study orders: kept for 7 days after the study is ready. The request that produced the study and a fingerprint of your IP address are deleted as soon as it is ready; Delete My Account & Data erases your orders at once.
• Readings written by OpenAI — compatibility readings and, for versions of the App older than 1.10.30, paid readings — this applies to those readings only (§4), in the App or on the web app, not to chat replies nor to the studies written on our own hardware. We keep the request — your first name, your birth date, time and place, your profiling answers, what Solane remembers, and the same for the other person — and the text on our own server, under a shortened fingerprint of your identifier. We use them to check and improve how Solane writes and to train our own model, so that fewer readings need OpenAI. They are kept for 90 days. Today Delete My Account & Data does not erase them: write to hello@solane.app and we will.
• Web account: kept until you delete it, with — for the morning email (§13.4) — the hour you chose, your time zone, the lines for the days ahead (at most fourteen, replaced at each visit) and the date of the last email sent. Sign-in requests are deleted after 24 hours; a session expires after 180 days without a visit (§13.4).
• Purchase records: kept for 10 years (legal accounting obligation).
• Server logs: our web server's access log is kept for 14 days; our application log for 14 days; the table matching IP addresses to a country for at most 90 days (§13.8).
• Backups: our account database is copied to a backup every night; the event, conversation, order, purchase and reading-copy files are not part of those backups.
• Delete My Account & Data: erases your pseudonymised conversations and usage events, your study orders, your notification token and — on the web app — your account, chart, readings and balance at once. Purchase records, the copies of readings written by OpenAI and ordinary server logs remain.

6. Your rights

Regardless of where you live, you have the right to:

• Access the data we hold about you
• Correct inaccurate data
• Delete your data
• Receive a copy of your data in a portable format
• Object to any processing we base on our legitimate interests (§3), and ask us to restrict it while we look into your request
• Opt out of any optional processing (we don't have any "selling of data" — we don't sell anything)

To exercise any of these rights, email hello@solane.app. We respond within 30 days. If you live in the European Economic Area, the United Kingdom or Switzerland, you can also lodge a complaint with your data-protection authority — in France, the CNIL.

Because your data lives on your device — and, on the web app, with your account if you signed in — you can erase all of it instantly: Profile → Delete My Account & Data. You can also request removal of any transient server-side cache via our data deletion page.

6.1 California residents (CCPA / CPRA)

California residents have additional rights under the California Consumer Privacy Act:

• Right to know what personal information we collect, use, disclose, and how
• Right to delete your personal information
• Right to correct inaccurate information
• Right to opt out of sale or sharing — we never sell or share your data, period
• Right to non-discrimination for exercising your CCPA rights

We have not sold or shared personal information of California consumers in the past 12 months and have no plans to do so.

On the web app, the categories of personal information we collect are: identifiers (your email address if you sign in, a random identifier, your IP address in our server logs and a country derived from it), the details you give us (birth date, time and place, first name, gender, the city you live in), the content of your conversations and readings in pseudonymised form, commercial information (your purchases), and internet activity (usage events and the campaign details of your first visit). We sell none of it. A Global Privacy Control signal is read when the page loads, so a signal switched on afterwards takes effect at the next load (§13.7).

6.2 Other US states (Virginia VCDPA, Colorado CPA, Connecticut CTDPA, Utah UCPA)

Residents of states with comprehensive privacy laws have substantially the same rights described above. To exercise them, email hello@solane.app.

7. Children

Solane is intended for adults 18 and older. We do not knowingly collect data from anyone under 18. If you believe a minor has provided personal data, contact us and we will delete it.

App Store age rating: 17+.

8. In-app purchases

Solane offers consumable in-app purchases ("Stardust", shown in the App as your readings in hand) and auto-renewable subscriptions ("Pass"):

• In the App, payments are processed exclusively by Apple (App Store) or Google (Play Store). On the web app, they are processed by Stripe through RevenueCat (§13.5).
• We never see or store your payment card details.
• Subscription cancellation is managed in your device's store settings, or — for a Pass bought on the web app — from RevenueCat's customer portal (§13.5).

9. Security

We implement industry-standard measures:

• TLS 1.3 for all network traffic
• Encryption at rest for server-side data
• No advertising SDKs in the App, and no advertising profile built from your data; the web app's Google Ads tag is described in §13.7
• Regular security audits

No system is 100% secure. In case of a data breach affecting your data, we notify affected users within 72 hours of discovery, in accordance with applicable law.

10. Cookies and tracking

The App does not use cookies or cross-site trackers. On the web app, from October 18, 2026, Google's advertising tag places cookies, and OpenAI's advertising pixel keeps its click identifier, outside the EEA, the UK and Switzerland — see §13.7. From September 4, 2026 the App collects your device advertising identifier and shares it with Google Ads for a single purpose: measuring which of the adverts we ourselves buy actually brought someone to the App. This never happens if your device is set to the European Economic Area, the United Kingdom or Switzerland — there, the advertising identifier is never read at all, because doing so would require asking your consent first, and the App does not ask. Ad-personalisation signals stay disabled, so this data is not used to build an advertising profile of you or to target you elsewhere. You can reset or delete that identifier at any time in your device settings. Our analytics (Firebase, see §2.2) measure how the App itself is used.

10.1 This website

This section is about the site at solane.app — the pages you are reading now — not the web app at app.solane.app, which §13 describes. solane.app loads nothing from any other company. No analytics, no advertising tag, no embedded video, no social widget — not even a font, which is why the typefaces on this site are served from our own domain rather than from Google (the two advert landing pages on app.solane.app do load Google Fonts — §13.7). There is at present no cookie of ours to accept or refuse, and that is why you have not been shown a banner: we do not ask for permission we have no use for. You can check this yourself in your browser's network inspector. One exception does not come from this site. Outside the EEA, the UK and Switzerland, Google's advertising tag on app.solane.app places its cookies for the whole solane.app domain (§13.7), so your browser may carry them when it opens these pages. This site has no script that loads or reads them.

If that ever changes on this site, you will be asked before anything loads. Refusing will be exactly as easy as accepting, the site will be identical either way, and you can change your mind at any time from the “What this site loads” link at the foot of the site's main pages. If your browser sends a Global Privacy Control or Do Not Track signal, we treat it as a refusal and do not ask at all. (The web app at app.solane.app honours Global Privacy Control and does not read Do Not Track — §13.7.)

Your choice is recorded in your own browser — not on a server: this site records nothing of your visit. We keep a refusal for six months and an agreement for thirteen, then ask again. One honest limit: if you withdraw permission, we stop loading the third party, but any cookie it had already placed lives on its domain and cannot be deleted from ours. Your browser settings can remove it.

10.2 The free book

One page on this site asks for something: the synastry field guide. If you give your address there, we write one line to a plain text file on our own server — your address, the date, the exact sentence you ticked, and a salted fingerprint of your IP address (not the address itself, which we never keep). Nothing else. The book opens immediately; it is not emailed.

We keep the address for one reason, the one you agreed to: to write to you occasionally about reading charts. It goes to no one else, it is not a mailing list we rent or sell, and there is no tracking pixel in anything we send. Ask us at hello@solane.app and we will delete your line, or tell you what it contains — there is one line per person, so this takes us a minute.

The file lives outside the part of the server that answers web requests, and is unreadable over the internet by design. We do not use a third-party form service, so your address is never handed to one.

11. Disclaimer

12. Changes to this Policy

We may update this Policy. Material changes will be notified in-app at least 14 days before taking effect. The "Last updated" date at the top reflects the latest revision.

13. Web version (app.solane.app)

13.1 What this section covers

Solane also runs in a web browser, at app.solane.app (the "web app"), with two pages that our adverts land on: app.solane.app/compatibility/ and app.solane.app/birth-chart/. There is no app store in between: the web app is served by our own server. L&L France SAS is the data controller there too. Everything else in this Policy applies to the web app as it applies to the App, except where this section says otherwise. Some of the companies named below — Google, OpenAI, Stripe, RevenueCat and Postmark — are established in the United States, so part of your data leaves the European Economic Area when they are used, under the EU–US Data Privacy Framework where that company is certified, and otherwise under the European Commission's standard contractual clauses.

13.2 Using the web app before you sign in

When you first open the web app, your browser generates a random identifier and keeps it. It carries no name and no birth data. The browser also asks our server for a token that identifies it as a copy of Solane (an "installation token"; the App keeps one too), and keeps that too. Until you sign in, that identifier and that token are how our server tells your browser apart; its ordinary log also records the address each request came from (§13.8).

What the web app sends to our own server is what the App sends. Your birth date, time and place go there to compute your chart and the planetary positions of the day, for your daily reading. Each chat message goes there with the birth details and the computed chart Solane needs to answer. So do usage events and a pseudonymised copy of your conversations and readings. §2, §4 and §13.8 describe each of these. The web app sends no push notifications; it can email you one line from your chart each day (§13.4).

13.3 What stays in your browser

The web app keeps in your browser's local storage, for app.solane.app, what the App keeps on a phone: your birth details and chart, your first name and profiling answers, your conversations with Solane and what Solane remembers of them, your readings and forecasts, and your readings in hand (the balance §8 calls Stardust). It also keeps your random identifier, the installation token, your sign-in session once you sign in (your email address and a session key), and — if you arrived from one of our adverts — the campaign details of that first visit (§13.7). We place no cookie of our own; the cookies that Google's tag and Stripe's checkout may place are described in §13.7 and §13.5.

Clearing your browser's site data for app.solane.app erases all of it. Profile → Delete My Account & Data erases your chart, profile, conversations, readings and balance from that browser; your random identifier, the installation token and the record of past store transactions (kept so that a purchase is never credited twice) remain until you clear the site data. Signing out erases from that browser your chart, your readings and your balance — which stay with your account and come back when you sign in again (§13.4) — and also your conversations with Solane and what Solane remembers, which the account does not keep: those are gone. A browser you signed out of starts again under a new random identifier.

13.4 Signing in with your email address

Once your chart is drawn, the web app asks for your email address, and you cannot continue without it (if our sign-in email cannot be sent, the web app lets you continue for that visit and asks again later). It is how you sign in there, and on any other browser or device, with no password — and it is what lets you find your Pass, your chart and your readings again wherever you open the web app.

How it works. We email you a six-digit code and a sign-in link. The email is sent through Postmark, our email provider, from hello@solane.app; it carries no tracking pixel and no rewritten link. The code and the link work once and expire after 15 minutes; after five wrong tries the code is void. The link carries its token in the web address, so that address appears in our web server's access log for 14 days (§13.8). Before sending, we check that your address's domain can receive email (if that check itself fails, we send anyway). To stop abuse, we accept at most five requests per address and twenty per IP address in an hour. We do not tell a requester whether an address already has an account. The sign-in request itself keeps only a salted fingerprint of your IP address, not the address; the ordinary server log (§13.8) is separate.

The morning email. When you create your account on the web app from outside the European Economic Area, the United Kingdom and Switzerland, we email you one line from your own chart every day at 8 am, your local time — the sign-in screen tells you so before you enter your email. In the EEA, the UK and Switzerland we send it only if you ask for it: Email it to me on Today, or an hour you chose. In both cases Profile → Morning email changes the hour or stops it, and every email ends with a link that stops them at once. The line is composed in your browser, from your chart, for the days ahead; it is kept with your account (at most fourteen days ahead, replaced at each visit) together with the hour you chose and your browser's time zone, and our server sends only what the web app wrote — no line for the day, no email. Each email goes through Postmark's broadcast stream and carries no tracking pixel and no rewritten link. We keep the date of the last email sent, never its text.

What your account keeps on our server.

• Your email address, in lower case and without surrounding spaces, with the date the account was created and your last sign-in.
• The code and link we sent — only as irreversible fingerprints, never in clear — with the salted fingerprint of the IP address that asked for them and your random identifier. Sign-in requests are deleted after 24 hours.
• Your sessions, one per browser or device, kept as fingerprints with the kind of device. A session expires after 180 days without a visit; signing out ends it at once.
• Your random identifier, so that signing in elsewhere finds your Pass and purchases.
• Your chart: the birth date, time and place you gave, your first name, how you described your gender, the city where you live, and the positions calculated from them. It is sent to your account a few seconds after any change.
• The text of your readings — paid studies, forecasts, daily readings and the readings you saved — 2,000 at most per account — so you find them on any browser where you sign in.
• Your readings in hand, as a ledger of what you were given and what you spent. To credit what your Pass gives you, we keep the confirmation of each payment that RevenueCat sends us (product, date, transaction number), linked to your random identifier.

Your account itself stores no conversation: your conversations with Solane, and what Solane remembers about you, stay in your browser. A pseudonymised copy of your conversations (your name, birth date and cities removed as best we can) is kept on our server under your random identifier for up to 90 days (§13.8). While you have an account, that identifier is also the one your account carries, so those logs could be tied to your email address; deleting your account breaks the link and erases them.

The balance that browser held before you signed in is credited to the account once, within what you had been given (the welcome reading and what your Pass had already paid for). Readings already in the browser are sent to the account like any other.

We use your email address for nothing else: no newsletter, no marketing. The sign-in email is the only one the web app sends.

Deleting your account. Profile → Delete My Account & Data erases your account from our server at once — your email address, sessions, chart, readings and balance — together with your pseudonymised conversations and your usage events, the study orders our server was writing for you, and what the web app kept in your browser (§13.3). A reading sent to you as it is being written is also kept for 7 days under a random key that is not linked to you, so that it can be sent again if your connection drops. The record of your payments stays, as §5 says, and so do the copies of readings written by OpenAI (§13.8).

13.5 Paying by card

Payments are taken by Stripe, through RevenueCat's web checkout, which opens over the page. You enter your card details on their checkout, never on ours: we never see your card number. We give RevenueCat only your random identifier — never your birth data, your name or your readings. What you type on their checkout (card, name, email address, country) is held by RevenueCat and Stripe under their own privacy policies (RevenueCat, Stripe). When the checkout opens, Stripe's own script is loaded from js.stripe.com and may place Stripe's fraud-prevention cookies in your browser. RevenueCat is also contacted each time the web app opens, not only when you buy, to read your purchases: it receives your random identifier and your browser's IP address at each visit.

What we receive is RevenueCat's confirmation of each payment: the product, the date, the price and currency, the transaction number, whether it is a trial or a renewal, the country RevenueCat recorded for the purchase, and the event as RevenueCat sent it — which may include the email address you gave on their checkout. It sits in our purchase record with the transaction (§5), and deleting your account does not remove it. If Google's advertising tag is loaded (§13.7), we also report the price, the currency and the transaction number to Google Ads as a conversion.

A Pass bought on the web is managed — and cancelled — from RevenueCat's customer portal, which you reach from Manage subscription in the Store screen of the web app or from the link in your receipt email; if that link is unavailable, write to hello@solane.app.

13.6 Finding a place

When you type a place — where you were born or where you live — your browser looks it up as you type with Open-Meteo's place-search service, and only then. When you create your chart, if Open-Meteo finds nothing your browser also asks Photon (by komoot), and if Open-Meteo cannot be reached our own server relays that search to the same two services, which then see our server's address, not yours. The place where the other person in a compatibility reading was born is looked up once, with Open-Meteo, when the reading is prepared. These services receive the text you typed, your browser's IP address and the address of our site — never your name, your birth date or your identifier. Our server keeps relayed results in memory for 7 days, under the text typed. The place you typed is not written to our server log; the request itself is, like any other (§13.8). The web app never asks your browser for your location: our server's policy for the page switches geolocation off. The App does the same for place search; see §4.

13.7 Measuring our adverts

Arriving from an advert. When you reach a landing page or the web app from one of our adverts, the web address carries the name of the campaign, the ad group, the search words that showed it, the kind of device and the reading the advert was for. Each time you arrive with those parameters, the web app sends them to our own server in a usage event, with the page you landed on; the first of those visits is also kept in your browser. This happens for every visitor, wherever they are, and before any Google tag. Google adds a click identifier to that address: the web app records only that it was there, never its value; the full address, click identifier included, does sit in our web server's access log for 14 days, like any page requested (§13.8). The landing pages run no script of ours that talks to our server; they pass the address on to the web app as it stands.

The Google Ads tag. From October 18, 2026, the web app and the landing pages load Google's advertising tag (gtag.js, from googletagmanager.com) for one purpose: telling Google Ads when a visitor finishes creating their chart, or buys something — with the price, the currency and the transaction number — so that Google can match it to one of our adverts if that visitor had clicked one. Those are the only two events we add. When the tag is loaded it also reports each page it loads on to Google: the page address, click identifier included, and the page you came from. That is how it places its own cookies (their names begin with _gcl_) in your browser for solane.app. Depending on your browser, Google's servers (googleadservices.com, doubleclick.net) may also place cookies on Google's own domains. What Google does with them is described in Google's privacy policy. The tag runs with ad personalisation switched off everywhere, and in Google's restricted data processing mode, which — for residents of US states with privacy laws — limits Google to acting as our service provider; elsewhere Google acts under its own advertising terms. It is not used to build an advertising profile of you or to target you. The web app uses no Google Analytics and sends no events to Firebase.

The OpenAI advertising pixel. From the same date, under the same conditions — and so never in the EEA, the UK or Switzerland, and never when your browser sends Global Privacy Control — the web app and the landing pages also load OpenAI's advertising pixel (oaiq.min.js, from bzrcdn.openai.com), for one purpose: telling OpenAI when a visitor finishes creating their chart, so that OpenAI can match it to one of our adverts shown in ChatGPT if that visitor had clicked one. That is the only event we add. When the pixel is loaded it reports each page it loads on to OpenAI (bzr.openai.com), with the page address — the click identifier OpenAI adds to our links (oppref) included — and it keeps what it needs to match that sign-up to the click in your browser, for solane.app. It receives no name, no birth data and no purchase from us. What OpenAI does with it is described in OpenAI's privacy policy. Delete My Account & Data removes what both tags left in your browser for solane.app (§13.3).

When the tag is never loaded. The tag is not loaded at all — and no Google cookie is placed — if your browser is set to the European Economic Area, the United Kingdom or Switzerland (by its language region or its time zone), if its region cannot be told, or if it sends a Global Privacy Control signal, which we honour. (We sell and share nothing — §6.1 — but the signal is respected all the same.) The web app reads that signal when the page loads, so a signal switched on afterwards counts from the next load; it does not read the older Do Not Track setting. There is no consent banner on the web app: the Google tag is not loaded where asking would be required. Two things do happen for every visitor, EEA included: the campaign details of your first visit are kept in your browser and sent to our server, and the landing pages load their typefaces from Google.

Removing the cookies. Profile → Delete My Account & Data removes Google's cookies for app.solane.app and solane.app from your browser, together with the record of your first visit. Your browser settings can remove them too.

Typefaces on the landing pages. The two landing pages load their typefaces from Google Fonts. Google's font servers therefore receive your browser's IP address when one of those pages opens, wherever you are — even where the advertising tag is never loaded. The web app itself serves its typefaces from our own server, and so does the solane.app website (§10.1).

13.8 What our server keeps

• Usage events — as in the App (§2.2): the event's name and properties, your random identifier, a session number, the platform (web), the web app's version, the country of your browser's language setting, the size of your window (and your text-size setting, if you changed it) and the test group you were placed in. Our server adds the time and a two-letter country. That country is obtained by asking the public internet registries (RIPE, ARIN…) which network your IP address belongs to — they receive the address — and is kept next to that address in a table for at most 90 days. The address itself is not written into the event. Events are kept for 180 days in our event store, on our own server only — the web app sends them to no other company — and are erased at once by Delete My Account & Data. A copy of each event also goes to our server's application log, kept for 14 days, which Delete My Account & Data does not rewrite. Technical error reports go to that log only.
• Your conversations with Solane and the text of your readings — as §2.2 says. They are pseudonymised by the web app before they leave your browser and stored under your random identifier for at most 90 days. They are never stored when they touch health, pregnancy, a death, substances or personal crisis (a usage event then records that such a topic came up, never what was said). Delete My Account & Data erases them at once.
• Studies being written — a study you order is written on our server and kept there for up to 7 days after it is ready, so that you can collect it if your connection drops. While it is being written, the order holds the request that produced it and a fingerprint of your IP address; both are deleted once the study is ready. Delete My Account & Data erases your orders at once. A reading sent to you as it is being written is kept for 7 days under a random key not linked to you, so that it can be sent again; it is separate from these orders.
• Readings written by OpenAI — compatibility readings and, for versions of the App older than 1.10.30, paid readings — this applies to those readings only (§4), not to chat replies nor to the studies written on our own hardware. We keep the request — your first name, your birth date, time and place, your profiling answers, what Solane remembers, and the same for the other person — and the text on our own server, under a shortened fingerprint of your identifier. We use them to check and improve how Solane writes and to train our own model, so that fewer readings need OpenAI. This copy is separate from the orders above and exists for the App too. It is kept for 90 days. Today Delete My Account & Data does not erase it: write to hello@solane.app and we will.
• Purchases — RevenueCat's confirmation of each payment (§13.5), kept as §5 says.
• Your account — what §13.4 lists, until you delete it.
• Server logs — our web server logs each page and file you request with your IP address, the full address requested (campaign parameters, click identifier and any sign-in link you opened included), the page you came from and the name and version of your browser, for 14 days. Our application server logs each call the web app makes, with your IP address and the address called, for 14 days. The table matching IP addresses to a country (above) is kept for at most 90 days.
• Backups — our account database is copied to a backup every night; the event, conversation, order, purchase and reading-copy files are not.

13.9 Your rights and how to reach us

Your rights are those of §6, the same whether you use the App or the web app. On the web app, Profile → Delete My Account & Data erases at once what §13.3 and §13.4 describe and, of §13.8, your usage events, your conversations and your study orders. Your purchase records, the copies of readings written by OpenAI and the server logs remain, as §13.8 says. If you signed in with your email address, you can also write to hello@solane.app to receive a copy of what your account holds, to correct it, or to have it deleted; §6 says how quickly we answer.

14. Contact

Questions or complaints? Email us at hello@solane.app.

© 2026 L&L France · All rights reserved