Privacy Policy

1. Who we are and what this policy covers

This policy explains how Phone Guardian (“we”, “us”) handles personal information in the Phone Guardian call-screening service. It covers:

• the Phone Guardian website and web app at https://pg.isilive.ca;
• the Phone Guardian Android app (package ca.isilive.phoneguardian), used by family members (“guardians”) who keep watch over a protected phone line; and
• the Phone Guardian Safe Calls Android app (package ca.isilive.phoneguardian.guarded), used by the protected person (usually a parent) to answer screened calls.

Both apps are free, show no ads, contain no purchases and include no advertising or analytics SDKs. We never sell personal information.

2. The short version

• Calls to a protected phone line pass through our service. Every call is recorded and transcribed — the caller, the protected person, and any guardian who joins the call by phone. Callers hear a notice that calls are recorded.
• Transcripts are checked for scam warning signs by automated and AI services as the call happens. Guardians are alerted and can review, listen live, join, or end a call. Families can also turn on automatic warnings and automatic call cut-off; these are off by default.
• Call data is deleted automatically after 90 days unless the account owner chooses a different period (1–3650 days).
• Recordings and the database live in Canada (AWS ca-central-1). Some service providers process data in the United States.
• Any guardian can delete their account; the protected person can ask for their data to be deleted without any login. See Delete your account and Delete your data (Safe Calls).

3. The people involved

Account owner

The guardian who set up the subscription on the website and pays for it. Owners control retention, export and deletion of the family’s call data.

Guardians (family members)

People the owner or an admin invites. They sign in on the website or the Phone Guardian app, receive alerts and can review calls.

Protected person

The person whose phone line is screened. They have no account. If they use the Phone Guardian Safe Calls app, it is linked to the line once with a setup code shown by a guardian.

Callers

Anyone who calls the protected line. They are told the call is recorded before it connects.

4. What we collect

4.1 Guardian accounts (website and the Phone Guardian app)

• Sign-in identity: your email address and, if you sign in with Google, your display name. Sign-in is handled by Clerk (see section 6).
• Session security data recorded by Clerk: the IP address of each sign-in and the approximate city and country derived from it, device and browser details, and — in the Android app — a Google Play Integrity device attestation and an app-scoped device identifier used to detect tampered devices and fraudulent sign-ins.
• Your phone number (optional): used only so the service can call you when you choose “Listen in” or join a call.
• Settings you enter: the friendly name of a protected line (for example “Mom”), allow/block phone numbers and their labels, alert thresholds, retention period, and the email addresses of people you invite.
• Notification registrations: Firebase Cloud Messaging (FCM) tokens for the Android app and web-push subscriptions for the browser, so alerts can reach you.
• In-call chat: messages guardians send each other during a call are stored with that call’s record.
• Actions you take: marking a call safe, viewing a call, changing roles, sending invitations, ending or joining a call, and similar actions are written to a tamper-evident audit log (section 8).
• Billing (website only): payment details are entered directly on Stripe; we store your email, plan and billing history. Neither app contains purchases.

4.2 The protected person (Phone Guardian Safe Calls app)

• No account. A single-use setup code (valid 15 minutes) links the phone to the line and issues it a device credential, which is stored in the phone’s hardware keystore and excluded from backups.
• Device details sent to us at enrollment and on check-in: manufacturer and model, app version, the FCM push token (used to wake the phone for an incoming call), and the time of the last check-in. Guardians can see these on the line’s settings page.
• Line name and phone number, sent by the app to our telephony carrier (Telnyx) as caller-ID when it connects.
• Microphone: used only during a call so the caller can hear the protected person. The app does not read contacts, the call log, text messages or location, and has no camera permission — the QR setup code is read by Google’s code scanner, and the app receives only the decoded text.
• Per-call quality reports sent by the Telnyx calling SDK to Telnyx: device model, operating-system version, network type, codec, permission states, connection and audio statistics, SDK logs and the device’s IP address.
• Whether a forwarding code was dialed from the status screen (the call itself is placed in the phone’s own dialer).

4.3 Calls on a protected line

• Audio recordings of every leg of the call — the caller, the protected person, and any guardian who listens in, whispers or joins by phone.
• Transcripts, produced live by speech-to-text providers.
• Risk assessments and summaries, produced by AI language models from transcript excerpts (phone numbers are not sent to the AI providers).
• Call records: caller and called numbers, times, duration, outcome, voicemail messages, and alerts sent.

4.4 Server logs

Our web servers log each request’s IP address, time, URL and outcome for security and troubleshooting. Logs are not used to derive location. Reverse-proxy access logs and application logs are both deleted after at most 90 days.

5. How we use information

• To connect, record and transcribe calls to the protected line and check them for signs of a scam.
• To alert guardians, show live transcripts and risk scores, and let guardians listen, join, whisper or end a call.
• To play automatic warnings or end a call automatically when the family has turned those features on.
• To deliver voicemail and service emails, and push notifications (notification text may include caller numbers and short call summaries).
• To keep the service secure: sign-in protection, fraud prevention, rate limiting and the audit log.
• To bill the account owner (website only).

We do not use call content to train AI models, and we do not use personal information for advertising.

6. Who we share information with

We share personal information only with service providers that process it on our behalf under contract, and with the guardians the family has invited. We never sell it.

Family members. Guardians on a protected line can see that line’s call history, recordings, transcripts, risk scores, the linked phone’s model and last check-in, and each other’s chat messages. They can listen to a call live, join it, or speak a warning to the protected person.

Legal requests. We may disclose information when required by law or to protect the safety of our users, and we will tell the account owner when we are allowed to.

Signed-in guardians can see exactly which providers are active for their account on the Data & Privacy page (/settings/privacy); only providers enabled in our configuration are listed there.

7. Where information is stored and international transfers

Recordings are stored in Amazon S3 in Canada (ca-central-1), encrypted at rest with a customer-managed KMS key. Transcripts, call history, risk assessments and account data are stored on our servers in Canada. The providers in section 6 process data in the United States or on global infrastructure; by using the service you understand that information may be transferred to and processed in those countries, where privacy laws may differ from those in Canada.

8. How long we keep information

9. Security

All traffic between the apps, the website and our servers uses TLS; call signalling uses secure WebSockets and call media uses DTLS-SRTP. Recordings are encrypted at rest with a customer-managed key. Access to a line’s data is limited to the guardians invited to it, and every privileged action is written to a tamper-evident audit log. The Phone Guardian Safe Calls app stores its credential in the Android keystore and excludes it from backups. No system is perfectly secure; if we learn of a breach affecting you, we will notify you as the law requires.

10. Your choices and rights

• Access and export: an account owner can download the family’s data (recordings, transcripts, settings) from Settings → Privacy on the website.
• Delete call history: an account owner can delete all recordings, transcripts and call records at any time, and can shorten the retention period.
• Delete your account: any guardian can delete their account from the Phone Guardian app (Settings → Delete account) or the website. Steps and what is deleted: https://pg.isilive.ca/delete-account.
• Protected person: you can ask for your data to be deleted or your phone to be unlinked without any login. Steps: https://pg.isilive.ca/delete-data.
• Notifications: control them in the app’s settings or your device settings.
• Correction and questions: email support@isilive.ca. We respond within 30 days.

Canadian residents have rights under PIPEDA and may complain to the Office of the Privacy Commissioner of Canada. Residents of the EU/UK have rights under the GDPR, including access, rectification, erasure, restriction, portability and objection; the export and deletion tools above are how we honour them.

11. Children

The service and both apps are intended for adults (18+). We do not knowingly collect personal information from children. Calls from a child to a protected line are handled like any other call.

12. Changes to this policy

We will post changes on this page and update the date at the top. For material changes we will notify account owners by email before they take effect.

13. Contact

Phone Guardian · support@isilive.ca · https://pg.isilive.ca