The short version. This website sets no cookies, runs no analytics, has no tracking pixels, no advertising, and its only form is the optional product review form. We do not know who visits it. The complete privacy policy for our Jarvis Bodyguard app is included on this page, under Jarvis Bodyguard privacy policy.
1. Who we are
Aeon Frost Capsule Corp is an independent software company registered in Ontario, Canada. For any privacy question, write to legal@aeonfrostcapsulecorp.com.
2. What this website collects
Nothing, unless you post a review. There is no account system, no contact form, no newsletter sign-up and no e-commerce. We set no cookies and use no local storage. We run no analytics package of any kind — not Google Analytics, not a self-hosted alternative, not a "privacy-friendly" one. We do not build a profile of you, because we have no mechanism to.
2a. Product reviews
Product pages carry an optional review form. Plugin reviews require a valid licence; Jarvis Bodyguard reviews are open to anyone, limited to one per network, and every one is read before it appears. If you post a review we keep: the star rating, headline, review text and display name you choose (these are published once the review is live); a one-way scrambled (hashed) form of your licence email or review code, used only to stop duplicate reviews; and a one-way scrambled form of your IP address, used only for flood and spam limits. Your email address, licence key and IP address are not stored in readable form and are never published. The form is protected by Cloudflare Turnstile, which checks that you are human and is covered by Cloudflare's Turnstile privacy addendum. We decide at our discretion which reviews are published, may remove any review at any time, and may reply publicly. To have your review removed, write to legal@aeonfrostcapsulecorp.com with the display name and product.
2b. Site visit counter
The site shows a public count of visits and the top countries they come from. To count visits we record the date, the hour, the visitor country reported by our network provider, and whether the request came from a person or an automated crawler. To avoid counting the same connection twice in a day we keep a one-way scrambled (hashed) token of your IP address that changes every day and is deleted after two days. No cookies are used, nothing is stored in your browser, and no visit is linked to you.
3. Third parties that see your request
We will not pretend a static website exists in a vacuum. Two parties necessarily see a request for this page:
- Our hosting provider. Serving a web page requires a server to receive your request, which means your IP address reaches our host as a technical necessity. Hosts typically retain short-term operational logs for security and abuse prevention. We do not access these for any marketing purpose.
- Google Fonts. The typefaces on this site are served from Google's font CDN, which means your browser makes a request to fonts.gstatic.com and Google receives your IP address and user agent as part of that request. We disclose this because it is true, and because we would rather tell you than have you find it.
Apart from Cloudflare Turnstile on the review form, there is no other third-party code on this site. No tag managers, no embedded video, no social widgets, no chat bubbles, no session recorders.
4. If you email us
If you write to us, we receive your message and your email address, and we keep that correspondence for as long as it is useful to the matter you raised. We use it to reply to you and nothing else. We do not add you to a mailing list, and we do not sell, rent or share correspondence with anyone.
5. Our products
Jarvis Bodyguard stores its data encrypted on the user's own device and transmits nothing to us. Its complete privacy policy is set out in full below, under Jarvis Bodyguard privacy policy. Its Terms of Service are at /software/jarvis-bodyguard/privacy.
6. Your rights
Under Canadian privacy law (PIPEDA), and under the GDPR if you are in the UK or EEA, you have rights of access, correction, deletion and objection regarding personal information an organisation holds about you. In our case the honest answer is that this website holds none, so there is generally nothing to access or delete. If you have emailed us and want that correspondence deleted, write to us and we will delete it.
7. Children
This website is not directed at children and collects nothing from anyone, including children.
8. Security
This site is served over HTTPS with HSTS, a strict Content Security Policy, and no third-party JavaScript. If you believe you have found a security issue with this site or any of our products, please report it to legal@aeonfrostcapsulecorp.com. We will acknowledge good-faith reports and we will not pursue researchers who act responsibly.
9. Changes
If this policy changes we will update the date at the top of this page. We do not make material changes quietly.
Jarvis Bodyguard privacy policy
This part covers the Jarvis Bodyguard Android app (com.jarvisbodyguard.app), published by Aeon Frost Capsule Corp. It is the app's complete privacy policy, reproduced in full.
Jarvis Bodyguard — Privacy Policy
Aeon Frost Capsule Corp · Guelph, Ontario, Canada
Application: Jarvis Bodyguard (com.jarvisbodyguard.app)
Effective date: The date this application first became publicly available on Google Play (Version 1.0, September 2026)
Privacy contact: HelpdeskAFCC@outlook.com
In plain terms. This app runs on your phone. We do not receive your data, we cannot see it, and we cannot recover it for you. Nothing in this policy is a promise that the app will work — that is dealt with in the Terms of Service, and you should read them.
1. The short version
We do not collect your data. We cannot see it. We could not give it to anyone if we were asked, because we do not have it.
Jarvis Bodyguard runs entirely on your phone. Aeon Frost Capsule Corp operates no servers for this app. Your emergency contacts, recordings, location history, PINs and settings are stored on your device, encrypted, and they never reach us.
There are exactly three ways information leaves your phone, and you trigger all three yourself. They are in section 4, and we describe them plainly rather than burying them.
2. Who we are
Aeon Frost Capsule Corp, of Guelph, Ontario, Canada, publishes Jarvis Bodyguard and is the data controller for the limited purposes described here.
For any privacy question, or to exercise any right in section 9, contact HelpdeskAFCC@outlook.com.
3. What the app accesses, and why
| What | Why | Where it goes |
|---|---|---|
| Emergency contacts — names, phone numbers, optional email, relationship | To send alerts to the people you choose | Encrypted on your device. Phone numbers go to your carrier only when you send an alert |
| Your name and custom alert message | Included in the alert so contacts know who it is from | Encrypted on your device; sent in the alert you trigger |
| Precise location | Included in alerts; shared periodically during an SOS and during "walk me home" | Encrypted on your device; sent to your chosen contacts as a map link |
| Background location | So an alert and a walk-home update still work when the app is closed | Same as above |
| Microphone | Evidence recording during an SOS, and the voice-activated safe phrase | Recordings stay on your device, encrypted. See §4.3 for the safe-phrase exception |
| Camera | Optional video evidence during an SOS | Encrypted on your device |
| Motion sensors | Optional, off by default, experimental fall and crash detection | Never leaves the device |
| Medications and emergency medical notes | Optionally included in an alert so responders can act | Encrypted on your device; sent only in an alert you trigger |
| PINs and duress PINs | To lock the app and to trigger a silent alert | Stored as a salted hash. Never stored in readable form, never transmitted |
| In-app diagnostic log | So a fault can be diagnosed on your own phone | Stays on your device. Sensitive entries go to a separate file. Never uploaded automatically |
The app does not read your phone's contact list. When you add a contact, Android's own contact picker returns just the one entry you chose, or you type it in.
4. The three times information leaves your phone
4.1 Alerts you send
When you trigger an SOS, a walk-me-home update, an "I'm uncomfortable" check-in, or an all-clear, the app sends an SMS — and optionally places a call — to the contacts you chose.
That message travels through your mobile carrier, exactly like any text you send yourself. Your carrier can see it, and carriers keep records of messages under their own policies and their own legal obligations. That is outside our control and outside the app.
We are not a party to that message. It does not pass through us.
4.2 Purchases
Subscriptions are sold through Google Play Billing. Google handles the payment and tells the app whether a subscription is active. We never see your payment details. Google's handling of that transaction is governed by Google's privacy policy.
4.3 The voice-activated safe phrase — read this one carefully
If you enable the voice-activated SOS, the app listens for a phrase you choose, using Android's own speech recognition.
On some devices, that recognition may send audio to Google's servers. We ask Android for on-device recognition, and use it wherever the device offers it — but on older Android versions, or on devices without an on-device recogniser, audio may leave your phone and be processed by Google. We cannot prevent that and we will not pretend otherwise.
Why this matters more for some people than others. If someone else has access to your Google account, voice activity recorded there could reveal that you use this app, or reveal your safe phrase. If that is a risk for you, leave the voice feature off and use the button, the duress PIN, or a hardware trigger instead.
This is the only feature in the app where audio can leave the device. Evidence recordings never do.
5. What we do not do
- We do not upload, sync, or back up your data to any server of ours. We have none.
- We do not use analytics, crash reporting, advertising, tracking, or attribution SDKs.
- We do not sell, rent, or share your personal information with anyone.
- We do not build a profile of you.
- We do not read your recordings, your location, or your contacts. We cannot.
- We do not track you across other apps or websites.
- We do not use cookies. The app has no web pages, no embedded browser, and no internet permission at all, so there is nothing in it that could set or read a cookie or a web tracker of any kind. Our public Terms and Privacy page is a plain static page that exists only to display these documents; it asks you for nothing and stores nothing on your device.
Your consent. You accept these terms and this policy the first time you open the app, on a screen that cannot be skipped, and that acceptance is recorded so it is always clear which version you agreed to. The only information the app ever holds is what you type into it yourself — a contact, a name, a medical note, a message. Entering it, and turning on the feature that uses it, is your consent to the app handling it in the way described here. There is nothing collected in the background to consent to, and there are no forms that send your details anywhere: the one place you can contact us is your own email app, which you control.
6. How your data is protected
- Personal data at rest — contacts, medications, your name, your custom message, the alert queue, and recordings — is encrypted with AES-256-GCM, using a key held in the device's hardware-backed keystore and bound to the app's identity.
- PINs are stored as salted hashes and are never recoverable, by you or by us.
- Screens showing sensitive information are marked to be excluded from screenshots and from the recent-apps preview.
- The evidence vault has its own PIN, separate from the app PIN.
The trade-off, stated plainly: because the encryption key lives in your device's secure hardware and we hold no copy, nobody can recover your data if the device is lost, reset, or if its keys are invalidated by an OS update, a repair, or a restore onto different hardware. There is no back door. That is deliberate — a recovery route we could use is a route someone could use against you — but it means the responsibility for keeping a copy of anything you need is yours. The app has an export function for exactly that.
6.1 Privacy risks we cannot remove
Encryption protects data at rest, on a device you control. It cannot protect you from these, and we would rather say so than let you assume otherwise:
- Someone who can unlock your phone. If a person has your device unlocked, or knows your PIN, the app's protections are already behind them. No app can tell who is holding a phone.
- The messages you send. An alert travels through your carrier as an ordinary text. Your carrier can see it and keeps records of it under its own policies and legal obligations. It also sits in the recipient's phone, where anyone with access to *their* phone can read it — including your name, your message, and your location.
- Voice recognition. On some phones the safe-phrase audio is processed by Google rather than on your device, and may appear in the voice activity on your Google account. Anyone with access to that account may find it. See section 4.3.
- Recordings capture other people. Anyone within range of the microphone or camera is recorded, whether or not they know or consented. Whether that is lawful is your responsibility.
- Exported files are ordinary files. The export function decrypts your recordings so you can keep them elsewhere. Once exported they are no longer protected by this app, and a determined person searching the device can find them.
- The diagnostic log. The app keeps a log on the device so a fault can be diagnosed. Sensitive entries go to a separate file, but the log does record that the app is running and what it did.
- The app's presence is visible. Android's Settings, the app info screen and your Google Play library name this app, regardless of any disguise.
- Backups. This app opts out of Android's automatic backup, so its data is not copied into a device or cloud backup by the operating system. Anything you export yourself is an ordinary file and is covered by your own device and account settings.
This list is what we know of. It is not a promise that there are no others.
7. How long data is kept, and how to delete it
We keep nothing, so there is nothing for us to delete.
On your device:
- Contacts, settings, medications — kept until you delete them or uninstall the app.
- Recordings — kept in the vault until you delete them. Recordings from an incident are protected from deletion for 7 days, so evidence cannot be destroyed in a panic or by someone who has taken the phone.
- The pending-alert queue — cleared when the incident ends.
- The delivery report — describes one incident and is replaced when the next alert is sent.
- Diagnostic logs — kept on the device on a rolling basis and never uploaded unless you deliberately export them.
- Location — a last-known position is held only in memory and in the alert you send. There is no location history file.
To delete everything: uninstall the app. That removes all of it, permanently, including the encryption keys. Exporting anything you want to keep first is on you.
8. Children
This app is not directed at children under 13, and we do not knowingly collect anything from them. A "child mode" exists so a parent can give a child a phone with a limited version of the app; it does not collect anything additional and everything in this policy still applies.
9. Your rights
Because your data never reaches us, the fastest route to every right below is the app itself: you can view, correct, export and delete everything from inside it, immediately, without asking us.
Depending on where you live you may also have statutory rights — under PIPEDA (Canada), the UK GDPR and Data Protection Act 2018, the EU GDPR, and the CCPA/CPRA (California) — to access, correct, delete, restrict or object to processing of your personal information, to data portability, and to complain to a regulator.
We will honour any such request. In most cases our honest answer will be that we hold no personal information about you at all, and we will say so in writing if you ask.
We do not sell or share personal information as those terms are defined under the CCPA/CPRA. We have never done so.
10. Legal requests
If we receive a subpoena, warrant, or other legal demand for a user's data, we have nothing to produce. We hold no user data, no account records, no location history and no message contents.
Records of a message that was sent would sit with the user's mobile carrier, not with us.
11. Changes to this policy
If this policy changes materially, the change will be shown in the app before it takes effect. The effective date at the top always reflects the current version.
12. How to contact us
For any question about this policy, to exercise any right in section 9, or to report a privacy concern:
Aeon Frost Capsule Corp
Guelph, Ontario, Canada
We answer privacy enquiries in writing. In most cases the answer will be that we hold no personal information about you at all, and we will say so plainly.