Privacy Policy

Effective date: September 19, 2026

Last updated: October 28, 2026

This Privacy Policy explains what information Domisomi LLC ("Domisomi," "we," "us," or "our") collects through the Stratocheck iOS application (the "App") and the servers and application programming interfaces that support it (together with the App, the "Service"), and how we use, disclose, and retain it. It also explains your choices and rights.

This Policy describes how the Service works today. When it says we do not collect something, that describes the Service as it is currently designed and operated.

1. Summary

• The Service estimates whether the sky above a location will stay clear over the next few hours. To do that, it needs the location's latitude and longitude.
• You can get a forecast without an account. You need one only to save sites, sync preferences, keep a subscription, or create an API access token. Accounts use Sign in with Apple, and we do not receive your name or email address.
• The App does not use advertising identifiers and contains no advertising, attribution, or third-party analytics software development kits ("SDKs").
• We do not sell or share personal information, as the California Consumer Privacy Act defines those terms.
• We do not track your location in the background. We receive coordinates when you request a forecast or save a site, and when the App refreshes the forecast for the place you last selected in the background, using coordinates it already has.
• Our service-health analytics are anonymous. Each record identifies only an area about 20 by 25 to 35 kilometers, contains no account, device, session, IP address, or other identifier, and is deleted after 30 days.
• Deleting your account permanently deletes your account data. It does not just deactivate the account.

2. Information We Collect

2.1 Location Information

Information collected. We collect the latitude and longitude of the places you request forecasts for. They come from your device's location services, with the permission you grant in iOS, or from a place you search for, select on the map, or save.

Forecast requests. Each forecast request sends coordinates as request parameters. Our servers match them to our forecast grid, return the forecast, and discard them. We do not store the exact coordinates from a forecast request in a database, link them to your account, or record them in our request logs.

Background refresh. While the App is in the background, iOS may let it refresh the forecast for the place you last selected, at most every 15 minutes. These requests use coordinates the App already has: a saved site's coordinates, or the location it obtained the last time you used the App. We handle them like any other forecast request. The App cannot get a new location reading in the background, because it has permission to use your location only while you are using it.

Saved sites. If you are signed in and save a site, we store the name you give it, its exact coordinates, its position in your list, whether it is your primary site, and whether standing alerts are on for it. These coordinates are the most precise personal information we hold. We store them only because saved sites need them to work. If your subscription lapses, we keep your saved sites so they come back if you resubscribe. Your subscription tier sets how many saved sites you can use, not whether we keep them.

Background location. The Service does not keep a continuous record of your location. You can withdraw location permission at any time in iOS Settings, and the App will then use searched and saved sites.

2.2 Device Integrity Information

Before we answer forecast requests, we use Apple's App Attest service to check that each request comes from a genuine, unmodified copy of the App running on real Apple hardware.

For each installation of the App, we store an installation identifier we generate, the keys and related data that App Attest issues for the installation, and the dates the installation was first seen, attested, and last seen. We also briefly store outstanding cryptographic challenges and a record that each registration was completed.

So that one installation cannot use up capacity that others share, we count each installation's attestation challenges and attested requests over a short period. Each counter holds only the installation identifier, the kind of request, the number of requests, and when the period began and the latest request arrived. It contains no IP address, and it is deleted within 2 days after the period ends.

We use this information to prevent abuse of the forecast service and circumvention of usage limits. It does not include your name, email address, device name, or any advertising identifier, and we do not store the Identifier for Advertisers ("IDFA") or the Identifier for Vendors ("IDFV"). It is not linked to your identity unless you also sign in.

2.3 Account Information

Accounts can be created only through Sign in with Apple. We do not receive or process your Apple Account password. We do not ask Apple for your name or email address, so we do not receive them either.

If you sign in, we store:

• Apple user identifier. The unique identifier Apple issues for your account. Apple issues it only to Domisomi, so other developers cannot use it to identify you.
• Apple refresh token. A token issued by Apple, which we store encrypted. We keep it for one reason: so that when you delete your account, we can ask Apple to revoke Stratocheck's access, as Apple requires.
• Sign-in nonces and authorization codes. We store sign-in nonces and Apple authorization codes only as one-way cryptographic hashes, and delete them within two days after they expire or are used.
• Installation links. A link between your account and each App installation you sign in from, with the dates each link was created and last used.
• Account audit records. Records of sign-ins, sign-outs, account deletions, and failed requests to Apple to revoke access, each with a timestamp. We keep them to investigate security incidents and to show that deletion requests were carried out. We keep sign-in and sign-out records for one year. When you delete your account, we delete these records and keep only a record of the deletion, as described in Section 7.2.
• Last activity date. The most recent day your account was active: the last day an App installation you are signed in on contacted us, or one of your API tokens was used. We keep it only to find accounts that have been inactive for 24 months, as described in Section 7.2.

2.4 Preferences

If you sign in, we store your preferred units of measurement (metric or imperial), whether notifications are on, and your quiet-hours settings.

2.5 Subscription and Purchase Information

Stratocheck Pro is an automatically renewing subscription sold through the Apple App Store, and Apple processes all payments. We do not receive your payment card number, bank account details, billing address, or any other financial account information, and we have no way to access it.

Apple sends us, and we store, what we need to determine your subscription status: the transaction identifier and original transaction identifier, the product identifier, the store environment, the app account token, the purchase and original purchase dates, the expiration and revocation dates, the dates Apple signed the transaction records, and the resulting status (active, expired, refunded, or revoked). We also record the notifications Apple sends us through App Store Server Notifications, so that renewals, refunds, and revocations take effect without you having to open the App.

Apple also tells us how your subscription will renew: whether automatic renewal is on, the product it will renew to, the renewal price and its currency, and whether you bought the subscription yourself or have it through Family Sharing. We keep the most recent of these with your subscription record.

California law requires us to remind you of your subscription's terms each year. About every nine months, the App shows you the product, how often and how much you are charged, and how to cancel. For each reminder, we store the text we showed you, the product, price, and currency it stated, when it was due and first shown, whether a newer reminder replaced it because those terms changed, and when, and from which App installation, you confirmed it.

We use this information only to determine whether your account is entitled to Stratocheck Pro features and to remind you of your subscription's terms.

2.6 API Access Tokens

If you create a personal access token so that an AI agent, script, or other software you use can request forecasts through our Model Context Protocol ("MCP") endpoint or our forecast API, we store a hash of the token, a short non-secret prefix that helps you tell your tokens apart, the label you give it, and the dates it was created, expires, was last used, and, if applicable, was revoked.

We show the full token only once, when you create it, and we do not store it in a recoverable form. If you lose it, we cannot show it again or recover it. Tokens expire one year after they are created, and you can revoke a token at any time.

Requests made with a token contain the place names or coordinates your software sends. We handle them as described in Section 2.1.

2.7 Service-Health Analytics

For each forecast and map-tile request, we record an anonymous event that tells us where the Service is used, how quickly it responds, and whether it is working correctly.

Each event contains: the time of the request; a four-character (level 4) geohash, which identifies an area about 20 kilometers north to south and 25 to 35 kilometers east to west in the contiguous United States, rather than your coordinates; the endpoint requested; a request-origin category from a fixed list (current location, saved location, search, map, widget, background, or unknown); information about the forecast used to answer the request, such as its forecast cycle, source satellite, age, freshness, and confidence status; the response status code; a result code; the response time in milliseconds; and the version of our server software.

Events contain no user, account, installation, session, saved-location, request, IP address, user-agent, pseudonymous, hashed, or client identifier, and nothing else that could link one event to another. So neither we nor anyone who obtained this data could use it to count unique users, measure retention, or reconstruct the sequence of one person's requests, and we do not try to.

The request-origin category comes from a request header that accepts only the values listed above. Any other value is recorded as "unknown," and nothing else from the header is stored.

We keep analytics events for 30 days. A scheduled process deletes expired events at least once an hour.

2.8 Operational Logs

Our access logs record each request, its outcome, and how long it took. They do not record your IP address or your coordinates.

Our application logs record operational events and errors. We keep logs for 90 days in production and 30 days in other environments, and then they are deleted automatically.

2.9 IP Addresses

Like any internet service, our infrastructure receives your IP address when your device connects to the Service.

We use IP addresses for one thing: to keep any single source from exhausting our device-attestation capacity. When the App registers, requests an attestation challenge, or makes an attested request, such as a request for a forecast, we convert the IP address it connects from into a short code that many other addresses share, and we count the requests for each code over a short period. Each counter holds only the code, the kind of request, the number of requests, and when the period began and the latest request arrived. It does not contain the IP address, it is not linked to an installation, an account, or the content of any request, and it is deleted within 24 hours.

We do not store IP addresses in our access logs, our analytics, or your account record.

2.10 Legal Acceptance Records

When you tap "Agree and Continue" in the App, we record that you accepted our Terms of Service and acknowledged this Policy. Each record holds the document, its version, the time, and the App installation you tapped it on. If you sign in, we copy these records to your account with their original times, unless your account already has a record of the same version. Section 15.6 of our Terms of Service lets you opt out of arbitration within 30 days after you first accept the Terms, and these records show when that period begins. We record only the first time you accept or acknowledge each version of a document; opening the App again does not create new records.

3. Information We Do Not Collect

The Service does not collect the following, and the App contains no code designed to collect it:

• advertising identifiers, including the IDFA, or any information for an advertising network or attribution SDK;
• information for any third-party analytics SDK;
• contacts, photos, camera, microphone, calendar, or health data;
• biometric data;
• browsing or search history from outside the App;
• financial account or payment card information;
• a continuous record of your location in the background; or
• any information used to track you across apps or websites owned by other companies.

4. How We Use Information

We use the information described in Section 2 for these purposes:

We do not use your information to build advertising profiles or to train models on your behavior. Our forecasting model is trained on satellite imagery from the National Oceanic and Atmospheric Administration ("NOAA"), not on user data.

5. How We Disclose Information

We do not sell personal information, and we do not share it for cross-context behavioral advertising.

We disclose personal information only to these service providers, and only for these purposes:

• Apple Inc., for Sign in with Apple, App Attest, and App Store purchases and server notifications. Apple's privacy policy governs how Apple processes your information.
• Amazon Web Services, Inc. ("AWS"), which hosts the Service in the United States. AWS stores the information described in this Policy on our behalf and does not use it for its own purposes.

We also use these data sources to run the Service. We send no personal information to either of them:

• NOAA/NESDIS GOES satellite imagery, which we get through the AWS Open Data program and use as input to our forecasting model. Retrieving imagery is not triggered by, and does not reveal, any individual request.
• GeoNames, whose United States place-name dataset we import into our own database. Place searches run entirely within our infrastructure, and your search text is not sent to any outside geocoding service.

We also send automated notifications to Domisomi staff through a third-party notification service when a new App installation is registered, an API token is created, or a subscription begins. Each notification says only what kind of event it was, whether it happened in our production or a test environment, and, for a subscription, the product purchased. It contains no text you enter and no user, account, device, or transaction identifier.

We may disclose information when required by law or valid legal process, or when necessary to protect the rights, safety, or property of Domisomi, our users, or the public. If we are legally compelled to disclose your information, we will tell you unless the law forbids it.

If Domisomi is involved in a merger, acquisition, or other transfer of its business, account information may be transferred as part of that transaction. We will tell you before your information becomes subject to a different privacy policy.

6. Data Retention

We keep information for the periods below. A scheduled process runs at least once an hour and deletes records when their retention period ends.

We also delete an account, with everything above that we keep until you delete your account, after 24 months without activity, as described in Section 7.2.

7. Your Choices and Rights

7.1 Choices Available to All Users

• Using the Service without an account. You can get forecasts without signing in.
• Location permission. You can withdraw location permission in iOS Settings and use searched or saved sites instead.
• API tokens. You can revoke any API token in the App at any time.
• Saved sites. You can delete any saved site on its own.

7.2 Account Deletion

When you delete your account in the App, it is permanently deleted, not just deactivated. Deletion removes your account record along with your Apple credentials, installation links, saved sites, preferences, legal acceptance records, subscription and entitlement records, renewal reminders, App Store notifications about your purchases, API tokens, and sign-in and sign-out records. We also ask Apple to revoke Stratocheck's refresh token for your Apple Account. If that request fails, we keep the token, encrypted and with nothing linking it to you or your account, ask Apple again for up to 7 days, and then delete it.

Inactive accounts. If your account has no activity for 24 months, we delete it in the same way. Activity means signing in, using the App while you are signed in, including when it refreshes in the background, or using one of your API tokens. We do not delete an account for inactivity while it has an active Stratocheck Pro subscription, and the 24 months begin no earlier than the end of your last subscription period. Because we do not collect your name or email address, we cannot warn you before we delete an inactive account.

These exceptions apply:

1. Anonymous analytics. We cannot delete service-health events on request. They contain nothing that identifies you or links them to your account, so we have no way to find the events associated with you. They are deleted automatically within 30 days.
2. Apple purchase records. Apple keeps its own records of your purchases, under its own retention practices. Deleting your account does not cancel a subscription; you cancel it in your Apple Account settings. Until you do, Apple keeps sending us renewal notices, which we store without linking them to any account and delete after 90 days.
3. Record of the deletion. We keep a record that the account was deleted, and of any failed request to Apple to revoke access, for 24 months. For the first 30 days, the record includes our internal identifier for the deleted account, so that we can repeat the deletion if we restore a backup. After that, it contains no identifier.
4. Backups. Copies of deleted information may remain in encrypted database backups for up to 14 days, until the backups expire. If we restore a backup, we delete again any account that was deleted after the backup was made.
5. Installation records. Two records belong to an installation of the App rather than to your account: its device attestation record and its record of your accepting our Terms of Service and acknowledging this Policy. They remain until the installation goes unused for one year. Deleting your account removes their link to your account.

7.3 California Privacy Rights

If you are a California resident, the California Consumer Privacy Act, as amended by the California Privacy Rights Act (together, the "CCPA"), gives you these rights:

• Right to know. You can ask what personal information we collect, the purposes we use it for, and the categories of recipients we disclose it to. Sections 2, 4, and 5 of this Policy also set this out.
• Right of access. You can ask for a copy of the personal information we hold about you.
• Right to delete. You can ask us to delete your personal information, subject to Section 7.2.
• Right to correct. You can ask us to correct inaccurate personal information.
• Right to opt out of sale or sharing. We do not sell or share personal information, so we do not provide a "Do Not Sell or Share My Personal Information" link. We have not sold or shared personal information in the preceding twelve months.
• Right to limit the use of sensitive personal information. Precise geolocation is sensitive personal information under California law. We use it only to provide the Service you request and for the purposes described in Section 4, and never to infer characteristics about you. These uses fall within the exceptions to the right to limit. You can still withhold location permission or delete a saved site at any time.
• Right to non-discrimination. We will not give you a lower level of service or charge you a different price because you exercise any of these rights. The differences in features between the free tier and Stratocheck Pro reflect only the subscription you choose.

Categories of personal information collected. In the preceding twelve months, we have collected these categories of personal information, as the CCPA defines them: identifiers (the Apple user identifier and installation identifiers); commercial information (subscription and transaction records); internet or other electronic network activity information (service-health events and operational logs); and geolocation data, including precise geolocation where you provide it.

Submitting a request. You can exercise your rights of access and deletion in the App while you are signed in. To get a copy of the personal information associated with your account, use Download My Data on the Account screen. To delete your account, use Delete Account, as described in Section 7.2. You can correct your saved sites and preferences in the App at any time. For any other request or question, email [email protected]. Because we do not collect your name or email address, the App is the only way we can confirm that a request comes from the account holder, so we will ask you to complete the request there. We will respond within 45 days, and we will tell you if we need the additional 45 days the CCPA permits.

Installation records. The records we keep for an installation of the App rather than for an account, described in Sections 2.2 and 2.10, are not linked to your name, your contact information, or, unless you sign in, an account. So if you use the App without an account, we cannot verify that a request about them comes from you. They are deleted after the installation goes unused for one year.

Authorized agents. An authorized agent can submit a request on your behalf by providing written proof of authorization. We may still ask you to confirm the request in the App.

7.4 Residents of Other States

If you live in another U.S. state that has a comprehensive consumer privacy law, you may have rights similar to those in Section 7.3. We handle requests from all users the same way, wherever they live. To submit a request, follow the process in Section 7.3.

Appeals. If we decline all or part of your request, we will tell you why. You can appeal by emailing [email protected] with the subject line "Privacy Request Appeal." We will respond within 45 days and explain our decision. If we deny your appeal, we will tell you how to submit a complaint to your state's attorney general.

8. Security

We protect the information described in this Policy with measures that include:

• All communication between the App and our servers is encrypted in transit with TLS, and stored data is encrypted at rest.
• Sign-in nonces, Apple authorization codes, and API tokens are stored only as one-way cryptographic hashes, never in readable form.
• Apple refresh tokens are encrypted with managed keys.
• In production, forecast requests must carry a valid device attestation, and replayed requests are rejected.
• Rate limits apply to attestation, forecast, and API token requests.
• Our production systems run on hardened, access-controlled infrastructure.

No method of transmission or storage is completely secure, and we cannot guarantee the security of your information. If we learn of a security breach affecting your personal information, we will notify you, in the App or by any other means the law permits, and we will notify any applicable regulator, as the law requires.

9. Children's Privacy

The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has given us personal information, contact us at [email protected] and we will delete it.

10. International Users

The App is available only on the United States App Store, the Service provides forecasts only for the contiguous United States, and our infrastructure is in the United States. If you use the Service from outside the United States, your information will be processed in the United States, whose data protection laws may differ from your country's.

11. Changes to This Policy

We will post any changes to this Policy on this page and update the "Last updated" date above. If a change materially reduces the protection of your personal information, for example by allowing us to collect information this Policy says we do not collect, we will give notice in the App before the change takes effect and get your consent where the law requires it.

12. Contact Us

Send questions, requests, and complaints about this Policy to Domisomi LLC at [email protected].

California residents who are not satisfied with our response can contact the California Privacy Protection Agency or the California Attorney General.