1. Our Privacy Commitment

Volta Instruments LLC is committed to collecting only the minimum data necessary to deliver each application's functionality. We do not collect data for advertising purposes. We do not build profiles about our users. We do not sell or share personal information with third parties for commercial gain. Each application's specific data practices are described in the app-specific sections below.

2. What Information Do We Collect?

Personal information you disclose to us

We collect personal information that you voluntarily provide to us when you contact us with questions or support requests. See Section 3 for details on what we receive when you contact us.

Sensitive Information. We do not process sensitive information.

Payment Data. Payment processing for our applications is handled entirely by Apple through the App Store. Volta Instruments LLC never receives, handles, or has access to your payment information, including credit card numbers, billing addresses, or any other financial data. Payment data is collected directly by Apple and governed by Apple's Privacy Policy at apple.com/legal/privacy.

Application Data. Some of our applications request access to certain features of your mobile device to deliver core functionality. What's requested, and how it's used, is described in that application's own section below. If you wish to change an application's access or permissions, you may do so in your device's settings.

Information collected automatically

What each application collects automatically, if anything, is described in that application's own section below. We do not use cookies, tracking pixels, third-party analytics tools, or advertising trackers in any of our applications.

3. When You Contact Us

When you contact us at studio@byvolta.app, we receive the personal information contained in your message, which may include your name, email address, and the content of your inquiry. We use this information solely to respond to your request. We do not share it with third parties. We retain correspondence for no longer than 12 months after your inquiry is resolved, unless a longer retention period is required by applicable law.

Please be aware that standard email transmission is not encrypted end-to-end. We recommend avoiding sending sensitive personal information such as financial details or government identification numbers by email.

4. How Do We Process Your Information?

How we process information is described precisely in each application's own section below, since it depends entirely on how that application works.

Correspondence is always processed the same way regardless of application: if you contact us at studio@byvolta.app, we process the personal information you provide solely to respond to your inquiry, as described in Section 3.

Purchase verification through Apple's StoreKit framework always occurs within Apple's own infrastructure; what Volta Instruments LLC itself receives as a result of that verification is described in each application's own section below.

5. What Legal Bases Do We Rely On to Process Your Personal Information?

In Short: How much personal data we process, if any, depends on which application you use. What's true for every application: correspondence you send us is processed the same way regardless.

If you are located in the EU or UK, this section applies to you.

The GDPR and UK GDPR require us to explain the valid legal bases we rely on to process your personal information.

Our legal basis for processing information, where applicable, depends on how a given application actually works, and is stated precisely in that application's own section below.

The sole exception is email correspondence to studio@byvolta.app, which we process under Legitimate Interests — specifically, our legitimate interest in responding to your inquiries. This processing is limited to the content of your correspondence, used only to respond, and retained for no more than 12 months.

We may also process information under Legal Obligations where required to comply with applicable law.

Withdrawing your consent: If we ever rely on your consent to process personal information, you have the right to withdraw your consent at any time by contacting us at studio@byvolta.app.

If you are located in Canada, this section applies to you.

We process correspondence you send us under implied consent — you contact us, and we use the information to respond. You may withdraw this consent by requesting that we delete your correspondence at studio@byvolta.app.

6. When and With Whom Do We Share Your Personal Information?

In Short: We do not share personal information with third parties for commercial purposes.

We may share or disclose information only in the following limited circumstances:

• Business Transfers. We may share or transfer your information in connection with, or during negotiations of, any merger, sale of company assets, financing, or acquisition of all or a portion of our business to another company. In the event of a business transfer, we will require any successor entity to honor the privacy commitments made in this Privacy Policy, including those specific to each application as described in the app-specific sections below.
• Legal Requirements. We may disclose information where required to do so by law or in response to valid requests by public authorities.
• Service Providers. Some of our applications share limited information with named third-party service providers as necessary to deliver that application's functionality — for example, generating a reading using an AI provider. Exactly which providers, what they receive, and why, is named specifically in that application's own section below. This is a service provider relationship necessary to operate the application, not a sale or a share of your information for advertising or other commercial purposes.

We have not sold or shared any personal information to third parties for a business or commercial purpose. We will not sell personal information in the future.

7. International Data Transfers

Whether any personal data is transferred internationally, and to whom, depends on the application and is described in that application's own section below. Our own infrastructure is located in the United States. Any correspondence you send to studio@byvolta.app is received and processed by us in the United States, regardless of which application you use.

If you are located in the EU, UK, or another jurisdiction with data transfer restrictions, please be aware that by contacting us directly, your correspondence will be processed in the United States. We handle all correspondence with appropriate confidentiality and in accordance with this Privacy Policy.

8. How Long Do We Keep Your Information?

How long we retain information depends on the application and is described precisely in that application's own section below.

If you contact us at studio@byvolta.app, we will retain your correspondence for no longer than 12 months after your inquiry is resolved, regardless of which application you use, unless a longer retention period is required by applicable law.

9. How Do We Keep Your Information Safe?

How we secure your information depends on the application and is described in that application's own section below. Where information stays on your device, the primary security is provided by iOS's built-in device security — including device encryption, app sandboxing, and Face ID or passcode protection — and we encourage you to maintain a secure device passcode and keep your iOS software up to date.

For email correspondence to studio@byvolta.app, please be aware that standard email is not encrypted end-to-end. We recommend avoiding sending sensitive personal information by email.

10. Do We Collect Information From Minors?

In Short: We do not knowingly collect data from or market to children under 18 years of age.

We do not knowingly collect, solicit data from, or market to children under 18 years of age, nor do we knowingly sell such personal information. By using the Services, you represent that you are at least 18 years of age.

What personal data, if any, there would be to delete in the event that a minor used one of our applications depends on that application — described precisely in its own section below. If we become aware that a minor has used our Services, we will investigate and take steps to prevent continued use. If you become aware of any such situation, please contact us at studio@byvolta.app.

11. Automated Decision-Making

Volta Instruments LLC does not use automated decision-making or profiling based on personal information in connection with any of its applications. No decisions that produce legal or similarly significant effects are made about you by automated means.

12. What Are Your Privacy Rights?

In Short: Depending on your location, you have rights that allow you greater access to and control over your personal information.

In some regions (like the EEA, UK, Switzerland, and Canada), you have certain rights under applicable data protection laws. These may include the right (i) to request access and obtain a copy of your personal information, (ii) to request rectification or erasure; (iii) to restrict the processing of your personal information; (iv) if applicable, to data portability; and (v) not to be subject to automated decision-making.

What we hold about you, if anything, depends on which application you use, and is described precisely in that application's own section below. See Section 18 for how to exercise your privacy rights and what our response will include.

You can make a request by contacting us at studio@byvolta.app.

If you are located in the EEA or UK and you believe we are unlawfully processing your personal information, you also have the right to complain to your Member State data protection authority or UK data protection authority.

If you are located in Switzerland, you may contact the Federal Data Protection and Information Commissioner.

13. Controls for Do-Not-Track Features

Most web browsers and some mobile operating systems and mobile applications include a Do-Not-Track ("DNT") feature or setting you can activate to signal your privacy preference not to be tracked.

California law requires us to disclose how we respond to Do-Not-Track signals. We do not respond to DNT signals because we do not engage in the tracking behaviors such signals are designed to prevent. Our applications do not track users across apps, websites, or services. If a standard for online tracking is adopted that we must follow in the future, we will inform you in a revised version of this Privacy Policy.

14. Do United States Residents Have Specific Privacy Rights?

In Short: If you are a resident of California, Colorado, Connecticut, Delaware, Florida, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, or Virginia, you may have specific privacy rights.

Categories of Personal Information We Collect

Each of our applications collects different categories of personal information. Rather than one table trying to describe every application at once, each application's own section below has its own precise table of what it collects.

How We Use and Share Personal Information

We do not use personal information for internal research, technological development, advertising, or any business purpose beyond delivering the core functionality of our applications.

We have not sold or shared any personal information to third parties for a business or commercial purpose in the preceding twelve (12) months, and will not in the future. Some applications disclose limited information to named service providers as necessary to deliver that application's functionality — described specifically in that application's own section below — which is not the same thing as a sale or a share for a business or commercial purpose.

Your Rights

You have rights under certain US state data protection laws. These rights include:

• Right to know whether or not we are processing your personal data
• Right to access your personal data
• Right to correct inaccuracies in your personal data
• Right to request the deletion of your personal data
• Right to obtain a copy of any personal data Volta Instruments LLC holds about you
• Right to non-discrimination for exercising your rights
• Right to opt out of the processing of your personal data if it is used for targeted advertising, the sale of personal data, or profiling

How to Exercise Your Rights

To exercise these rights, contact us at studio@byvolta.app. What our response includes depends on which application you use — described precisely in that application's own section below — and we will provide written confirmation of our response upon request.

Appeals

Under certain US state data protection laws, if we decline to take action regarding your request, you may appeal our decision by emailing us at studio@byvolta.app.

California "Shine The Light" Law

California Civil Code Section 1798.83 permits California residents to request information about categories of personal information (if any) we disclosed to third parties for direct marketing purposes. We do not disclose personal information to third parties for direct marketing purposes. To make such a request, contact us at studio@byvolta.app.

15. Do Other Regions Have Specific Privacy Rights?

In Short: You may have additional rights based on the country you reside in.

Australia and New Zealand

We operate in compliance with Australia's Privacy Act 1988 and New Zealand's Privacy Act 2020. What we collect and why, if anything, depends on the application and is described in that application's own section below.

If you believe we are unlawfully processing your personal information, you have the right to submit a complaint to the Office of the Australian Information Commissioner or the Office of New Zealand Privacy Commissioner.

Republic of South Africa

If you are unsatisfied with the manner in which we address any complaint with regard to our processing of personal information, you can contact the Information Regulator (South Africa):

General enquiries: enquiries@inforegulator.org.za
Complaints: PAIAComplaints@inforegulator.org.za & POPIAComplaints@inforegulator.org.za

16. Do We Make Updates to This Policy?

We may update this Privacy Policy from time to time.

For material changes — meaning changes that affect your rights, your obligations, or how we handle your data in connection with applications you currently use — we will note the change at the top of this page at the time it takes effect.

For non-material changes — including the addition of privacy terms governing new Volta Instruments applications that do not affect your existing use of applications you already use — we will update the "Last updated" date at the top of this document without prior notification.

Continuing to use any Volta Instruments application after an update to this Privacy Policy takes effect constitutes your agreement to the updated Privacy Policy. If you do not agree, please stop using the application.

17. How Can You Contact Us About This Policy?

If you have questions or comments about this policy, you may email us at studio@byvolta.app or contact us by post at:

Volta Instruments LLC
418 Broadway STE N
Albany, NY 12207
United States

18. How Can You Exercise Your Privacy Rights?

Under applicable privacy laws including the GDPR, CCPA, and similar regulations, you have the right to request access to, correction of, deletion of, and portability of your personal data. Volta Instruments LLC welcomes these requests and will respond to all of them within 30 days, regardless of your jurisdiction or whether applicable law requires it. This is our policy because it is the right thing to do.

Our response to any privacy request depends on which application it concerns, and follows what's described in that application's own section below — which may mean confirming we hold nothing, or acting directly on your request to access, correct, delete, or export what we do hold, subject to any narrow, disclosed exceptions named in that section.

If you would like written confirmation of what we hold about you — or that we hold nothing, for applications where that's true — for your own records, for legal purposes, or for any other reason, we will provide it upon request.

For data held by Apple in connection with your App Store purchases, iCloud account, or Apple ID, please contact Apple directly at privacy.apple.com.

To submit a privacy request to Volta Instruments LLC, contact us at studio@byvolta.app.

19. Our Approach to Your Privacy

mercuri is built to collect as little as we honestly can while still functioning as a real product with a free tier worth protecting. We do not use third-party analytics or advertising tools of any kind. We do not ask for your name, your email address, or your date of birth — tarot doesn't require a birth chart, so we never ask for one. The limited technical information we do collect exists almost entirely to prevent people from abusing mercuri's free tier by reinstalling the app to claim more free readings than intended — not to build a profile of you. We think you should know exactly why we collect what we collect, so this section says so plainly rather than in the abstract.

20. Your Account Identifier

mercuri creates an account identifier the first time you open the app, so your subscription and reading history can follow you rather than resetting every time you reinstall. How that identifier is created depends on your device's settings:

If you have an iCloud account and a network connection is available, your identifier is derived from an identifier Apple's CloudKit service already associates with your Apple ID — but the raw Apple value never reaches our servers. It is transformed into a one-way, irreversible hash on your own device first, and only that hash is ever sent to us. This lets us recognize that your second device belongs to the same person — so your subscription and free-trial status are consistent across your own devices — without our ever receiving anything Apple itself would consider identifying.

If you do not have an iCloud account, or a network connection is not available at that moment, mercuri instead generates a random identifier with no connection to your Apple ID, stored in your device's Keychain.

Support code — because mercuri has no account login of any kind, we have no way to know which record is yours if you write to us for help. So when you tap "support" in Settings, mercuri opens a new email to us with a short support code already written at the bottom, along with the version of the app and of iOS you are using. Under the code is a short request proof, a number your phone works out from its own identifier and the date. It shows the email came from your phone, and it stops working after a week. The code is built from the identifier described above. Nothing is sent unless you press send, and you are free to delete those lines first. If you leave them in, they let us find your account to look into what you're reporting: your subscription status, usage timestamps, and enough of a trail through our own systems to investigate a technical problem. It never reveals the contents of a reading or the question you asked — those remain sealed even from us, for the reasons Section 22 describes.

21. Preventing Free Trial Abuse

mercuri offers three free readings, for life, per account. To keep that offer meaningful rather than something a single person could claim unlimited times by reinstalling the app, mercuri uses two additional, narrow mechanisms, both provided by Apple:

App Attest — every request mercuri makes to our servers is signed using a cryptographic key generated in your device's own Secure Enclave and verified once by Apple. This proves a request genuinely came from an unmodified copy of mercuri running on a real Apple device. No personal information is included in this process — it proves the app and device are genuine, nothing about who you are. We do store the resulting key identifier, associated with your account, so future requests from your device can be checked against it — the same non-identifying shape as the device fingerprint below: it recognizes your device, but reveals nothing about who you are.

DeviceCheck — mercuri also asks Apple, through a mechanism called DeviceCheck, whether this specific physical device has claimed a free trial before — even if the app has been deleted and reinstalled, or you've signed out of iCloud. We receive only a yes-or-no answer from Apple, never a readable device identifier. If the check cannot be completed yet (Apple has not answered, or your device cannot produce it), free readings wait until it can; this usually resolves on its own within moments.

Device fingerprint — we also store a one-way cryptographic hash of your device's push-notification token, truncated and irreversible, purely as an additional signal for the same purpose — detecting when the same physical device is being used to claim multiple free-trial allowances. This value cannot be turned back into your push token or used to identify you outside of this narrow comparison.

22. Your Question and Your Reading

When you ask mercuri a question, here is exactly what happens to it and what doesn't:

Your question is not saved. It exists only in the request that generates your reading and briefly in memory while your reading is being written, and it is discarded the moment your reading is complete. It is never written to our database, never written to our logs, and never included in a backup. There is one narrow exception: if the internal step that starts writing your reading fails to run, the request carrying your question is held in a temporary internal queue for a few minutes at most, and is then deleted automatically. That queue is not used for anything else.

Your finished reading is stored, but encrypted before it is ever written to our servers, to keys created on your own devices and held only by you: one that never leaves the phone you asked on and, if you use iCloud Keychain, one that travels with you to your other devices, end-to-end encrypted by Apple. We cannot decrypt or read a stored reading — only your own devices can open it. Put simply: the copy we keep is one we cannot read. What stays readable beside it is which cards were drawn: each card's name, its suit and whether it was upright or reversed, for as long as that copy is kept. The same is true of the daily card. Claude, the AI model that writes your reading (see Section 28 below), does read your question in the moment your reading is being written, because that's how a reading gets written at all — but nothing readable of your question, or of the words written for you, is retained by us once it's done.

While your reading is being written, the name Claude gives your spread and its positions (which come from your question) are readable on our servers. They are removed as soon as your reading finishes or is stopped. If a reading fails, or you leave before it is written, they are kept for about a day so you can finish it. Either way they are gone from our systems within three days, apart from the backup described in Section 30.

A short code derived from your question is kept and removed the same way, so a retry can prove it carries the same question; it is not your question and cannot be read as one.

If your question suggests you may be carrying something heavy, we make a note of that while your reading is being prepared, so it can be written with care and end with a line saying where to find support. The note is kept and removed as the spread's name and positions are above: gone when your reading is ready or stopped, or after about a day if it fails or you leave before it is written, and with the same backup exception. One difference: if your question is declined, the note alone stays for about a day, so the app can show you that line. We use it for nothing else, and the only ones besides us who learn of it are Claude, which already reads your question to write your reading, and your own copy of the app, so it can show you the line.

If the cards decline several of your questions in one day, or you leave several while they are being checked (we count days in UTC), mercuri stops taking new questions from your account until the day ends, without sending anything to Claude. This applies to every account, subscribers included. Your finished readings, your journal and the daily card still work. A question that suggests you may be carrying something heavy is not counted when the first check declines it, and if the pause comes it shows you where to find support. This is to limit misuse.

This isn't only a policy — it's a technical limit. There is no function anywhere in mercuri's own systems that can decrypt a stored reading; the ability to do so was deliberately never built. That means if we were ever legally compelled to turn over a reading — a court order, a subpoena, any lawful demand — the most we could produce is the list of cards drawn and the encrypted file itself, which would be unreadable without keys that live only on your own devices and in your own iCloud Keychain, and that we have never had access to. We are not making a promise to refuse such a request. We are telling you we would have nothing usable to hand over even if we complied fully. This applies specifically to the contents of a stored reading — it does not extend to account information such as your subscription status, which we do hold and would have to produce if legally required to.

23. How Long We Keep a Reading

A reading's encrypted copy is kept on our servers for up to 14 days after it's created — this exists purely as a delivery buffer, in case your phone is offline, off, or hasn't opened the app since the reading finished, so your reading is still there once you reconnect. The moment your device confirms it has received and safely saved your reading, that window shrinks to 48 hours. It isn't reduced to zero at that point on purpose — a second device of yours, like an iPad, may still need a reliable way to retrieve the same reading, and this short window covers the rare case where Apple's own device-to-device sync hasn't caught up yet.

None of this changes whether the reading can be read during that window — it can't, by us, at any point, for any reason. The length of the window is about how long the encrypted file exists before deletion; it has no bearing on whether anyone here can open it, which is never.

24. Your Journal

If you save readings or notes to your journal within mercuri, that content is stored using Apple's iCloud, synced only to your own personal iCloud account across your own devices — the same way Apple Notes or Reminders work. We do not have access to your journal content, and your journal is governed by your own iCloud account settings and Apple's own terms, not by us.

This one is simpler than the reading, and worth saying plainly: your journal is never on Volta's own servers at all, in any form, encrypted or otherwise. If we were ever asked to produce it, the honest answer would be that we don't have it and never have — it exists only on Apple's infrastructure and your own devices.

25. The Collective Reading and the Daily Card

mercuri's collective (moon) reading is the same for every reader — it's generated once and shown to everyone, so nothing about it is personal to you. Requests for it pass the same App Attest verification described in Section 21, but because it is identical for everyone, a copy may be served from our content cache for up to an hour without that check.

Your daily card interpretation, by contrast, is personal to you and is handled the same way as a full reading, with one precise distinction: which of the 78 cards you drew is not sensitive, so that part is kept in the clear — but what the reading says about your day is sealed to your device exactly like a full reading, and we cannot read that part either.

26. Push Notifications

If you enable daily reading reminders or moon notifications, mercuri sends your device's Apple push-notification token directly to Apple's own push servers to deliver them. The notification itself never contains anything about your question, your cards, or your reading — it's always a fixed, generic message like "your reading is ready." Nothing private passes through Apple's push infrastructure.

Separately: when a reading you asked for is ready, we may let you know quietly — you can turn this off in Settings or from the notification itself.

27. Crisis Support

If a question you submit contains language suggestive of a mental health crisis, mercuri interrupts the reading and shows you the 988 Suicide & Crisis Lifeline, available by call or text, 24 hours a day, in both the United States and Canada. We do not store, show, or log what you actually wrote — only that something was noticed, never what it was. If this happens five times in one day (we count days in UTC), mercuri shows that same screen for any new question you ask until the day ends, without sending those questions to Claude. This is to limit misuse. This feature is presently only available in the United States and Canada; mercuri does not yet direct readers in other countries to a local equivalent. mercuri is not a crisis service — if you're in immediate danger, please contact 911 or your local emergency services directly. We may keep a brief record that this happened, for a short time — see Section 30 below for exactly what that record contains and how long it's kept. A question that stops short of that, but suggests you may be carrying something heavy, is not interrupted: your reading is written as usual and ends with one line giving the same 988 number. Section 22 says how long the note behind that line is kept.

28. Third Parties We Work With

mercuri uses a small number of outside providers, each for a specific, limited purpose:

Anthropic — generates your reading using their Claude AI models. Anthropic does not train its models on the content mercuri sends it, and automatically deletes it from their systems within 30 days, except as required for legal compliance or to enforce Anthropic's own usage policies. See Anthropic's Commercial Terms of Service at anthropic.com/legal/commercial-terms.

Apple — processes your subscription and any in-app purchases through the App Store (we never receive your payment details), delivers push notifications, syncs your journal through your own iCloud account, and provides the App Attest and DeviceCheck mechanisms described in Section 21. See Apple's Privacy Policy at apple.com/legal/privacy.

Amazon Web Services (AWS) — hosts our own servers and database, located in the United States. AWS does not have independent access to your data beyond providing the infrastructure it runs on.

We do not send any of these providers more information than is needed to do their specific job, and we do not use any of them for advertising or analytics.

29. No Third-Party Analytics or Advertising

mercuri does not use any third-party analytics, crash-reporting, or advertising SDKs of any kind — no Firebase, no Google Analytics, no Sentry, no attribution or ad-tracking tools. We do not track how you use the app screen-by-screen, and we do not build behavioral profiles. The only usage information we hold is the specific, narrow set described in Section 30 below — how many readings you've had, mainly for enforcing your plan's limits — not a general record of your activity in the app.

30. How Long We Keep Everything Else

Account and usage information (your account identifier, App Attest key identifier, device fingerprint, push token, time zone (its offset from UTC and its name), reading counts, and the dates you last used the app, last opened your daily card, and last opened the moon reading, each overwritten rather than logged) — kept for as long as your account is active.

Crisis or invalid-question flags — if the safety feature in Section 27 is triggered, we may keep a record that it happened — your account identifier, which reading it was, and that the reason was "crisis" or "invalid" — for 7 days, for monitoring purposes only. We never keep the question itself. We also keep two counts for the daily limits in Section 27 and Section 22: how many times that day a question of yours triggered the crisis screen, and how many times that day the cards declined a question of yours (including one you left while it was being checked), each under a one-way hash of your account identifier, for about two days. If a declined question suggested you may be carrying something heavy, we keep only a note that this happened, on the same record and for the same time, so the app can show you where to find support. They are used only for those limits.

Subscription verification records — kept as needed to maintain your subscription and comply with tax and accounting obligations.

A note on backups — our production servers use a standard AWS safety feature that keeps a continuously-updated backup of our database, so we can recover from a serious technical mistake. This means that even after something is deleted from our live systems, a copy may still exist in that backup for up to 35 days before it's fully gone — but that backup isn't something anyone can browse or search; the only way to retrieve anything from it is a deliberate restoration of a table to a past point in time, by an administrator, into a new table, not something that could happen quietly or by accident.

A note on IP addresses — like any server on the internet, ours necessarily receives your device's IP address as part of any connection — this is how the internet works, not something specific to mercuri. We do not intentionally log or store IP addresses in the ordinary course of operating mercuri.

31. Accessing, Correcting, or Deleting Your Data

You can ask us what we hold about you, ask us to correct it, ask for a copy of it, or ask us to delete it, at any time, by emailing studio@byvolta.app. To keep anyone else from asking for your data, please send the request from the app (Settings → support): we act on a request for a copy or a deletion only when it carries the request proof from that email, and we reply only to the address it came from. We will respond within 30 days. For a deletion request specifically, we will delete your reading history, usage information, notification preferences, and subscription linkage within that time.

One narrow, disclosed exception to deletion: we retain the minimal device-identifying signals described in Section 21 — your device fingerprint and your App Attest key identifier — even after a deletion request, specifically and only to prevent the same physical device from claiming a second set of free trial readings. Both exist for the same reason and are kept for the same reason. They are kept on a small record filed under your account identifier (described in Section 20), which is how mercuri recognizes you if you return on the same device or iCloud account. That record holds nothing else: no readings, no plan, no counts, and no settings. Two other short-lived records outlast a deletion. One is a note that a deletion happened, kept for 36 days under a one-way hash of your account identifier, so that restoring a backup cannot bring a deleted account back. The other applies only if you were ever refunded a reading: a count of those refunds, kept for up to 35 days under one-way hashes of the same device signals and of your subscription, so the refund limit cannot be reset by deleting and returning. This is a standard, legally recognized exception for fraud and abuse prevention — we're naming it plainly here rather than leaving it unstated. Nothing else about your request is affected by this exception.

32. Children and Minors

mercuri is intended for users who are at least 18 years old, consistent with the eligibility requirement in our Terms of Use. We do not knowingly collect personal information from anyone under 18. Since mercuri does not collect a name, email address, or date of birth from any user, we have no way to independently verify age — if you believe a minor has used mercuri, please contact us at studio@byvolta.app.

mercuri's Categories of Personal Information

The table below shows the categories of personal information mercuri collects, following the same categories described generally in Section 14 above.

mercuri collects your device's time zone: its offset from UTC (a number of minutes, like -300) and the zone's name (such as “America/New_York” or “Europe/London”). It uses them only to send reminders and moon notifications at the right local time, including across daylight-saving changes, and to work out your calendar date for daily readings. A time zone is shared by millions of people and names at most a broad region; mercuri never asks for or uses your device's location.