Privacy Policy — Got Your 6

Effective date: November 8, 2026

Summary (plain-English, not a substitute for the full policy)

• Who we are. Got Your 6 is a personal-safety app operated by Extension Tech Inc., a developer based in Ontario, Canada.
• What we collect. Your phone number, name, optional email and profile avatar, device push tokens, your location (including in the background while Circle sharing or a safety feature is active), the emergency-contact details you enter, Circle messages you send, your safety and relationship activity history, detected device unlock/restart check-in records, and your subscription status.
• Your microphone. Voice-activated SOS listens for your chosen wake phrase entirely on your device. Microphone audio is processed locally, including during voice enrollment; a voice enrollment model is stored on your device. We do not upload microphone audio or that model to our servers or third parties.
• Why we collect it. To deliver safety alerts and live location to the emergency contacts you choose, to run your account, and to operate the subscription.
• Who we share it with. The emergency contacts and mutually agreed Circle members you choose, and processors that deliver messages, run our infrastructure, and help us diagnose failures. We may also disclose limited information where required or permitted by applicable law, including valid legal process and legally permitted safety disclosures described in Section 8. We use Sentry for limited server and staff-console error/performance monitoring. We do not sell your data and we do not use advertising or behavioural-analytics SDKs in the consumer mobile app.
• Emergency contacts are real people. Please only add people who have agreed to be your contact. Emergency-contact SMS requires the recipient’s own recorded opt-in; each recipient can reply STOP independently of the account owner.
• Your choices. You can access, correct, export, or delete your data, and you can delete your account at any time.
• Contact us. Email support@gotyour6.app.

1. About this policy

1.1 This Privacy Policy explains how Extension Tech Inc. ("we", "us", "our") collects, uses, discloses, and safeguards personal information in connection with the Got Your 6 mobile application (bundle identifier app.getyour6.mobile) for iOS and Android and its related server services (together, the "Service").

1.2 We are based in Ontario, Canada. Our handling of personal information is governed primarily by Canada's Personal Information Protection and Electronic Documents Act (PIPEDA). Because the Service is distributed globally through the Apple App Store and Google Play, this policy also addresses rights available under the EU/UK General Data Protection Regulation (GDPR) and the California Consumer Privacy Act / California Privacy Rights Act (CCPA/CPRA). See Sections 9–11.

1.3 By creating an account or using the Service, you acknowledge the practices described here. If you do not agree, please do not use the Service.

2. A note on the nature of this app

Got Your 6 is a safety tool. To do its job, it necessarily processes sensitive information — most importantly your location, including while the app runs in the background during an active safety feature. We have designed the Service to collect this information only when a safety feature you have turned on requires it, and to share it with the contacts you have chosen and as otherwise described in Section 8, including service providers and legal and safety disclosures. We describe exactly when this happens in Section 4.

3. Information we collect

We collect the following categories of personal information. We do not collect more than we need to operate the Service.

3.1 Information you provide

3.2 Information collected automatically

3.3 Microphone audio — processed on-device only

If you enable Voice-activated SOS, the app listens through your microphone for a wake phrase you choose. This listening happens entirely on your device using an on-device wake-word model. During voice enrollment, the app captures and processes your spoken samples locally to create a voice enrollment model used by the detector. That model is stored on your device. We do not upload microphone audio or the enrollment model to our servers or third parties. A successful detection can trigger an SOS, which sends the safety-event information and location described in this Policy. You can disable this feature at any time, and it requires microphone permission that you control in your device settings.

Activity timestamps. Event time is the activity time recorded by the device; received time is when the server receives the upload. On iOS, restart time is estimated from device uptime, and unlock time reflects when the app observed the unlock, which may be later than the physical unlock. Some events may be missed entirely. These records are not a complete or exact log of phone use, and receipt of an event does not necessarily mean it reset the inactivity timer. See Terms Sections 3.8–3.12.

3.4 What we do NOT collect

• We do not run advertising or behavioural/product-analytics SDKs in the consumer mobile app. Sentry is used for limited operational error and performance monitoring as described in Section 8.1, not to build advertising profiles or analyze consumer behaviour for marketing.
• We do not serve advertising or use advertising identifiers for ad targeting.
• We do not collect or receive your payment-card details — all payments are handled by Apple or Google (see Section 8).
• We do not continuously track your location. Location is collected only during an active safety feature.

4. When location is collected and shared

Location is central to the Service, so we want to be precise about it.

• SOS button. When you trigger an SOS, the app captures your location. After a short cancel window (a few seconds, during which you can abort), the app alerts your emergency contacts with your location and then continues to share your live location with them until you end the session.
• "Track me" (live location sharing). When you start a Track me session, the app shares your location with your contacts at an interval, in the foreground and background, until you stop it.
• Dead-man's switch (inactivity check). If you enable this feature and the server does not receive and accept a qualifying check-in within your configured inactivity window, the Service may alert your contacts with your last known location after a grace period. Free users must check in manually; Guardian Plus may also use supported automatic activity signals. Using, unlocking, or restarting your phone does not guarantee a check-in. Background execution, permissions, and connectivity affect detection and upload, and location availability depends on your settings. See Terms Sections 3.8–3.12.
• Watch circle. If you and another user mutually accept an invitation, you share live location with each other while the feature is active. This is consent-based and mutual — a person must accept your invitation before they receive any location point, and either side can exit at any time. Both people are notified when either person exits, and mutual circle-location sharing ends. Exiting does not remove the separate emergency-contact relationship or stop its alerts.

Live location shared with non-app contacts may be delivered via an expiring share link so they can view your position without installing the app; such links expire after a limited period.

You can stop location sharing at any time by ending the relevant session, and you control location and background-location permissions through your device's operating-system settings. Revoking OS permissions can prevent safety features from working — see the safety disclaimer in our Terms of Service.

5. Why we use your information (purposes and legal bases)

We use personal information to:

1. Provide the core safety features — deliver SOS alerts, live-location updates, dead-man's-switch alerts, and watch-circle sharing to the contacts you choose.

2. Operate your account — authenticate you by OTP, maintain your profile, and verify your email.

3. Send transactional messages and show activity history — SMS, email, and push notifications that are part of the Service, and a signed-in timeline of safety incidents and contact or watch-circle changes.

4. Operate the subscription — recognize your Guardian Plus status and gate premium features.

5. Maintain security and integrity — protect accounts, prevent abuse, and keep the Service reliable.

6. Diagnose and respond to incidents — identify software errors, failed provider operations, degraded performance, and security or availability problems; correlate related failures; and validate recovery.

7. Evaluate inactivity and investigate check-ins — use activity event times and acceptance status to calculate inactivity deadlines, prevent duplicate timer resets, and investigate missed, delayed, or incorrect events. Authorized administrators can view check-in history through the staff console for support and operational troubleshooting; access is controlled and history views are audited.

8. Comply with law — meet legal obligations and respond to lawful requests.

Legal bases (GDPR, where applicable). We rely on: performance of a contract (Art. 6(1)(b)) to deliver the Service you request; consent (Art. 6(1)(a)) where consent is the appropriate basis for device permissions and optional features; legitimate interests (Art. 6(1)(f)) for security, abuse prevention, necessary emergency-contact processing, service operation, and proportionate error/performance monitoring, after balancing those interests against affected individuals' rights; and legal obligation (Art. 6(1)(c)) where the law requires. You remain responsible for having permission and lawful authority to provide contact details. Where we rely on consent, you may withdraw it at any time (Section 9), though doing so may disable safety features.

6. Data retention

6.1 We keep personal information only as long as needed for the purposes above or as required by law.

• Location trails from Track me and SOS sessions are transient safety data and are automatically purged a short time after the relevant session ends. We do not maintain a long-term history of your movements.
• Account information (phone number, name, email, contacts, subscription state) is retained while your account is active. After account closure, we delete or anonymize it promptly and within 30 days, rather than retaining it for a mandatory waiting period. We retain only the limited records necessary for legal obligations, financial recordkeeping, SMS consent and suppression, or a specific dispute or legal hold, for as long as that purpose requires.
• Safety and relationship activity history is retained with the associated account for the account-retention period above. Deleting an account deletes the rows belonging to that account, subject to the backup and legal-preservation limits below. A description of an event involving that person may remain in another user's account history where reasonably needed to explain that other user's own contact or Circle change, subject to applicable deletion rights.
• Automatic activity/check-in history is retained on the server for up to 90 days from server receipt, or until the associated account is deleted, whichever occurs first. Deleting the associated account deletes its activity-event records from the active database, subject to backup and legal-preservation limits below. Account data exports include these records. Pending on-device events are queued for retry and removed when acknowledged by the server; an upload is not guaranteed.
• Expiring share links for non-app viewers expire automatically after a limited window. SMS consent invitations expire after seven days.
• SMS consent and suppression records are retained as needed to demonstrate the recipient’s instructions, honor opt-outs, prevent unwanted re-enrollment, and resolve messaging complaints or legal claims. Minimal suppression information may remain after a contact is removed or an account is deleted so that deleting a relationship does not undo STOP. We review retention against these purposes and applicable deletion rights; contact us for access or deletion requests.
• Sentry diagnostic error events are retained for up to 90 days; sampled performance traces and application logs, where enabled, are retained for up to 30 days. A shorter provider or plan retention period may apply. These periods concern active diagnostic data; provider backups follow their separate expiry schedules. Specific records may be preserved where necessary for a legal obligation or a specific dispute or legal hold.
• Voice enrollment is processed locally. The resulting enrollment model remains on the device for voice detection; the app attempts to delete associated enrollment models when you sign out or change accounts. Turning off listening or microphone permission does not itself delete a stored model. We do not retain microphone audio or enrollment models on our servers (Section 3.3).

6.2 The active-system deletion periods above do not mean every backup copy is erased immediately. Some information may persist in protected backups or providers' systems until their separate backup-expiry schedules complete. Backup copies are restricted from ordinary use; if a backup is restored, applicable deletion requests must be reapplied. Contact us for information about backup retention applicable to your data.

7. Emergency contacts — third-party information you provide

When an account owner adds an emergency contact, they provide that person's name, phone number, and optionally email. They must have permission to provide those details. We use the details to maintain the relationship and deliver authorized safety information.

• SMS requires the recipient’s own opt-in. Each seven-day invitation identifies the account owner and the last four digits of the invited number. Selecting I agree records a consent ID, date, method, relationship, number and disclosure version. We retain a hash of the invitation token. Page views and Circle invitations do not grant SMS consent.
• Recipients control SMS. Replying STOP suppresses Got Your 6 safety SMS to that number across emergency-contact relationships. We retain the suppression needed to enforce this choice. A provider's START command alone does not restore application consent; a fresh invitation and opt-in are required. HELP provides assistance. Message frequency varies; message and data rates may apply. We do not send marketing under this consent.
• Other channels are separate. Adding or removing a contact can generate email or in-app notifications. SMS is sent only with valid consent and no opt-out. Safety text preferences are separate from the codes you request to sign in. STOP does not remove a contact or end Circle sharing, email, or push notifications. Ask the owner to remove the contact or contact support@gotyour6.app for assistance and privacy requests. We do not require the owner's permission to honor a valid recipient SMS opt-out or privacy request.
• Account email sharing. After a Circle invitation is accepted, each person can see the other’s current account email, if provided. The shared address updates automatically when changed or removed in the account profile and is used for new safety email alerts. Before acceptance, knowing a phone number does not reveal the account email. Leaving the Circle ends automatic email sharing; independently supplied emergency-contact details remain subject to this Policy.
• Relationship history is visible to the people involved. We record contact additions and removals and watch-circle joins and exits in signed-in activity history. Where both people have accounts, each person's history can include the other person's name and what changed. Owners can see whether their contacts' SMS consent is pending, active, or withdrawn. Non-app contacts do not have an in-app history.
• Your rights apply independently. Emergency contacts can request access, correction, or deletion of the limited information we hold about them through Section 9. We verify the requester's identity and consider legal retention duties and the need to preserve a minimal SMS suppression record.

8. Who we share information with

We share personal information only as described here. We do not sell personal information.

• The emergency contacts you choose — they receive your alerts and location as you have configured.
• Watch-circle members — mutually consented users receive your live location while the feature is active.
• Service providers (processors) who act on our instructions:
• an SMS provider (such as Twilio) to deliver text messages;
• an email provider (such as Postmark or Resend) to deliver email;
• Apple Push Notification service (APNs) and Google Firebase Cloud Messaging (FCM) to deliver push notifications;
• our hosting/database infrastructure (including PostgreSQL and Redis services);
• Functional Software, Inc. d/b/a Sentry for the limited operational monitoring described below.
• Apple / Google for subscription billing (see Section 8 of the Terms).
• Legal and safety disclosures — we may disclose personal information, including location records and associated timestamps that we hold, when required by a valid subpoena, warrant, court or production order, or another binding legal obligation. We may also disclose information without consent where applicable law permits it, including qualifying emergencies or threats to safety. A request from police or another government authority does not by itself require or authorize disclosure. Before responding, we assess the requester’s identity, legal authority, jurisdiction and scope, and limit disclosure to the information legally required or permitted for that purpose. These exceptions do not authorize unrestricted government access to user information.
• Business transfers — if the Service is involved in a merger, acquisition, or asset sale, information may transfer as part of that transaction, subject to this policy.

SMS information and consent. Mobile phone numbers, SMS opt-in data, and consent records are not sold or shared with third parties or affiliates for marketing or promotional purposes. We disclose the minimum needed to messaging, hosting, and other service providers acting on our behalf to deliver and operate the SMS program, maintain consent and opt-out records, and prevent abuse. These processors may not use this information for their own marketing. Other necessary disclosures, such as those required by law, remain subject to this Policy; SMS consent is not permission for another business's marketing.

We do not permit our service providers to use your information for their own purposes.

8.1 Sentry error and performance monitoring

We use Sentry, operated by Functional Software, Inc., as a processor to help identify, investigate, and alert our staff to server errors, failed provider operations, degraded performance, and failures in the staff-only Ops Console. Under the current implementation, Sentry is initialized on our server and Ops Console; it is not initialized in the consumer mobile application. Sentry describes its service as application monitoring designed to identify and alert developers to errors and performance problems. Its current legal documents are available in its Data Processing Addendum, Privacy Policy, and subprocessor list.

Data sent or processed. A Sentry event may contain the diagnostic and operational fields listed in Section 3.2. Because event transmission uses the internet, Sentry and its infrastructure may also process source-IP and connection metadata even where our SDK does not attach an IP address as a user field. Error messages and stack traces are partly unstructured; despite our controls, they could incidentally contain personal information if an unexpected error embeds it.

Our minimization controls. We configure Sentry not to send default PII or local variables. Before an event is sent, our code removes request bodies, cookies, query strings, most request headers, extra context, and non-trace contexts; strips query parameters from URLs; limits retained user information to a pseudonymous internal identifier where present; and redacts recognizable URLs, email addresses, phone numbers or similar identifiers, precise coordinate pairs, and push tokens from common text fields. We do not intentionally send contact lists, alert bodies, authentication secrets, precise location trails, payment details, or microphone audio to Sentry. These controls reduce risk but cannot guarantee that every unexpected value will be recognized or removed.

Purpose and legal basis. We use this processing only for operating, securing, debugging, and restoring the Service, based on our legitimate interests and, where applicable, performance of our contract with you. We do not authorize Sentry to use our Service Data for advertising. Sentry acts as our processor for Service Data under its customer agreement and DPA.

Location, subprocessors, and retention. Our selected Sentry data-storage region is US (Iowa, USA) for region-scoped event data and its backups. Account, organization, and integration metadata may also be stored in the United States. Selecting the US region does not mean all Sentry-related information or processing remains in the United States. Sentry and its subprocessors may process information in other countries as needed to provide infrastructure and support, subject to contractual transfer safeguards. Sentry's current subprocessor list includes infrastructure and affiliated support providers in the United States, Canada, and Europe and may change over time. We retain Sentry events as described in Section 6.

Your rights. Requests to access, correct, delete, or restrict diagnostic data associated with you should be made to us through Section 9. We remain responsible for responding to your request and will use Sentry's available search, deletion, export, and assistance mechanisms where applicable. Sentry's public privacy policy governs information it collects for its own website and customer-account purposes; this Policy governs the Service Data we direct Sentry to process for Got Your 6.

9. Your rights and how to exercise them

Depending on where you live, you have some or all of the following rights:

• Access a copy of the personal information we hold about you.
• Correct inaccurate or incomplete information (you can edit much of it in-app).
• Delete your information and your account (Section 10).
• Export / portability — receive your data in a portable, machine-readable format.
• Withdraw consent — reply STOP for Got Your 6 safety SMS; turn off location features, voice activation, or other notifications through the relevant controls (note this may disable safety features).
• Object to or restrict certain processing.
• Non-discrimination — we will not deny you the Service for exercising your privacy rights.

How to exercise them. Email support@gotyour6.app from the address or phone associated with your account, or use the in-app controls. We will respond within the timeframes required by applicable law (generally 30 days under PIPEDA and GDPR; up to 45 days under the CCPA/CPRA, extendable as permitted). We may need to verify your identity before acting.

Complaints.

• Canada: you may contact the Office of the Privacy Commissioner of Canada (OPC), and, in Québec, the Commission d'accès à l'information.
• EU/UK: you may lodge a complaint with your local data protection authority.
• California: you may contact the California Privacy Protection Agency or Attorney General.

We ask that you contact us first at support@gotyour6.app so we can try to resolve your concern.

10. Deleting your account and data

You can request deletion of your account and associated personal information at any time by using the in-app account controls (where available) or by emailing support@gotyour6.app. On a verified deletion request, we will delete or anonymize your personal information promptly and within 30 days after account closure, subject to the backup limits in Section 6, except where retention is required by law, needed to resolve disputes, or necessary to enforce our agreements. Deleting your account ends its safety features, removes its server-side automatic activity records and contact relationships, subject to the consent-evidence and minimal SMS suppression retention described in Section 6. Note that subscription cancellation is handled by Apple/Google — deleting your account does not by itself cancel an active store subscription (see the Terms).

11. International data transfers

We are based in Canada, and our providers—including Sentry and its subprocessors—may process information in Canada, the United States, Europe, and other countries. Information processed outside your province or country may be accessible to courts, law-enforcement bodies, and national-security authorities under the laws of the destination. Where we transfer personal information across borders, we use providers and safeguards intended to protect it consistent with this policy and applicable law (for EU/UK transfers, mechanisms such as Standard Contractual Clauses, the UK International Data Transfer Addendum/Agreement, the EU-U.S. Data Privacy Framework where valid and applicable, or transfers to jurisdictions covered by an adequacy decision). By using the Service, you understand your information may be processed outside your country of residence.

12. Security

We use technical and organizational measures designed to protect personal information, including encryption in transit, access controls, OTP-based authentication, secure token handling, least-data diagnostic configuration, and redaction before Sentry transmission. No method of transmission, filtering, monitoring, or storage is perfectly secure, and we cannot guarantee absolute security or that an automated scrubber will identify every sensitive value. The Service also depends on third-party networks and processors that we do not control.

13. Data-breach notification

If we become aware of a breach of security safeguards involving your personal information—including a qualifying incident reported by a processor such as Sentry—that creates a real risk of significant harm, we will notify affected users and the appropriate authorities without undue delay and as required by applicable law (including PIPEDA's breach-reporting obligations to the OPC and affected individuals, and applicable GDPR/CCPA timelines). We will keep records of breaches as the law requires. Provider notification to us does not replace our assessment or our legal notification responsibilities.

14. Children's privacy

The Service is not directed to children under 13, and we do not knowingly collect personal information from them. You must be the age of majority in your jurisdiction, or have the consent and supervision of a parent or legal guardian, to use the Service. If you believe a child has provided us personal information, contact support@gotyour6.app and we will delete it.

15. App-store disclosures

This policy is intended to support the privacy disclosures we make on the Apple App Store (including App Store Review Guideline 5.1.1) and the Google Play Data safety form. It identifies the data we collect, including diagnostic data where applicable, why we collect it, the third parties involved, our retention approach, and how you can request deletion. Store disclosures must be updated if our Sentry deployment or any other production data flow changes. If there is any conflict between a store's summary label and this policy, this policy governs our actual practices, subject to rights that cannot lawfully be waived.

16. Changes to this policy

We may update this policy from time to time. If we make material changes, we will update the effective date above and, where appropriate, notify you in the app or by another reasonable means. Your continued use of the Service after an update means you accept the revised policy.

17. How to contact us

Extension Tech Inc.

Privacy contact: Jack Chen, CTO

Email: support@gotyour6.app

Postal address: 3601 Hwy 7 E, Suite 1005, Markham, ON L3R 0M3, Canada

Location: Ontario, Canada