Privacy Policy

Effective date: 23 October 2026
Last revised: 23 October 2026
Supersedes: the RidgeReader Privacy Policy of 8 October 2026. This policy covers both the ridgereader.com website and the RidgeReader application.

Introduction

This Privacy Policy applies to Alpha Angle Labs, LLC, a Colorado limited liability company (“RidgeReader,” “we,” “us,” or “our”) and describes how we collect, use, and share information from users of the RidgeReader website, mobile application, and related services (collectively, the “Service”).

“Personal Information” means any information relating to an identified or identifiable individual. It does not include information that has been aggregated, de-identified, or anonymized such that it can no longer reasonably be associated with you.

By accessing or using the Service, you consent to the practices described in this Privacy Policy. If you do not agree with this Privacy Policy, do not access or use the Service. Your use of the Service is also subject to our Terms of Use at https://ridgereader.com/terms.

Highlights

• Your photos stay on your device during normal analysis. Slope analysis runs entirely in the application on your own device; we do not receive, process, or store your photographs as part of it. There are two exceptions, and both are your choice: a “My result doesn’t look right” report, which sends a photo only when you press the button and confirm (Section 2), and Contribute, if you turn it on (Section 3).
• A report includes where the photo was taken. If you send us a report, we receive a reduced copy of the photo — prepared on your device, with the faces it detects blurred and the data embedded in the image file removed — and the location as a separate field. We say so on the screen before you send.
• Contribute is optional, and off unless you turn it on. It is available only to signed-in account holders, who must be 18 or older. When it is on, the photos you take with RidgeReader’s camera are sent to us — with the faces it detects blurred and embedded data removed on your device — together with the precise location and the phone’s readings at the moment you took them, to train RidgeReader’s own models. You can turn it off, and delete what you have contributed, at any time. Section 3 explains exactly what is sent.
• An account is optional. The Service works fully without one. Signing in lets you sync the routes and zones you draw across your devices, and makes Contribute available.
• We do not sell your Personal Information, and we use no advertising or tracking services. The application carries no analytics SDK at all; the website measures aggregate, cookie-free traffic. Section 1.4 is precise about the difference.
• Terrain data you download for offline use stays on your device. We do not have access to it and we do not receive a record of the analyses you run.
• We do receive the locations you ask us to build terrain for — including where you took a photograph, if terrain for that spot is not yet on your device. Section 1.3 explains exactly what is sent and what is kept.
• You must be 18 or older to create an account. The Service itself has no age limit — its terrain and analysis features collect almost nothing, so there is no reason to lock younger backcountry travelers out of them.

1. Information We Collect

1.1 Information you provide to us

• Account information (optional). You may use the Service without an account. If you choose to sign in, you do so through a third-party identity provider — currently Google — and we receive from that provider your email address, your name, your profile picture URL, and a unique account identifier. We never receive your Google password. We do not offer a RidgeReader-specific password and therefore do not store one.
• Routes, zones, and drawings. Lines, polygons, and boundaries you draw or import, together with the names, colors, and groupings you give them. See Section 4.
• Contributions (optional). If you turn on Contribute, the photographs you take with RidgeReader’s camera and the readings recorded with them. See Section 3.
• Manually entered coordinates. If you type a latitude and longitude rather than using a photo's embedded location, those coordinates are used on your device and are transmitted to us only if you then ask us to build terrain for that area.
• Waitlist sign-up. If you join the waitlist on ridgereader.com, we collect your first and last name and your email address. We use these only to contact you about RidgeReader — beta access, launch news, and occasional product updates. Every email includes a one-click unsubscribe link, and unsubscribing removes you from the list.
• Communications. If you contact support, we receive your name, email address, the contents of your message, and any attachments you send.
• Payment information. If you purchase a subscription in the future, payment details will be collected and processed by a third-party payment processor on our behalf. We would not store complete payment card numbers; we may retain the last four digits, card brand, and expiration date for billing and support purposes. No paid tier is currently offered and no payment information is currently collected.

1.2 Photographs and camera data — processed on your device

When you select a photograph for analysis, the application reads its embedded EXIF metadata within the application on your device and extracts:

• GPS latitude and longitude
• Compass heading, where present
• Focal length and image dimensions, used to derive the camera's field of view
• Capture timestamp, where present

None of this leaves your device as part of the analysis, and neither does the photograph. The slope computation, the terrain render, and the resulting statistics are all produced locally from terrain data already stored on your device. No analysis request is sent anywhere. If terrain for the photograph’s location is not yet on your device, the application requests it from us, which sends that location and the compass heading (Section 1.3); the photograph and its other metadata still stay on your device.

A photograph reaches us in exactly two circumstances, and both are your choice: you report a result that looks wrong and confirm the send (Section 2), or you have turned on Contribute and take a photograph with RidgeReader’s camera (Section 3). Photographs you select from your device’s photo library are never contributed, whether or not Contribute is on. Nothing about analysis uploads an image.

If a photograph contains no location data, the application asks you to enter coordinates manually. It does not substitute your device's current position. An uploaded photograph could have been taken anywhere at any time, and your current position describes you rather than the picture — using it would answer a question about the wrong terrain with no outward sign that anything had been assumed.

Taking a photograph inside the application is a different case. When you use the in-app camera, the application reads your device's live GPS position and its accuracy, compass heading, and tilt at the moment of capture, because there the device and the subject genuinely are in the same place. This occurs on your device and is not sent to us — unless Contribute is on, in which case these readings are sent with the photograph (Section 3).

You may strip EXIF metadata before selecting a photograph, or enter coordinates manually instead. Without heading data the application cannot orient the terrain render to match the photograph.

1.3 Information we receive when you request terrain

This is the main category of information the Service transmits to us, and it is narrower than it may appear. We receive the locations you ask us to build or download terrain for — and when you analyze a photograph somewhere whose terrain is not yet on your device, the application asks us to build it, so that location is among them. Once terrain covering an area is on your device, every analysis you run in that area is invisible to us.

• Pre-built regions. Downloading a region from our catalog tells us which catalog region you requested.
• Automatically generated regions. Requesting terrain for a point — for example, the location of a photograph you are analyzing — transmits that point’s precise coordinates and, where available, the compass heading. Our servers use them only to decide which terrain to build: the region is anchored to a grid of 0.001 degrees (roughly 110 meters) and oriented to one of a fixed set of compass sectors. We do not store the precise coordinates or heading, and we do not write them to our logs. The resulting terrain file is named after that anchor point and compass sector, so its name reflects approximately where the request came from (to about 110 meters) and which way the camera faced. It contains no account identifier, session identifier, or other Personal Information, and it is reused for anyone who requests the same area (Section 5).
• Custom regions built from your drawings. If you ask us to build terrain around routes you have drawn, the coordinates of those routes are transmitted to us at full precision, because the shape of the region is derived from them. This is the one path on which we receive precise geographic information you created. The resulting terrain file is identified by a hash of that geometry.

1.4 Information we collect automatically

• IP address. Our servers receive your IP address with each request, as any web server does. We retain IP addresses in server memory for up to one hour for the sole purpose of enforcing per-user rate limits on terrain generation, which is computationally expensive. These records are not written to disk, are not associated with your account, and are discarded when the hour elapses or the server restarts.
• Server logs. Our hosting providers generate operational logs that may include IP address, request path, timestamp, response status, browser type (user agent), and the referring page.
• Device and technical information. Request headers such as browser type and operating system version, as transmitted by your browser. If Contribute is on, each contribution also records your device model and operating system version, because phone sensors err differently from model to model.
• Location information. The Service uses your device's GPS or browser geolocation only when you use a location-dependent feature, such as taking a photograph in the application or centering the map on your position. We do not collect background location, and location acquired this way is used on your device — or, if Contribute is on, sent with the photograph you take (Section 3).
• We do not use advertising or tracking services. Neither the application nor the website contains an advertising identifier, a tracking pixel, or a cross-site tracking service, and we do not sell or share Personal Information for advertising.
• No analytics in the application. The RidgeReader application contains no analytics SDK and no crash-reporting service. We may add crash reporting in the future; if we do, this policy will be updated to name the provider before it is enabled.
• Aggregate traffic measurement on the website. The ridgereader.com website uses Vercel's built-in traffic measurement, which reports page views, referring site, country, and device type in aggregate. It sets no cookies and does not identify you individually.
• Aggregate service statistics. We count terrain requests by day, by coarse geographic cell, and by outcome, so we know where terrain is wanted and where coverage is missing. These counts record no IP address, no account identifier, no session identifier, and no exact coordinates — only grid cells of 0.014 degrees, approximately 1,560 meters north-to-south and 1,200 meters east-to-west at Colorado latitudes.

1.5 Local storage on your device

The Service stores the following in your browser's or device's local storage, where it remains under your control and is not transmitted to us except as described in Sections 3 and 4:

• Downloaded terrain data, in the Origin Private File System (OPFS) or equivalent
• Your routes, zones, and drawings
• Your acceptance of our Terms of Use
• Interface preferences, such as which map layer you last used
• Whether Contribute is on, and whether you chose to send contributions only over Wi-Fi
• If Contribute is on, contributions waiting to be sent, already prepared as described in Section 3.2 — for example while you are out of signal, or waiting for Wi-Fi. They are deleted from your device once sent, never kept longer than 14 days, and deleted immediately if you turn Contribute off or sign out.
• If you are signed in, an authentication token issued by our identity provider

1.6 Information we derive

• Region matching. We match the coordinates of a terrain request to a mountain region and the corresponding avalanche forecast center. This lookup runs on our servers as part of answering the request.
• Terrain statistics. Mean slope, maximum slope, and the proportion of terrain in each slope band. These are computed on your device and are not transmitted to us.
• From contributions. If you contribute, we may derive from each photograph, on our own systems, an estimate of where the camera was really pointing and which parts of the image show which terrain. These derived labels are kept with the contribution and deleted with it.

2. Reporting a Result That Looks Wrong

The terrain RidgeReader draws can be wrong — survey gaps, old elevation data, a compass reading that was off. When a result looks wrong you can send it to us so we can reproduce it.

Nothing is sent unless you press the button and confirm. There is no background upload, no automatic crash report, and no sampling of results.

What a report contains. When you send one, we receive:

• A copy of the photograph, prepared on your device before it is sent. The application makes it smaller (at most 2,048 pixels on its longest side), blurs the faces it detects, and removes the data embedded in the image file — the EXIF and similar metadata that normally hold the GPS position, the capture time, and camera details. Faces are detected only to blur them: we do not identify anyone and keep no record of any face, and the report says only how many were blurred. Detection can miss a face that is very small or far away. If the photograph can’t be prepared on your device, the report is sent without it, and the application tells you.
• The precise location where the photo was taken, its compass heading and, where the photo recorded it, when it was taken — sent as separate fields, not inside the image. The location is the single most sensitive thing in a report, and it is also the thing that makes a report useful — without it we cannot tell which terrain you were looking at.
• A picture of the terrain view you were shown, captured from your screen, so we can see the render you are describing.
• The analysis itself: coordinates used, camera angle and heading, the terrain region identifier, and the slope statistics you were shown.
• Anything you type in the comment box.
• Your email address, only if you choose to enter one. It is optional, it is used solely to reply to you about that report, and a report sent without one is still useful.

What a report does not contain. We do not attach your identity, your other photographs, your saved routes, or anything from a previous session. A report is a single snapshot you chose to send.

Where reports go. They are stored with our database provider, Supabase, under access rules that permit reports to be created but not read back by anyone using the application. They are used to diagnose terrain and rendering problems and for nothing else — not for training models, not for marketing, and they are never published or shared.

Retention and removal. Reports are kept while the problem they describe is open and for a reasonable period afterwards, and no longer than 24 months. If you want a report deleted, email admin@ridgereader.com — include roughly when you sent it and where the photo was taken, since without an email address on the report that is how we find it.

If you would rather not send the photograph, describing the problem by email works too. It is harder for us to act on, but it is a real option.

3. Contributing Photos to Improve RidgeReader (optional)

RidgeReader draws terrain from your phone’s compass and tilt sensors, and those sensors are often wrong — a compass can be off by tens of degrees. We want to build models that correct this automatically, so the terrain view lines up with your photograph, and that recognize avalanche-terrain features in photographs. Training those models needs real photographs taken in the mountains, with the readings the phone recorded at the time. Contribute is how you can choose to provide them. It is entirely optional: using RidgeReader never requires it, and nothing about the Service changes if you leave it off.

3.1 It is off unless you turn it on

• Contribute is off by default. It is not part of accepting our Terms of Use, and it is never turned on for you.
• It is available only in the RidgeReader iOS application, and only when you are signed in — and therefore only to account holders aged 18 or older (Section 13). We are making it available gradually; if you don’t see it in your account settings, it isn’t available to your account yet.
• You turn it on in your account settings. Before it takes effect, a screen lists exactly what will be sent, including that it sends your precise location. Turning it on is your consent to the collection and use described in this section.
• While it is on, the camera screen shows that it is on.
• You can choose to send contributions only over Wi-Fi. Until then they wait on your device (Section 1.5).
• You can turn it off at any time, in the same place. Turning it off stops all future contributions immediately and discards any not yet sent. Signing out turns it off too.

3.2 What is contributed

Only photographs you take with RidgeReader’s camera while Contribute is on. Photographs you select from your device’s photo library are never contributed, and nothing taken before you turned Contribute on is sent.

For each such photograph we receive:

• The photograph, prepared on your device before it is sent, the same way as a report (Section 2): made smaller (at most 2,048 pixels on its longest side), with the faces it detects blurred and the data embedded in the image file removed. Detection can miss a face that is very small or far away. If the photograph can’t be prepared, it is not contributed.
• Where you were: the precise GPS position your device reported when you took the photograph, the device’s own estimate of that position’s accuracy, and how recent the position fix was. We keep this precise rather than rounding it, because the purpose is to correct pointing errors of a few degrees, and at the distance of a nearby slope a rounded position would cause errors larger than the ones we are trying to correct.
• How the phone was held: compass heading, pitch, and roll as your phone’s sensors measured them, with the compass’s own accuracy estimate where your device provides one, whether the heading is a true compass bearing, and how recent the reading was. These are the raw readings; adjustments you make to the view afterwards are not sent.
• The image’s dimensions and the camera’s field of view — or, where your phone doesn’t report it, the value the application assumes, marked as assumed.
• The time the photograph was taken.
• How many faces were blurred.
• Your device model and operating system version, because sensor errors differ between phone models.
• Which terrain was used: the identifier and version of the terrain region the view was drawn from.
• Your account identifier, so that you can withdraw and so that we can delete your contributions on request or when you delete your account.

What is not contributed: the slope statistics and terrain view you were shown, any adjustment you make to the view, your routes and zones, photographs from your library, reports (Section 2), and anything from a time when Contribute was off.

3.3 How contributions are protected

• Faces are blurred on your device, before the photograph is sent. The unblurred photograph never leaves your phone. We detect faces only to blur them: we do not recognize or identify anyone, and we do not create or keep any record of facial geometry.
• Embedded metadata is removed from the image on your device; the location and readings travel as separate fields, so the image file itself carries no location.
• Contributions are stored privately, separately from reports, under access rules that allow the application to send them but not read them back, and they are accessible only to the people at RidgeReader who build and evaluate our models.
• Terrain snapshots. Because terrain is periodically rebuilt, we keep a copy of the terrain region each contribution refers to, so a model can be trained against the terrain as it was. Terrain files are public elevation data and contain no Personal Information.
• Precise location is sensitive. Combined with a time, a precise location can reveal where a person was. We treat contributions accordingly: we do not describe them as anonymous, and we do not publish or share them.

3.4 How contributions are used

Contributions are used only to train, test, and improve RidgeReader’s own models for:

• correcting compass and tilt errors, so that the terrain view lines up with the photograph; and
• recognizing avalanche-terrain features in photographs.

They are used in-house only. We do not sell contributions, license them, share them with research partners, or provide them to third-party AI or machine-learning services for those services’ own purposes. They may be processed on computing infrastructure we rent, under terms that prohibit the provider from using them for any purpose of its own; any such provider will be listed in Section 7.1 before it is first used. We do not use contributions for advertising or marketing, and we do not publish them. We may publish aggregate results — for example, how much a model reduced compass error — that contain no photographs, locations, or other information about any contributor. Reports (Section 2) are never used as contributions.

3.5 Withdrawing and deleting

• Stop contributing: turn Contribute off (Section 3.1).
• Delete what you have contributed: use “Delete my contributions” in your account settings, or email admin@ridgereader.com. We delete your contributed photographs, their readings, and the labels derived from them within 30 days, apart from residual backup copies that are overwritten in the ordinary course (Section 8).
• Deleting your account deletes your contributions in the same way.
• Models already trained are not retrained. A model learns general patterns from many photographs and does not store any photograph in a form that can be retrieved from it. Once your contributions are deleted they are not used to train any future model, but models trained before your deletion request are not retrained or withdrawn.

4. Accounts and Route Sync

Signing in is optional and is not required for any terrain or analysis feature. Its main purpose is to carry your work between your devices: a route drawn on a laptop appears on a phone at the trailhead. Signing in also makes Contribute available (Section 3).

What is stored in your account. When you are signed in, the application stores a single document containing your zones and drawn objects — their coordinates, names, colors, type, grouping, and the timestamps of your edits — together with records of items you have deleted, which are retained so that a deletion made on one device is not undone by another device that has not yet synchronized. This document is stored by our authentication and database provider, Supabase, and is protected by database-level access rules that permit only your own signed-in session to read or write it.

What is not stored in your account. Downloaded terrain data is not synchronized and is never uploaded. It is large, it is re-downloadable from us at any time, and it stays on each device. A zone that appears on a second device will offer to download its terrain there.

Signing out does not delete the routes on that device. They remain available locally, exactly as they would be for a user who had never signed in. Signing out turns Contribute off and discards any contributions not yet sent.

When you are signed out, no routes, drawings, or contributions are transmitted to us at all, except the geometry contained in a custom terrain request you specifically make (Section 1.3).

5. Server-Side Terrain Cache

To avoid repeatedly retrieving the same elevation data, we cache derived elevation and slope data on our servers.

• Cached terrain for automatically generated regions is keyed to an anchor point and compass sector, not to you. The cache key is the requested point rounded to a 0.001-degree grid (roughly 110 meters) together with a compass sector, and the cache entry contains no account identifier, session identifier, or other Personal Information. Because a key reflects approximately where a request came from, we treat cache keys as location information: we do not publish them, and entries that go unused are cleared on a rolling basis.
• Cached terrain for custom regions is keyed to a hash of the geometry you submitted. The stored terrain file itself is public geospatial data, but the identifier is derived from your drawing.
• Cached terrain is derived from government elevation sources. The same cache entry is reused for any user requesting the same area.
• Cache entries may be cleared by us at any time. Copies kept for contributions are described in Section 3.3.

6. How We Use Information

We use the information we collect to:

• Generate and deliver the terrain data you request
• Retrieve elevation data for the area you have asked us to build
• Authenticate you and synchronize your routes across your devices, if you have signed in
• Train, test, and improve our own models from contributions, if you have turned on Contribute (Section 3)
• Provide customer support and respond to your inquiries
• Monitor Service performance and reliability, and diagnose errors
• Enforce rate limits and detect, investigate, and prevent abuse, security incidents, and violations of our Terms of Use
• Communicate with you about your account and material changes to the Service
• Comply with legal obligations and respond to lawful requests
• Process payments and manage subscriptions, if you purchase a paid plan in the future
• Produce aggregated and de-identified statistics, such as which regions are most frequently requested, to prioritize terrain coverage

Aggregated and de-identified information is not associated with you, and we take reasonable steps to keep it that way.

7. How We Share Information

We do not share information about you except as described below. We do not sell your Personal Information, and we do not share it for cross-context behavioral advertising.

7.1 Infrastructure and service providers

These vendors process information on our behalf and are not permitted to use it for their own purposes:

7.2 Elevation data providers

To build terrain, our servers query public elevation data sources — including the U.S. Geological Survey and the Microsoft Planetary Computer — for the geographic area being built. These queries transmit the coordinates of the area requested. For automatically generated regions, the area queried is the region built around the anchor point described in Section 1.3, not your precise coordinates. For custom regions built from your drawings, the area is derived from your route geometry at full precision. These providers do not receive your account identifier, email address, or any photograph. Their handling of request data is governed by their own privacy policies.

7.3 Third parties your browser contacts directly

The following are requested by your browser rather than by our servers, which means these providers receive your IP address directly from you, along with what you requested:

We do not control these providers and do not receive the data they collect.

7.4 Other disclosures

Payment processor. If a paid tier is introduced, billing information will be shared with a payment processor to process payments.

Legal and safety disclosures. We may access, preserve, and disclose information where we believe doing so is required or appropriate to comply with law or legal process (such as a subpoena or court order), to enforce our Terms of Use, to detect and prevent fraud or security incidents, or to protect the rights, property, or safety of RidgeReader, our users, or the public. Where permitted by law, we will make reasonable efforts to notify you of legal requests for your data.

Business transfers. If we are involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, your information may be transferred as part of that transaction. We will make reasonable efforts to notify you if your Personal Information becomes subject to a different privacy policy.

With your consent. We may share information for other purposes with your permission.

8. Data Retention

After deletion, residual copies may persist in backups for a limited period before being overwritten.

9. Cookies and Similar Technologies

The Service does not use advertising or analytics cookies. It does not use a cookie consent banner because it sets no optional cookies.

The Service stores the following on your device using browser storage mechanisms rather than cookies:

• Authentication token, if you have signed in, so that you are not asked to sign in on every visit
• Terms of Use acceptance, so you are not asked repeatedly
• Interface preferences, such as your last-used map layer and whether Contribute is on
• Downloaded terrain data, your routes, and contributions waiting to be sent, as described in Section 1.5

You can clear all of the above through your browser or device settings. Doing so will sign you out and delete downloaded terrain and any unsent contributions, and — if you are not signed in — will delete your routes.

There is no accepted industry standard for responding to browser “Do Not Track” signals, and the Service does not currently respond to them.

10. Your Choices

• Use the Service without an account. Every terrain and analysis feature works signed out.
• Location. You can decline or revoke location permission through your device or browser settings. Features that depend on your live position — in-app photo capture, centering the map on you — will not work; analyzing an uploaded photograph does not require it.
• Photo metadata. You can strip EXIF data before selecting a photograph, or enter coordinates manually. In ordinary use this has no effect on what we receive, because analysis never sends the photograph — and reports and contributions never carry a photo’s embedded data either: it is removed on your device before sending, and the location goes as a separate field.
• Reporting. Sending a report is always your choice, nothing is sent until you confirm, and a report can be deleted on request (Section 2).
• Contribute. Off unless you turn it on; you can limit it to Wi-Fi, turn it off at any time, and delete what you have contributed (Section 3).
• Offline data. You can delete downloaded terrain at any time through the Service's region manager, or by clearing your browser or application storage.
• Sync. Sign out to stop synchronizing. Your routes remain on the device.
• Marketing email. Should we send promotional messages, you will be able to unsubscribe using the link in any such message. You will continue to receive service-related and transactional messages.
• Account deletion. You can delete your account and associated account data within the Service. If you cannot use that option, contact us at admin@ridgereader.com. Deleting your account deletes the routes stored in it and your contributions; copies already on your devices remain there under your control.

11. Your Privacy Rights

We honor reasonable requests from U.S. users to access, correct, or delete Personal Information we maintain about them, including contributions. To make a request, email admin@ridgereader.com with the subject line “Privacy Request” and tell us whether you seek access, correction, or deletion. We may request information needed to verify that you are the person whose information is involved. We use verification information only for that purpose.

We do not sell Personal Information or share it for cross-context behavioral advertising. We do not use precise geolocation for advertising or to infer characteristics about you. We use it only to provide the terrain, account, or diagnostic-report feature you requested, or — if you turn on Contribute — to train and test our own models as described in Section 3, as described in this Privacy Policy. Because we do not sell or share Personal Information for advertising, we do not provide a “Do Not Sell or Share My Personal Information” or “Your Privacy Choices” link.

These rights are offered voluntarily to all U.S. users. If a law gives you additional rights, nothing in this policy limits those rights.

12. Security

We use technical and administrative safeguards designed to protect the information we maintain, including encryption of data in transit, database-level access rules that restrict each account's synced data to that account, and restricting administrative access to personnel who need it.

Because slope analysis runs on your device, the categories of information most sensitive to you are not exposed to us in ordinary use. The exceptions are contributions, if you turn on Contribute (Section 3), and a report you choose to send (Section 2), which carries a copy of the photograph, prepared on your device with the faces it detects blurred and its embedded data removed, and the location as a separate field; contributions and reports are stored under access rules that allow them to be created but not read back through the application.

However, no method of transmission or storage is completely secure. We cannot guarantee the absolute security of your information, and any transmission of data to the Service is at your own risk. If we become aware of a security breach affecting your Personal Information, we will notify you and any applicable regulators as required by law.

13. Children's Privacy

We do not knowingly collect Personal Information from children under 13. Children under 13 may use the ordinary terrain, mapping, and on-device analysis features without an account. They may not create an account or, without a parent or legal guardian, submit a diagnostic report, join the waitlist, or contact support. If we learn that we collected Personal Information from a child under 13 without appropriate parental involvement, we will delete it.

Accounts are limited to adults. You must be 18 or older to create a RidgeReader account. No account is required to use the Service. Contribute requires an account, and is therefore available only to adults.

We rely on the age representation made when an account is created. If you believe a child under 13 has provided us with Personal Information, contact us at admin@ridgereader.com.

14. Third-Party Sites and Data

The Service displays and links to information from third parties, including avalanche forecast centers, map tile providers, and public elevation data providers. This Privacy Policy does not apply to those third parties. We encourage you to review their privacy policies before providing information to them.

15. International Users

The Service is intended for users in the United States, and its terrain coverage is limited to United States elevation data. Our infrastructure is not located in a single country. Account information and synced routes are stored by Supabase in Canada; our terrain generation backend runs in the United States, and terrain files are stored in North America, primarily the United States. Canada is recognized by the European Commission as providing an adequate level of data protection.

By using the Service, you consent to your information being transferred to, stored in, and processed in the United States and Canada, where privacy laws may differ from those in your jurisdiction.

At launch, the Service is offered only in the United States, and app store availability is limited accordingly.

16. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. The revised version takes effect when posted to this page. If we materially change how we use or share previously collected Personal Information, we will notify you through the Service, by email, or by other reasonable means.

17. Contact

Questions, comments, or concerns about this Privacy Policy or our privacy practices:

Email: admin@ridgereader.com Mail: Alpha Angle Labs, LLC, 1500 N Grant St, Suite #11862, Denver, CO 80203, USA