◠ Halo
Privacy Policy
Portsmouth Technologies LLC · Last updated September 2026
Halo
Operated by Portsmouth Technologies LLC
Last updated: September 2026
Website: https://haloconfirm.com
Contact: pardha@portsmouthai.com
This Privacy Policy explains how Portsmouth Technologies LLC (“Portsmouth,” “we,” “us,” or “our”) collects, uses, shares, and protects information in connection with the Halo mobile application, related websites, and services (collectively, the “Service”).
Halo is a protective mid-call check: you can use device biometric presence (such as Face ID) to sign a short-lived check and text a safety word to a number you already trust so the recipient can read it back—helping you assess whether you are interacting with someone who has live biometric presence and control of the registered phone-number path, as implemented.
1. Scope
This Policy applies to information we process when you use Halo. It does not cover third-party websites, Apple’s App Store, your wireless carrier, or other services that have their own policies. For App Store purchases, Apple’s privacy practices also apply to payment and subscription data Apple collects as merchant of record.
2. What We Collect
2.1 Information you provide or that is created for your account
When you register or use Halo, we may process:
| Data | Notes |
|---|---|
| Display name | Chosen by you for your account |
| Public key identifier (kid) | Identifies the public key associated with your device-held key pair |
| Last four digits of phone number (num4) | Stored for display / recognition purposes |
| Salted phone hash | Used to look up or verify registration without storing the raw phone number in the registry |
| Account / verification signals | Such as confirmation that a verification step succeeded |
We do not store your raw phone number in the user registry. Your private key never leaves your device.
2.2 What we intentionally do not collect (product design)
Halo is designed not to store:
- Call records or call audio;
- Your contacts list;
- A send history of safety-word recipient numbers used for the primary mid-call check.
2.3 Safety-word recipient numbers
The primary safety-word text for a mid-call check is initiated from your own Messages (or equivalent device messaging). That design means Halo need not store the recipient’s number for that check. Recipient numbers are not retained by Halo as a history of who you checked with.
2.4 Transactional SMS (if used)
If Halo sends carrier SMS (for example, OTP or other transactional verification via a provider such as Twilio), we process the phone number as needed to deliver that message. Those messages are transactional verification only. We do not retain recipient numbers as a marketing list or long-term send history.
2.5 Automatically collected technical data
Like most online services, our infrastructure (including Cloudflare) may process limited technical data such as IP address, request timestamps, approximate location derived from IP, device/app version signals, and security or abuse-prevention logs. We use this for reliability, security, and debugging—not to build call or contact profiles.
2.6 Purchases
Halo Pro subscriptions are sold via Apple In-App Purchase. Apple is the merchant of record and processes payment method, Apple ID, and subscription status. We may receive limited subscription status information necessary to unlock paid features (for example, entitlement signals), not your full card number.
2.7 Communications
If you email us (for example, at pardha@portsmouthai.com), we receive the content of that message and your contact details.
3. How We Use Information
We use information to:
- Provide, operate, and improve the Service (registration, verification, check signing flows, subscriptions);
- Authenticate account-related actions and reduce abuse;
- Send transactional SMS when that channel is used (verification / account-related notices—not marketing lists by default);
- Provide customer support and respond to requests;
- Enforce our Terms of Service and protect security;
- Comply with law and respond to lawful requests;
- Analyze aggregate or de-identified usage for reliability (without rebuilding prohibited datasets such as call records or contact histories).
We do not sell your personal information. We do not sell mobile phone numbers or SMS opt-in information for third-party marketing.
4. How We Share Information
We share information only as described below:
4.1 Service providers / processors
- Cloudflare — hosts Worker / KV infrastructure that stores registry fields described above and processes requests as our processor;
- Twilio or similar SMS providers / carriers — if Halo sends transactional SMS (OTP or verification), the number and message content needed for delivery are processed by that provider and the carrier; we do not use that path to build a retained recipient history for marketing;
- Apple — for In-App Purchase, subscriptions, and App Store distribution; Apple’s terms and privacy policy apply to payment data Apple collects.
4.2 Legal and safety
We may disclose information if we reasonably believe it is required by law, regulation, legal process, or governmental request, or to protect the rights, safety, or security of Portsmouth, users, recipients, or the public.
4.3 Business transfers
If we are involved in a merger, acquisition, financing, reorganization, or sale of assets, information may be transferred as part of that transaction, subject to appropriate confidentiality and this Policy’s principles where practicable.
4.4 No sale; limited “sharing” for advertising
We do not sell personal information. We do not share personal information for cross-context behavioral advertising as that term is used under California law. Halo’s core product does not depend on advertising trackers for that purpose.
4.5 With your direction
If you initiate a message from your own device Messages app, that communication is between you, your carrier, and the recipient under their respective terms—not a Halo-stored send history.
5. Retention and Deletion
- Registry data (display name, kid, num4, salted phone hash, and related account fields) is retained while your account remains active.
- Account deletion erases your registry entry from our backend.
- Transactional SMS provider logs (if any) may be retained by providers for a limited period according to their retention schedules and legal requirements; Halo does not keep a product-level history of safety-word recipient numbers.
- Support emails may be retained as long as needed to resolve your request and for legitimate business or legal records.
- Security / infrastructure logs are retained for a limited period consistent with security and operations needs.
When retention is no longer necessary, we delete or de-identify information, subject to backups and legal holds that may delay complete erasure for a short period.
6. Security
We use administrative, technical, and organizational measures appropriate to the nature of the data we store—including keeping private keys on device, storing a salted phone hash rather than a raw number in the registry, and using reputable infrastructure providers. No method of transmission or storage is 100% secure. We do not claim certifications (such as SOC 2) in this Policy. You are responsible for securing your device, biometrics, and access to your Messages app.
7. Children
The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us information, contact us and we will take appropriate steps to delete it. Where local law sets a higher digital-consent age (for example, 16 in some contexts), we do not knowingly collect personal information from children under that age for Halo either. Halo accounts are intended for users who meet the eligibility requirements in our Terms of Service (generally 18+).
8. Your Choices
- Account deletion — use in-app delete (where available) or contact us to request erasure of your registry entry;
- SMS — for transactional SMS from Halo’s SMS channel (if used), reply STOP to opt out or HELP for help; you may also email us;
- Subscriptions — manage or cancel Halo Pro in your Apple ID subscription settings;
- Device permissions — control biometric, contacts, and messaging permissions in your device settings (Halo’s design does not require uploading your contacts or call history to our registry).
9. U.S. State Privacy Rights (Light Notice)
Depending on where you live (for example, California under the CCPA/CPRA), you may have rights to:
- Know / access categories and specific pieces of personal information we collected;
- Delete personal information (subject to exceptions);
- Correct inaccurate personal information;
- Opt out of “sale” or “sharing” for cross-context behavioral advertising (we do not sell or so share);
- Limit use of sensitive personal information in certain ways (our use of phone-related data is limited to providing the Service as described);
- Non-discrimination for exercising privacy rights.
Categories we may collect (CPRA-style)
| Category | Examples in Halo | Sold / Shared for ads? |
|---|---|---|
| Identifiers | Display name; salted phone hash; num4; kid | No |
| Commercial information | Subscription entitlement status from Apple (limited) | No |
| Internet / electronic activity | App/request logs, IP, security events | No |
| Geolocation (coarse) | Approximate from IP only, if logged | No |
| Audio/call content | Not collected by design | N/A |
| Contacts / send history | Not collected by design for primary check | N/A |
| Sensitive personal information (limited) | Phone-related verification data as described | Not sold; used to provide Service |
We do not use or disclose sensitive personal information for purposes that require a “limit the use” right beyond providing the Service you request.
To exercise rights, email pardha@portsmouthai.com. We will verify requests as required by law (for example, by confirming control of the account or registered contact path). You may use an authorized agent where law allows, subject to verification. We respond within the timeframes required by applicable law.
This section is a good-faith summary and is not legal advice; additional state laws may apply.
10. International Users
We are based in the United States. If you access the Service from outside the U.S., you understand that information may be processed in the United States and other locations where our processors operate (including Cloudflare’s network).
11. Changes to This Policy
We may update this Privacy Policy from time to time. We will post the updated Policy with a new “Last updated” date and, for material changes, provide additional notice where required by law. Continued use after the effective date means you acknowledge the updated Policy, except where affirmative consent is required.
12. Contact
Portsmouth Technologies LLC
Email: pardha@portsmouthai.com
Website: https://haloconfirm.com
For privacy requests (access, deletion, questions about this Policy), use the email above with the subject line “Privacy Request” when practical.
End of Privacy Policy.
See also our Terms of Service.