Privacy Policy

Plain-Language Summary

ExploraVist builds assistive technology — including a wearable device and a companion iOS app — for people who are blind or visually impaired. This Privacy Policy applies to the ExploraVist iOS app. Here is what you need to know about your privacy:

• Your face templates, photos, and notes stay on your device. The AI models that recognize faces, process depth, recognize objects, and search your photos run entirely on your iPhone — on every iPhone we support. Scene description also runs on your iPhone if it has enough memory for the on-device model; on iPhones that do not, scene description is available only through the optional Cloud descriptions setting described below. Your data is never uploaded unless you choose otherwise.
• You control cloud features. Scene description can optionally be processed in the cloud. This is off by default — it runs only if you turn it on, and you can turn it off again at any time in Settings → Cloud descriptions.
• We do not sell your data. We do not advertise to you. We do not share your data with data brokers.
• We store analytics and crash reporting. Our cloud services receive usage events and crash reports to help us improve the app.
• Your face templates never leave your device. The face templates used to recognize people you enroll are created and stored only on your iPhone, are excluded from backups, and are never shared with anyone. The names you assign are also stored on your device — but if you turn Cloud descriptions on, a name can be sent with an image to produce a description. Section 4 explains this in full.

Full details are in the sections below. If you have questions, contact us at exploravist@exploravist.net.

1. Who We Are

ExploraVist Inc ("we," "our," or "us"), located at 2261 Market Street STE 85134, builds assistive technology for people who are blind or visually impaired, including a wearable device and a companion iOS app.

The ExploraVist iOS app helps users understand their surroundings through on-device artificial intelligence, scene description, face recognition, and voice-driven interaction.

Scope of this policy. This Privacy Policy describes how we handle information in connection with the ExploraVist iOS app. A separate privacy policy governing our wearable device will be published as that product matures; until then, this policy does not cover the wearable.

Data controller for GDPR purposes: ExploraVist Inc., 2261 Market Street STE 85134, San Francisco, CA. EU representative (if required under GDPR Article 27): Not applicable.

For all privacy questions, requests, or complaints, email privacy@exploravist.net. We will respond to privacy requests within 30 days of receipt.

2. Our Privacy Principles

ExploraVist is built on an on-device-first architecture as a deliberate privacy-protective design choice. The machine learning models at the core of the app — depth estimation, face recognition, object recognition, and semantic search — run entirely on your device without sending data to any server. Face recognition and face enrollment run on your iPhone on every device we support, with no cloud path at all. Your most sensitive data stays on your iPhone: your face templates and your notes never leave it under any setting, while your photos and the names you assign to enrolled people leave it only if you turn Cloud descriptions on (Sections 3.6 and 4.4).

Scene description depends on your iPhone's hardware. On iPhones with enough memory to run our on-device description model, descriptions are generated on your device and work fully offline. On iPhones that cannot run that model, scene description is available only through Cloud descriptions — an optional setting that is off by default (Section 9.3) — and is not available offline. All other core features work fully offline on every supported iPhone.

We do not sell your data. We do not use your data for advertising. We do not share your data with data brokers.

3. Information We Collect

3.1 Account Information

Source: Directly from you at sign-in.

When you create an account or sign in, we collect:

• Name — provided via Apple Sign-In, Google Sign-In, or entered directly
• Email address — used to identify your account and for account-related communications such as password reset emails

You may use ExploraVist in guest mode without creating an account. In guest mode, no account information is collected. Usage analytics (Section 3.4) still run in guest mode but without a linked identity.

3.2 Device and Account Identifiers

Source: Generated automatically when you first sign in.

• Firebase User ID — a unique identifier assigned by Firebase Authentication to your account, used to authenticate your session
• Device name and device ID — your device's name (e.g. "James's iPhone") and a generated HMAC credential sent to our servers when you first sign in, solely to authenticate your device for API access

3.3 Location

Source: Directly from you, only when you choose to attach location to a note.

When you create a note and opt to include your location, we collect:

• GPS coordinates (latitude and longitude)
• A human-readable address derived by reverse-geocoding those coordinates

Location data is stored only on your device in the app's private database. Coordinates are never transmitted to our servers or to any third party. We request location access only while the app is in use ("When In Use" authorization). Location is never collected automatically or in the background.

3.4 Usage Data

Source: Collected automatically while you use the app.

We use Firebase Analytics (operated by Google LLC) to collect information about how you use the app, including:

• Screens viewed
• Features used (scene description, voice search, face enrollment, note creation, photo saving)
• Whether features succeed or fail, and how long they take
• Whether Cloud descriptions is enabled and which AI model is active
• Whether VoiceOver is running
• Whether camera, microphone, and location permissions were granted or denied

This data is linked to your Firebase installation ID, which is tied to your account if you are signed in. In guest mode, events are logged without an account identifier.

In addition to Firebase, we collect the same usage information through our own first-party telemetry system, which sends usage events directly to ExploraVist's servers over an encrypted connection. This includes the events listed above, screen views, and app session start and end times, along with basic technical context: your app version and build number, your iOS version, and your device model (e.g. "iPhone17,2"). These events contain only structured, non-identifying values — for example, search telemetry records the length of a search query, never the text you searched for. First-party telemetry is linked to your device credential, which is tied to your account when you are signed in. Usage analytics are integral to operating, securing, and improving ExploraVist and are collected for all users as part of providing the service.

3.5 Diagnostic Data

Source: Collected automatically when the app crashes or encounters an error.

We use Firebase Crashlytics and Firebase Performance Monitoring (both operated by Google LLC) to detect and fix crashes and performance problems. This includes:

• Crash reports and stack traces
• Non-fatal errors
• App performance measurements (e.g. how long scene description takes)
• Contextual information at the time of a crash: the last screen visited, camera and microphone permission states, whether VoiceOver was running, and which AI model was active

App errors are also reported to ExploraVist's own servers through our first-party telemetry system. These error reports contain only technical identifiers — the error category, type, code, and the location in the app where it occurred — and never include error message text or other free-form content. Diagnostic reporting is part of the app's standard operation and is collected for all users.

3.6 Camera and Photos

Source: Directly from you via the device camera.

The camera is used continuously while the Explore feature is active to provide real-time scene description. Camera frames are processed on-device by our AI models. Frames are not stored or transmitted unless you explicitly save a photo or have Cloud descriptions turned on.

In-app gallery: Photos you save are stored in the app's private on-device database. They are not saved to your iPhone's Photos library and are not accessible to other apps.

Cloud descriptions (off by default, you choose to turn it on): Cloud descriptions is off until you enable it, either in the one-time setup the app shows once or in Settings → Cloud descriptions. While it is on, images are uploaded to our servers over an encrypted connection and processed by Google's Gemini models on Vertex AI to generate a richer description. Images are not retained by our servers beyond the duration of the request. You can turn it off again at any time in Settings → Cloud descriptions.

Description editing: When you use your voice to edit a photo description, your speech is transcribed by Apple's on-device speech recognition engine and the updated description is saved in the app's private on-device database. Nothing is transmitted — no audio, no text, and no image leaves your iPhone during this step.

Recognition integration: While Cloud descriptions is on, the names of recognized people and detected objects may be sent to our servers to produce a more natural description — in the context data accompanying the request, in the text prompt, and as a name label drawn on the image that is sent. This means the names you assigned to enrolled people may be transmitted when this feature is used. The underlying face templates are never transmitted. See Section 4.4.

3.7 Voice and Microphone

Source: Directly from you when you use voice features.

The microphone is used for:

• Voice search — to find photos in your gallery by spoken description
• Note dictation — to create notes by speaking
• Description editing — to edit a saved photo description by speaking

Speech recognition is performed entirely on your device using Apple's on-device speech recognition engine (requiresOnDeviceRecognition is set to true). Audio is never sent to Apple's servers or to our servers. Only the resulting text transcript is stored or acted on. Raw audio is never saved to disk by the app.

3.8 Notes

Source: Directly from you via voice dictation.

Notes you create are stored as text in the app's private on-device database, optionally with an attached location (see Section 3.3). Note content is never transmitted to our servers or to any third party.

3.9 Face Data

Source: Directly from you when you choose to enroll a person.

ExploraVist can learn to recognize people you choose to enroll. Doing so creates face data of two kinds, which we keep distinct throughout this policy because they are handled differently: the face template computed from camera images, which never leaves your iPhone, and the assigned name you give that person, which is stored on your iPhone but can be transmitted if you turn on Cloud descriptions.

Because face data is sensitive, everything about it is described in one place: Section 4, Face Data. That section covers what we collect, how it is used, where it is stored, whether it is shared, how long it is kept, and how you delete it.

3.10 Bystander Privacy

When you use ExploraVist's camera-based features in public or shared spaces, the camera may capture images of people who have not consented to being photographed. We have designed ExploraVist to minimize privacy risks to bystanders:

• Camera frames are processed on-device and discarded immediately — they are not stored unless you explicitly save a photo
• While Cloud descriptions is on, images uploaded to our servers are processed to generate a description and are not retained afterward
• We do not attempt to identify bystanders using face recognition — the face recognition feature only matches against people you have explicitly enrolled
• We do not transmit bystander images to any third party for identification or profiling purposes

Users are responsible for using ExploraVist in a manner consistent with applicable laws and reasonable expectations of privacy in their jurisdiction.

4. Face Data

Face data is sensitive, so this section describes every part of how ExploraVist handles it: what we collect, how it is used, where it is stored, who it is shared with, how long it is kept, and how you delete it. This section applies to the ExploraVist iOS app.

4.1 What Face Data We Collect

Source: Directly from you, only when you choose to enroll a person.

ExploraVist collects two kinds of face data, and only when you deliberately enroll someone. They are handled differently, so this policy names them separately rather than making one promise about both:

• The face template — the biometric part. When you enroll a person, an AI model running on your iPhone converts camera images of that person's face into a face template: a list of 512 numbers that describes the geometry of the face. A face template is not a photograph: it cannot be displayed, and ExploraVist has no ability to reconstruct an image of anyone from it. Face templates never leave your iPhone.
• The assigned name — ordinary text, not biometric. The name you type for that person, so the app can tell you who it recognizes. It is stored on your iPhone, but unlike the face template it can be sent off your device if you turn on the optional Cloud descriptions setting, as Section 4.4 explains.

How to read the rest of this section. Where we say face template, the statement is about the biometric template only. Where we say assigned name, it is about the name only. We use face data as a collective term only where a statement is true of both.

Enrolling a person is always something you start yourself, from the People screen. Before your first enrollment, the app shows a consent screen explaining that face templates are created and stored only on your iPhone, and you must accept it to continue.

The camera images captured during enrollment are held in your device's memory only for as long as it takes to compute the face template, and are then discarded. The App Store version of ExploraVist never saves enrollment images to storage.

We do not collect face data about anyone you have not enrolled. Faces that the camera sees while you use the app are not enrolled, not stored, and not turned into saved templates.

4.2 How We Use Face Data

Face templates are used for exactly one purpose: recognizing, on your device, the people you have chosen to enroll — so the app can tell you who is in front of you, and can label the people it recognizes in photos you save. Recognition runs entirely on your iPhone.

We do not use face data:

• To identify strangers, bystanders, or anyone you have not enrolled
• For advertising, marketing, profiling, or cross-app tracking
• To train, fine-tune, or improve our AI models or any third party's AI models (see Section 6)
• For any purpose other than the recognition features you choose to use

4.3 Where Face Data Is Stored

Face templates are stored in a private index file, and assigned names are stored in a private database. Both live inside the app's own sandboxed storage on your iPhone, which other apps cannot read. Neither is saved to your iPhone's Photos library.

A third place face-related information can live is your saved photos. When you save a photo that contains someone you have enrolled, the photo itself is stored in the app's private on-device gallery, and that person's name is stored with it so you can search for and hear who is in the picture. Those photos and names stay on your iPhone; deleting a photo deletes both.

Face templates are stored only on your device. They are not stored on ExploraVist servers, not stored by Google, and not stored in iCloud or any other cloud service. There is no account-linked copy of your face templates anywhere.

Assigned names are also stored only on your device — we keep no server-side list of the people you have enrolled. A name is nevertheless the one part of your face data that can be transmitted: while the optional Cloud descriptions setting is on, a name can be sent off your device to produce a description. Section 4.4 sets out exactly when that happens and what is sent.

Face templates are excluded from backups. The app marks the files that hold your face templates as excluded from iCloud and device backups, so a template is never copied into an iCloud backup or an encrypted computer backup, and does not transfer to a new device when you restore one. If you move to a new iPhone, you enroll people again.

Assigned names are not excluded from backups. Unlike face templates, the names you assign to enrolled people are stored in the app's ordinary on-device database alongside your photos and notes, and that database is included in an iCloud backup or an encrypted computer backup if you use one. The same is true of the photos you save, which may contain images of people you have enrolled and which store their names alongside them. Backups made by Apple or by your computer are protected by those systems, not by us — if you would rather they were not backed up at all, you can turn off iCloud Backup for ExploraVist in iOS Settings, or delete the people and photos in question.

4.4 Whether Face Data Is Shared

Face templates are never shared with anyone. They never leave your device. They are not uploaded to ExploraVist's servers, not sent to Google or to Vertex AI, and not sold, rented, or disclosed to any third party, data broker, or advertiser — under any setting or subscription. Because we never receive your face templates, we cannot hand them to law enforcement or anyone else; we do not have them (see Section 7.5).

The names you assign are treated differently, and you control this. Cloud descriptions is an optional feature that is turned off by default; it is on only if you turned it on, either in the one-time setup the app shows once or in Settings. While Cloud descriptions is on, and only then, a camera image that contains someone you have enrolled may be sent to our servers together with that person's name, which our servers pass to Google's Gemini models on Vertex AI to produce the description. When this happens depends on your iPhone: on iPhones powerful enough to run our on-device description model, it happens when you save a photo, and the name can appear in three forms — as a field in the context data accompanying the request, inside the text prompt, and as a visible name label drawn on the image that is sent. On iPhones that cannot run that model, where the cloud is the only way to describe a scene at all, it happens each time you ask for a description, and the name is sent only inside the text prompt — no label is drawn on the image and no context data is sent. What is sent in that case is a camera image and a name — never a face template.

Turning Cloud descriptions off in Settings stops this entirely: while it is off, no image and no assigned name is sent anywhere, on any iPhone. What happens to scene description itself then depends on your hardware, exactly as described in Sections 2 and 9.3 — on iPhones with enough memory to run our on-device description model, descriptions are produced on your device; on iPhones that cannot run that model, scene description is unavailable while the setting is off.

Analytics. When you save a photo, we send our analytics providers a count of how many faces were detected and whether a face was matched to an enrolled person. These events never include a face template, a face image, or a person's name.

4.5 How Long Face Data Is Retained

Face templates and assigned names are kept until you delete them. There is no fixed retention period and no automatic expiry. Both remain on your iPhone for as long as the person stays enrolled and the app stays installed. Signing out of your account does not delete them; they stay on your iPhone until you delete the person, delete all face data, delete your account, or delete the app.

Because face templates never leave your device and are excluded from backups, deleting a template on your device deletes it everywhere. We hold no copy of it to retain, expire, or delete on our side.

The same is true of the stored copy of an assigned name: deleting it on your device leaves us with no stored copy. The one thing deletion cannot reach backwards is a name already transmitted for a description while Cloud descriptions was on — that is covered immediately below.

An assigned name sent under Cloud descriptions (Section 4.4) is used to produce that one description and is not retained by our servers afterwards. It is processed by Google as our processor on Vertex AI, under the Google Cloud terms described in Sections 6 and 7.4. Google does not use it for training and does not retain the content of ordinary requests. The single exception is Google's abuse monitoring: if its automated safety systems flag a request, Google may log it and, per Google, store it securely for up to 90 days, where it may be reviewed by authorized Google employees. So the honest answer for an assigned name is that we retain no copy once you delete it, and Google retains none either unless that abuse-monitoring exception is triggered. Face templates are never affected by any of this — they are never sent at all.

4.6 How You Delete Face Data

You can delete face data at any time, without contacting us. Every option below takes effect immediately and permanently — deleted face data cannot be recovered, and there is no cloud copy to restore from.

• Delete one person. Open the People screen, select the person, and choose Delete. This erases that person's face template and removes them from your saved people, so the app stops recognizing them immediately.
• Delete all face data. Go to Settings, then Privacy, and choose "Delete all face data". This erases every enrolled person's face template and name from your iPhone and turns face recognition off.
• Delete your account. Go to Settings, then Account, and choose Delete Account. This erases all on-device data, including every face template and the files that hold them.
• Uninstall the app. Deleting ExploraVist from your iPhone removes the app's private storage, including all face data.

One thing to know about photos you already saved. A photo you saved while someone was enrolled keeps the name that was recorded with it at the time, so your gallery and your searches still make sense after you delete a person. Deleting a person erases their face template and their enrolled record, but not the copy of their name stored with those earlier photos. To remove that too, delete the photos in question, use Delete all face data together with deleting those photos, or delete your account — which erases every photo and every face template on the device.

4.7 Your Consent and How to Withdraw It

Face recognition is off until you set it up. It begins only after you accept the consent screen described in Section 4.1, and only for the people you enroll yourself.

You can withdraw your consent at any time by choosing "Delete all face data" in Settings under Privacy. Withdrawing consent both erases the face data already on your device and turns face recognition off. We record only the date and time consent was given — never any face data — and that record is cleared when you withdraw consent or delete your account.

5. How We Use Your Information

We do not use any of your data for advertising, marketing targeting, or cross-app tracking.

6. AI Model Training

We do not use face data, images, audio, voice queries, notes, descriptions, or any other user-generated content submitted through ExploraVist to train, fine-tune, or otherwise improve our AI models or any third-party AI models. Face templates in particular are never used for training — they never leave your device at all (see Section 4.4).

While Cloud descriptions is on, images and text prompts are processed by Google's Gemini models running on Vertex AI, part of Google Cloud. We use Vertex AI under our Google Cloud enterprise agreement — not the consumer Gemini app or the consumer Gemini API — and Google acts as our data processor under the Cloud Data Processing Addendum.

Under the Training Restriction in Google Cloud's Service Specific Terms, Google will not use customer data to train or fine-tune any AI/ML models without the customer's prior permission or instruction. We give no such permission. This is a contractual commitment in the agreement we operate under, not a default setting that could be switched.

For more information, see Google Cloud's Service Specific Terms, the Cloud Data Processing Addendum, and Google's data governance documentation for generative AI on Vertex AI.

7. How We Share Your Information

We do not sell your personal data. We share data only as described below.

7.1 Google / Firebase

We use the following Firebase services, all operated by Google LLC:

• Firebase Authentication — manages your account credentials
• Firebase Analytics — receives usage events linked to your Firebase installation ID
• Firebase Crashlytics — receives crash reports and diagnostic context
• Firebase Performance Monitoring — receives performance measurements

Google's privacy policy: policies.google.com/privacy. Firebase data processing terms: firebase.google.com/support/privacy.

7.2 Google Sign-In

If you sign in with Google, Google shares your name and email address with us per Google's privacy policy.

7.3 Apple Sign-In

If you sign in with Apple, Apple shares your name and (optionally) email with us. Apple may provide a private relay email address at your discretion.

7.4 Google Cloud Vertex AI (via our servers)

While Cloud descriptions is on, images and text prompts are sent to our servers, which call Google's Gemini models on Vertex AI — part of Google Cloud — to generate descriptions. Our server acts as an intermediary: Vertex AI processes the content and returns a response. Images are not stored by our servers after processing. Editing a saved photo description does not use Vertex AI or our servers — it happens entirely on your device (see Section 3.6).

If the scene contains someone you have enrolled, the name you assigned to that person may be part of what is sent — in the context data, in the prompt text, and as a name label drawn on the image. Your face templates are never sent to Google or to our servers. See Section 4.4.

What Google does with it. Google acts as our processor under the Cloud Data Processing Addendum and does not use this content to train or fine-tune its models (Section 6). Google does not retain the content of ordinary requests. The exception is abuse monitoring: if Google's automated safety systems flag a request as possibly violating its Acceptable Use or Prohibited Use policies, Google may log that request so it can check whether a violation occurred. Google states that such logged data is stored securely for up to 90 days, is not used to train or fine-tune models, and may be reviewed by authorized Google employees. We use Google's global model endpoint, which Google routes to whichever of its regions is available at the time, so we do not select or control the country in which a given request is processed. This is the one circumstance in which an image, or a name you assigned to an enrolled person, could be retained by Google beyond the moment of the request.

7.5 Legal Compliance and Public Safety

We may disclose information we possess if required to do so by a legally binding order, court warrant, subpoena, or applicable statutory law. We may also disclose limited information in good faith where we deem it strictly necessary to:

• Protect the personal safety, rights, or property of our users, the public, or ExploraVist;
• Detect, prevent, or otherwise address fraud, security, or technical vulnerabilities.

Note on technical limitations: Because ExploraVist is engineered with a privacy-first, on-device architecture, the vast majority of your data — including your local photo gallery, note text, precise location tags, and facial recognition profiles — resides exclusively on your device. ExploraVist does not possess, and therefore cannot provide law enforcement or government entities with, data that is stored solely on your iPhone.

7.6 Business Transfers

If we are involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. We will provide notice before your information is transferred and becomes subject to a different privacy policy.

8. Data Retention

9. Your Rights and Choices

9.1 Account Deletion

You may delete your account at any time from Settings → Account → Delete Account. Deleting your account:

• Removes your Firebase Auth record and associated account data
• Removes your device credentials from our servers
• Permanently erases the data held on your device — including every face template and enrolled name, your saved photos, and your notes. You can also delete any of these individually from within the app at any time, and uninstalling the app removes them all.

9.2 Location

Location is never collected automatically. It is requested only when you choose to attach location to a note. You can revoke location permission at any time in iOS Settings → Privacy & Security → Location Services → ExploraVist.

9.3 Cloud Descriptions

Cloud descriptions is off by default. You turn it on yourself, either in the one-time setup the app shows once or in Settings → Cloud descriptions, and you can turn it off again at any time in the same place. While it is off, no image and no enrolled person's name is sent to our servers.

On iPhones powerful enough to run scene description on the device, turning Cloud descriptions off means description and recognition integration run on your iPhone instead. On iPhones that cannot run those models, Cloud descriptions is how description works at all, so turning it off turns the description feature off on that device. Editing a saved photo description is unaffected by this setting — it always happens on your device (Section 3.6).

9.4 Face Data

You can delete an individual enrolled person from the People screen, delete every enrolled person at once from Settings → Privacy → "Delete all face data", or delete all of it along with your account. Deletion is immediate and permanent. Section 4.6 sets out each option, and Section 4 covers our full handling of face data.

9.5 California Residents (CCPA/CPRA)

California residents have the following rights:

• Know — request disclosure of the categories and specific pieces of personal information we have collected, used, or shared in the prior 12 months
• Delete — request deletion of personal information we hold about you, subject to certain exceptions
• Correct — request correction of inaccurate personal information
• Opt out of sale or sharing — we do not sell or share personal information for cross-context behavioral advertising. If this changes, we will provide a "Do Not Sell or Share My Personal Information" link.
• Non-discrimination — we will not discriminate against you for exercising your rights

Categories of personal information collected in the prior 12 months: identifiers (name, email, user ID, device ID); commercial information (none); internet/network activity (usage events, crash logs); geolocation data (coarse/precise location if attached to notes); audio information (microphone used for on-device processing only); biometric information (face templates for the people you enroll, created and held only on your own device — see Section 4); inferences drawn from usage data (none).

Sensitive personal information. Face templates are sensitive personal information under the CPRA. We use them for one purpose only — performing the recognition feature you asked for, on your own device — which is a use permitted without a separate right to limit. We never sell or share them, and we never use them to infer characteristics about you.

To exercise your rights, contact us at privacy@exploravist.net. We will respond within 45 days (extendable by a further 45 days with notice).

9.6 European and UK Residents (GDPR / UK GDPR)

If you are located in the EEA, the United Kingdom, or Switzerland, you have the following rights:

• Access — obtain a copy of personal data we hold about you
• Rectification — correct inaccurate data
• Erasure — request deletion of your personal data
• Restriction — limit how we use your data
• Portability — receive your data in a structured, machine-readable format
• Objection — object to processing based on legitimate interests
• Withdraw consent — where processing is based on your consent

Legal basis table:

To exercise your rights, contact us at privacy@exploravist.net. We will respond within 30 days. You also have the right to lodge a complaint with your local supervisory authority. In the UK, this is the Information Commissioner's Office. In Ireland, this is the Data Protection Commission. For other EU member states, find your authority at edpb.europa.eu.

Data transfers: Firebase services are operated by Google LLC in the United States. Transfers of personal data from the EEA/UK to the US are governed by Google's Standard Contractual Clauses. Our own API servers are located in the United States (Google Cloud Platform, us-central1 region). Because our servers are outside the EEA/UK, transfers of personal data from the EEA/UK to the US are covered by Standard Contractual Clauses.

9.7 US State Privacy Rights (Virginia, Colorado, Connecticut, Utah, Texas, and others)

Residents of Virginia (VCDPA), Colorado (CPA), Connecticut (CTDPA), Utah (UCPA), Texas (TDPSA), and other US states with applicable privacy laws have the right to:

• Access personal data we hold about you
• Correct inaccurate personal data
• Delete personal data you have provided or we have collected
• Obtain a portable copy of your data
• Opt out of the processing of personal data for targeted advertising (we do not conduct targeted advertising)
• Opt out of the sale of personal data (we do not sell personal data)
• Appeal a denial of a privacy rights request

To exercise these rights, contact us at privacy@exploravist.net. We will respond within 45 days (extendable by a further 45 days with notice for complex requests). To appeal a decision, reply to our response email with "Privacy Rights Appeal" in the subject line.

9.8 Canadian Residents (PIPEDA / Quebec Law 25)

Canadian residents have the right to access and request correction of personal information we hold about you. Quebec residents have additional rights under Law 25, including the right to data portability and the right to be forgotten. To exercise these rights, contact us at privacy@exploravist.net.

10. Children's Privacy

ExploraVist is not directed to children under 13 in the United States (or under 16 in the EEA/UK). We do not knowingly collect personal information from children below these age thresholds.

In compliance with the Children's Online Privacy Protection Act (COPPA), we do not knowingly collect, use, or disclose personal information from children under 13 without verifiable parental consent. If you are a parent or guardian and believe your child has provided us with personal information, please contact us at privacy@exploravist.net. We will delete the information within 30 days of verified notification.

The app is rated 4+ on the App Store. Age-appropriate access is enforced at the platform level by Apple's parental controls and App Store age rating system. The app does not independently verify user age at sign-up, and is not directed at children.

11. Security

We use industry-standard security measures including:

• HTTPS/TLS encryption for all data in transit between the app and our servers
• HMAC-SHA256 request authentication to prevent unauthorized API access
• On-device storage in the app's private sandboxed container, inaccessible to other apps
• Account credentials and device secrets stored in the iOS Keychain

No method of transmission or storage is completely secure. We cannot guarantee absolute security but are committed to protecting your data using measures appropriate to its sensitivity.

12. Third-Party Links and Services

ExploraVist does not display advertising or contain links to third-party websites. The only third-party services that receive data from the app are those listed in Section 7.

13. Contact and Accountability

For all privacy questions, requests, or complaints:

ExploraVist Inc
2261 Market Street STE 85134, San Francisco, CA
Email: privacy@exploravist.net
Website: https://exploravist.net

We will acknowledge your request within 5 business days and respond fully within 30 days (45 days for CCPA/US state requests).

If you are an EU/UK resident and are not satisfied with our response, you have the right to lodge a complaint with your local data protection supervisory authority (see Section 9.6 for links).