AlmaMesh ("we", "our", "us") keeps chart and profile data in your browser. There is no account or chart-data backend. An optional feedback form uses a same-origin Cloudflare function and D1 database as described below. This policy explains every runtime network path and what stays local.

1. Your Data Stays on Your Device

What You Enter

Profile Names: Names you save for charts — stored only in this browser, never sent to us
Birth Details: Date, time, and place of birth, used on-device to compute your chart, and where you live now if you add it in Profile settings; all stored only in this browser
Chat Content: Questions and interpretations are stored in this browser; when you use optional AI, the prompt is also sent to your chosen provider as described below

Where It Lives

Browser Storage: Charts, profiles, portable settings and an optional AI key are held in one SQLite database in your browser's private on-device storage (OPFS). Legacy localStorage and user-data IndexedDB values are migrated locally, verified, and then removed; they are not kept as mirrors. If a saved interpretation cannot be read, it is set aside on this device in a quarantine table inside that same SQLite database for up to 30 days instead of being lost. Older versions kept it in localStorage; it is moved into SQLite, verified, and that copy removed. It is never sent anywhere, is not included in backups, and is erased by Reset chart / start fresh, Reset & reload, or clearing site data. Deleting a profile removes the set-aside records that hold that profile's readings; a record that matches no profile stays until Reset chart / start fresh, Reset & reload, clearing site data, or the 30-day expiry removes it. Calculated skies for dates you time travel to are cached in a separate on-device SQLite database. They can be recalculated, are never exported, and are deleted with the profile.
No Server Copy: AlmaMesh stores no server copy of your chart, profile, birth details, life events, readings, or chat. Optional provider requests and feedback are the separately disclosed exceptions below.

2. What Touches the Network

AlmaMesh makes the network do only these things:

Delivery only: downloading the app and a signed, content-addressed astronomy bundle (the DE421 ephemeris and program files) so the engine can run offline afterward. This is a one-way download; it carries no personal data about you.
Birthplace search: when you look up a birthplace, the city name you type plus ordinary HTTPS/request metadata visible to the provider are sent to a maps geocoding service (Open-Meteo) to fetch its coordinates and timezone. Never your birth date, time, name, or chart. If you are offline, AlmaMesh falls back to a bundled city list and sends nothing.
Optional AI: if you enable interpretation or chat, PII-redacted chart facts and your chat question go to your chosen endpoint. Your birth date itself is not sent, but those chart facts include planet positions and period dates, which can reveal your birth date and approximate time. If you submit life-event prose for organization after the disclosure, that narrative is sent as written without birth details or chart data.
Optional feedback: opening the form loads Cloudflare Turnstile when configured. Sending stores the page, thumbs sentiment, optional message as written, app version, and timestamp in our D1 feedback database. Do not include personal information.

We do NOT:

Operate accounts, logins, or collect your email — there is nothing to sign up for
Collect, store, or process your birth details or charts on our servers
Sell your data, track you across sites, or run targeted advertising

3. Optional Third-Party AI Endpoint

AI interpretation and chat are optional and are never required to draw a chart. They work only if YOU configure an OpenAI-compatible endpoint (for example, OpenRouter or your own).
Chart-derived AI prompts are PII-redacted and fail-closed before they reach the endpoint YOU chose. A life-event narrative is sent as written only after its separate disclosure. Those requests are subject to that provider's privacy policy and terms, not ours.
If you never configure an endpoint, no prompt ever leaves your device. The chart engine itself is zero-egress.

4. Cookies and Tracking

AlmaMesh uses no advertising or analytics trackers. Cloudflare Turnstile loads only when you open the optional feedback form and may process normal anti-bot request metadata. Product data otherwise stays in the browser storage described above.

5. Your Rights

Because your birth date, time, and chart stay on your device unless you send chart data to an optional AI, you are always in direct control of your data:

Know. Chart, profile, chat, and life-event data are visible in this browser. A feedback submission is a separate server record and may include whatever you typed in its optional message.
Delete. Remove a profile or chart in Settings, or clear your browser's site data / uninstall the app. See the Data Deletion page.
Port. Export one password-encrypted .almamesh file and import it in another browser or device, such as Chrome to iOS Safari. The password protects the transfer file only and is entered once on import.

6. Data Retention

Chart, profile, chat, and life-event data stay on your device until you delete them. Optional feedback submissions are retained separately in D1 for product improvement.
Deleting browser data is immediate but does not delete feedback already submitted. Because feedback has no account identifier, avoid personal information and contact us with the message details if you need help locating a submission.

7. Children's Privacy

AlmaMesh is not intended for users under 13 years of age.

8. Changes to This Policy

We may update this Privacy Policy from time to time. We will post the new policy on this page with an updated effective date.

9. Contact Us

For privacy-related questions:

Email: privacy@almamesh.com
Data Deletion: Visit /data-deletion or email support@almamesh.com