jelliejellieSOS Privacy Policy
Last updated: 27 October 2026. How jellieSOS handles your information and the limits of its deletion controls.
Who is responsible
jellieSOS is operated by Irene Maritz, operating as JellieLabs, South Africa. This policy covers the jellieSOS iPhone app, its browser/Android experience and the backend that supports group alerts. Contact our monitored privacy inbox at hello@jellielabs.com.
Information you provide
We store the display name and group names you enter, group membership and creator status, invitation details, and app-generated member and group identifiers. The app does not require your email address, telephone number or address book to join a group. If you email support, we receive your email address, message and any information or attachments you choose to send.
Locations and SOS activity
With your device�s location permission, the app can obtain and cache a recent location while in use to prepare an SOS. When you send an SOS, we store its available latitude, longitude, accuracy, capture time, sending and receipt times, sender and group identifiers, and alert identifier. Location can be absent or approximate depending on permission and availability. We also store recipient, delivery-attempt, read, acknowledgement and dismissal information to operate alerts. This is not a continuous server-side travel history.
Device identifiers, notifications and storage
We use random app/device-session identifiers and authentication credentials to recognize an authorized session and route alerts. These are not advertising identifiers. When you enable notifications, we store an Apple push token or a browser push subscription and its delivery keys, linked to membership. Local encrypted storage holds saved SOS records, membership and a recent location; cookies, Keychain and browser storage also support authentication, preferences and offline retry. Network connections expose an IP address to the server and service providers; our app uses it for security and short-lived rate limiting rather than advertising.
How we use information
We use this information to create and manage groups, authenticate access, route and display SOS alerts and locations, send notifications, record delivery and acknowledgement, prevent duplicate/replayed alerts, maintain security and respond to support or privacy requests. The inspected app has no advertising or analytics SDK, does not access the advertising identifier, and does not combine app data with other companies� data for advertising tracking. We do not use app information for advertising or sell it to data brokers.
Who can see it
Your SOS identity and available location are shared with authorized recipients in your group. Group creators can view active membership. The service�s authorized administrator can view group, member and alert records through its administration interface. A recipient may retain information they have already seen or copied; we cannot erase independent copies on their behalf.
Service providers and external links
Hosting and email infrastructure process service traffic, stored data and support correspondence as needed to operate the service. Apple Push Notification service processes iPhone notification tokens, generic alert messages and an incident identifier; the current notification payload does not include your name or GPS coordinates. Browser notifications use the relevant supported Apple, Google/Firebase, Mozilla or Microsoft push service. If you choose to open Google Maps directions, the destination coordinates are sent to Google, whose own privacy policy applies. These providers may process information outside South Africa. We do not promise that all processing or copies remain in South Africa.
Server retention
Server SOS records, including their locations and associated recipient/delivery records, are removed by scheduled cleanup after seven days from server receipt. Cleanup runs at startup and periodically, so deletion is not guaranteed at an exact minute. Invitations expire after seven days and expired/revoked invitations are pruned. Most non-SOS request-operation records are pruned after seven days. Device sessions expire after 365 days, but expiry revokes access rather than erasing every associated record. Group and membership records, device records, administration audit events and SOS replay-prevention receipts currently have no automatic purge deadline. Replay receipts retain identifiers, a request digest and outcome rather than the full SOS location payload. Push registrations are removed or deactivated when disabled or membership becomes inactive; expired native tokens can remain while membership is active.
Device retention and deletion controls
On iPhone and browser installations, saved acknowledged SOS location information is eligible for removal seven days after acknowledgement is recorded locally. Cleanup occurs when the app performs maintenance. Unresolved local SOS information remains until deleted. Other local caches and preferences can remain. Deleting a sent SOS from your screen removes its local saved record and, when the server is reachable, hides it from your sent list; it does not erase the server alert or recipient copies. Deleting a received alert hides it for that recipient. Leaving or removing a membership revokes access but does not erase all historical records. Administrator deletion of an incident removes its active server incident and delivery records but retains audit/replay records. Group deletion revokes memberships and invitations while preserving historical records according to the rules above. Uninstalling the app must not be assumed to erase server information or all Keychain items.
Logs, backups and retained copies
The service keeps operational output and error/status information for running and troubleshooting it. The inspected SOS host has no configured Caddy HTTP access-log block; network and infrastructure providers still process connection metadata. Container logs have no verified fixed expiry schedule. Encrypted SOS rollback backups exist and have no verified fixed automatic deletion schedule. Deletion from the live database is not a promise of immediate deletion from backups, provider-held copies, audit records or recipient devices. There is no single seven-day retention period covering all data. Contact us about the scope of retained copies or a specific deletion request.
Security and permissions
We use HTTPS for service connections and AES-256-GCM encryption for the backend data store. iPhone local SOS storage uses Apple CryptoKit, device file protection and Keychain; browser storage uses platform encryption APIs. The service can decrypt its records to provide the app, so this is not end-to-end encryption. Access controls and encryption reduce risk but do not guarantee absolute security. You may decline or revoke location and notification permissions in device or browser settings. The app does not need camera or microphone access. Location and notification availability affect those features.
Your choices and privacy requests
You can change permissions, disable notifications, use the app�s available record controls and leave a group. For access, correction, deletion, objection or other privacy requests, email hello@jellielabs.com. We may need enough information to verify and locate your records; do not send passwords or private invitation links. In version 1.0.19 (build 25) and the updated web app, open Information and choose Delete my account and data to erase the authenticated device identity, its memberships, sent SOS records, associated live-server records and local saved data. Online access with the original device session is required. Other members retain their own records; an active remaining member becomes owner of a shared group. Other separately registered devices, recipient copies and existing backups are not erased by this action. If your session has expired, or for other devices and retained copies, contact the privacy inbox. Earlier versions require a privacy request. This policy does not promise an automatic deletion deadline for retained copies. Support correspondence has no fixed automatic expiry schedule. If you believe your privacy rights have not been respected, you can contact South Africa�s Information Regulator or your applicable privacy authority.
Emergencies and policy changes
jellieSOS does not automatically contact emergency services. Do not send an emergency request to our support inbox. We will update this page when data practices change and show the revised date here.