SOMA collects and stores information to provide your protection features, preserve useful context, and help your Angels when you need them.
Your Angels cannot simply open SOMA and see where you are. Your safety information is only shared through specific protection features.
SOMA uses your information to provide and improve your safety features.
This may include information you give SOMA and information created while protection features are running.
SOMA may store your location and route information during protected outings and while supported SOMA Smart features are active.
This helps preserve useful context if something happens.
SOMA may store destinations, transport details, Safe Places, journey history, and other information connected to your protected outing.
If you add information about someone you are meeting, a driver, a vehicle, or another part of your outing, SOMA stores it as part of your private safety context.
When you send a Signal or SOS, SOMA uses relevant information from your protection context to help your Angels understand what is happening.
SOMA collects limited technical information to understand crashes, errors, and performance problems so we can keep SOMA working reliably.
SOMA does not sell your personal information or use your safety information to show you ads.
SOMA uses your location during safety activities such as journeys, check-ins and emergencies. Your location is not sold or used for advertising.
Location and route information may be stored securely on SOMA's servers.
Being your Angel does not mean someone can open SOMA and watch where you are.
Your location and safety context may become available to an Angel when:
Outside of these situations, your Angels do not automatically see your live location.
Incognito hides routine journey and arrival activity. It does not hide narrowly relevant safety information from an authorized Signal, serious emergency, or Missing Person request.
Your Angels are people you have chosen to help you when something goes wrong.
Adding someone as an Angel does not give them permanent access to your location or private safety information.
Relevant information may become available when you send a Signal, choose to share a protected outing, or an authorized Missing Person request is activated.
A Missing Person request uses the most recent relevant retained information SOMA still has. It does not unlock your full journey, location, or Evidence history.
SOMA is designed to share useful information when it is needed, not to let your Angels constantly track you.
SOMA keeps recent records from protected outings so useful information is not lost if something happens later.
SOMA records the information available to it.
SOMA does not decide who is responsible for an incident or make accusations based on your journey information.
If SOMA does not know something, it should remain unknown rather than being guessed.
Routine safety information is not intended to remain forever. SOMA will automatically remove eligible information according to its retention policy. Important emergency evidence may be preserved when you deliberately choose to keep it.
Deleting history is not available yet. SOMA removes eligible information automatically.
Photos, vehicle details, driver information, recordings, meeting details, and other safety information you add to SOMA stay private unless a protection feature allows them to be released.
Relevant information may become available to your Angels when you send a Signal or SOS, share a protected outing, or an authorized Missing Person request is active.
Some confirmed safety records cannot be individually edited or deleted after they have been saved. This helps protect the accuracy of information that may later become important.
Your normal data retention period still applies to eligible information when nothing happens.
Some SOMA features may use your microphone when you choose to use them. SOMA does not continuously listen to you.
Voice input can help you fill safety information without typing everything manually. When you use voice input, SOMA can use supported Apple speech features to turn what you say into information for the form you are completing.
You can review and correct the information before it is saved. Voice input is optional. You can always enter the same information manually.
SOMA collects limited technical information to help us understand crashes, errors, performance problems, and how reliably important features are working.
This information helps us find problems and improve SOMA. We do not sell this information or use your safety information for advertising.
SOMA does not sell your personal information.
SOMA does not show ads inside the app, including to Free users.
Your safety information is not automatically shared with your Angels.
Information may be shared when necessary to provide a protection feature you have chosen to use.
SOMA does not currently have an automatic connection or partnership with the police or other emergency services.
Sending a SOMA Signal does not mean the police or emergency services have been contacted.
Your Angels may choose to contact the appropriate authorities when necessary.
SOMA does not voluntarily release your private safety data directly to authorities as part of normal emergency handling. Your Angels control the information available to them and may choose what they share.
SOMA may respond separately where legally compelled through a valid court order or other binding legal process, limited to the minimum information legally required.
SOMA does not keep ordinary safety information forever.
Each piece of eligible safety information has its own retention period based on the date it was created.
14 days
Eligible safety information is normally kept for 14 days.
28 days
Eligible safety information is normally kept for 28 days.
Each day's information has its own retention period.
For example, information created today begins its retention period today. Information created tomorrow begins a new retention period tomorrow.
This means your safety history gradually expires over time instead of everything being deleted at once.
SOMA keeps recent information because a safety problem may not always be discovered immediately.
You can request a copy of the personal information associated with your SOMA account.
Your data will not be available immediately.
After you request it, SOMA will prepare your information and send it to the email address connected to your account when it is ready.
Your request is being prepared.
We'll let you know when your data is ready.
SOMA uses encryption and other security measures to protect your information while it is being transmitted and stored.
Access to sensitive safety information is limited based on what a person is allowed to see and what protection event is happening.
Your SOMA PIN also protects important safety actions.
SOMA does not claim that your information is end-to-end encrypted.
SOMA Web Safety Access and Recovery Vault add carefully restricted web processing to the same privacy model.
With deliberate permission, a user may send a short note, audio, video, a photo, the borrowed device's current location, or a temporary contact number to eligible Angels.
Vault information is persistent preparedness data, separate from temporary safety updates. Access depends on the sensitivity level selected for each item.
SOMA does not claim end-to-end encryption, zero-knowledge storage, automatic police partnerships, guaranteed delivery, or unlimited retention. The web examples on this page are demonstrations of the website experience; they are separate from the iOS app's live safety controls and do not claim to deliver live alerts.
Effective Date: 23rd August 2026
This Privacy Policy explains what information SOMA collects, why we collect it, how we use it, when it may be shared, how long we keep it, and the choices you have over your information.
SOMA is built around a simple principle: your safety information is personal.
We do not sell your personal information.
We do not show advertising inside SOMA, including to Free users.
SOMA collects information needed to provide your account, safety features, protected outings, SOMA Smart features, Signals, SOS features, and other services you choose to use.
The information we collect depends on which SOMA features you use.
When you create or use a SOMA account, we may collect:
Location is an important part of many SOMA safety features.
Depending on the permissions you give SOMA and the features you use, we may collect and store:
Location information may continue to be collected while supported protection features are running in the background.
Location and route information used by SOMA may be stored on SOMA's servers.
When you use SOMA to protect an outing, we may store information such as:
SOMA may preserve this information so that useful context is available if something later goes wrong.
If you choose to add information about a ride, driver, or vehicle, SOMA may store information such as:
This information forms part of your private safety context.
If you tell SOMA that you are meeting or visiting someone, we may store information you provide about that person.
This may include their name and any additional information you choose to provide through supported SOMA features.
Normal meeting context is separate from SOMA's more detailed Meeting Someone New features.
SOMA may allow you to choose someone from your device contacts when adding an Angel or entering supported safety information.
SOMA does not use your entire contact list simply because you open the contact picker.
We use the contact information that you choose to provide to SOMA for the feature you are using.
If you use SOMA Smart or Safe Places, we may store information such as:
Your SOMA Smart information is not automatically visible to your Angels.
When you send a Signal or SOS, SOMA may store information connected to the event.
This may include:
This information may be shared with your Angels according to the safety features and sharing settings you have enabled.
Depending on the features you use, SOMA may allow you to add or create safety evidence such as:
Safety evidence is kept private unless a SOMA protection feature allows it to be shared.
Some confirmed safety records cannot be individually edited or deleted after they have been saved.
This helps preserve the accuracy and integrity of information that may later become important.
Some SOMA features may allow you to use your voice instead of typing information manually.
Voice input is optional.
When you choose to use voice input, SOMA may use supported Apple speech and transcription features to convert what you say into text or structured form information.
SOMA does not continuously listen to you.
Voice input does not automatically submit or confirm important safety information.
You can review and correct information before it is saved.
SOMA does not use an external AI assistant to listen to or interpret your voice as part of this feature.
When you intentionally use a supported Live Witness or recording feature, audio, video, or other captured information may be uploaded to SOMA's systems so it can be preserved as safety evidence.
Live Witness does not mean SOMA is continuously recording you.
Recording only occurs through supported features and permissions.
SOMA collects limited technical information to understand crashes, errors, performance problems, and the reliability of important app features.
This may include:
This information helps us maintain and improve SOMA.
SOMA does not use your safety information to show you advertising.
We use information to:
Adding someone as an Angel does not give them permanent access to your location or safety information.
An Angel cannot normally open SOMA and see your live location whenever they want.
Relevant safety information may become available to an Angel when:
Outside of these situations, your Angels do not automatically receive access to your everyday location, private journeys, SOMA Smart history, driver information, meeting information, or private safety evidence.
SOMA may allow a Missing Person request to be activated according to settings selected by the user.
When an eligible Missing Person request is activated, the most recent relevant retained safety information SOMA still has may become available to the authorized Angel.
Incognito suppresses routine journey, arrival, and location visibility. It does not prevent narrowly relevant Incognito safety information from being used for an authorized Missing Person request, Signal, SOS, or serious emergency.
A Missing Person request does not unlock the user's complete SOMA history. Information that has already been removed under the applicable retention period cannot be recovered or recreated.
This may include available information such as:
SOMA only provides information available within the user's SOMA safety context.
SOMA does not invent missing information or determine who is responsible for an incident.
SOMA is designed to preserve useful safety context.
SOMA does not determine whether a person committed a crime.
SOMA does not identify suspects.
SOMA does not determine whether a driver, person being visited, Angel, or any other individual is responsible for an incident.
Journey information may be incomplete.
For example, if a user starts a ride but does not confirm that the ride ended, SOMA may record that the ride completion was not confirmed.
This does not mean the user remained with the driver.
If SOMA does not know what happened, the information should remain unknown rather than being guessed.
SOMA does not sell your personal information.
SOMA does not sell your location information.
SOMA does not sell your safety evidence.
SOMA does not show advertising inside the app.
We may share relevant information with your Angels when a SOMA safety feature allows it, including Signals, SOS events, protected outing sharing, and eligible Missing Person requests.
We use trusted service providers to help operate SOMA.
These providers may support services such as:
These providers process information only as needed to provide services to SOMA and are subject to their own security and privacy obligations.
SOMA does not directly store your complete card or Mobile Money payment credentials.
Subscriptions purchased through Apple are processed through Apple's payment systems.
Payments made through the SOMA website may be processed by supported third-party payment providers.
SOMA may receive information needed to confirm your purchase, subscription, or entitlement without receiving your complete payment credentials.
SOMA does not currently have an automatic connection, integration, or partnership with police or other emergency services.
Sending a Signal or SOS does not mean police or emergency services have been contacted.
Your Angels may choose to contact emergency services when appropriate.
SOMA does not voluntarily release a user's private safety data directly to authorities as part of normal emergency handling. Guardians control the information available to them and may choose what they share.
We may disclose information if we are legally required to do so under applicable law or a valid legal process.
Any disclosure would be limited to information that SOMA actually holds and is legally required to provide.
If you choose to connect Google Calendar, SOMA requests read-only Google Calendar access.
SOMA uses the calendar event title, time, and location only to help you create Plan Ahead safety plans. Calendar data is context for planning, not a safety trigger.
Browsing calendar candidates does not start protection or notify Guardians. A Plan Ahead item is created only after you explicitly choose an event and confirm it.
SOMA does not keep ordinary safety information forever.
Each eligible piece of safety information has its own retention period based on when it was created.
Eligible ordinary safety information is normally retained for 14 days.
Eligible ordinary safety information is normally retained for 28 days.
Each day's information begins its own retention period when it is created.
For example, information created on one day may expire before information created several days later.
Your safety history therefore gradually expires over time rather than being deleted all at once.
If a Signal, SOS, Missing Person event, or other supported safety incident occurs while relevant safety information is still available, information connected to that incident may be preserved beyond the normal 14-day or 28-day period while the incident remains active.
Incident information may be kept until the incident is resolved.
Once the applicable reason for preserving the incident information ends, SOMA will handle that information according to its applicable retention and deletion rules.
When no incident requires information to be preserved for longer, eligible Live Witness recordings and other safety media follow the applicable retention period for the user's plan.
You can change supported account and app settings from within SOMA.
Depending on the feature, this may include information such as:
Some confirmed historical safety records cannot be edited after they have been recorded.
This is because changing historical safety records could affect the accuracy and integrity of information that may later be important.
You can request a copy of available personal information associated with your SOMA account.
Your available copy may include information such as:
Your copy may not include information that has already expired under SOMA's retention rules.
Data requests are not processed instantly.
After you make a request, SOMA will prepare the available information and may send it to the email address associated with your account when it is ready.
You can request deletion of your SOMA account from within the app.
When you request deletion, your account enters a 7-day deletion period.
During this period, SOMA will display the remaining time before deletion.
You may cancel your deletion request during the 7-day period through your SOMA settings or by signing back into your account where supported.
If you do not cancel the request, your account will be scheduled for permanent deletion after the 7-day period.
Deleting your account may remove:
Some information may need to be retained where required by applicable law or where an active safety incident requires temporary preservation.
When there is no legal or active safety reason to retain eligible information, it will be handled according to SOMA's deletion process.
SOMA uses technical and organisational safeguards designed to protect personal and safety information.
These measures include encryption when information is transmitted and security measures designed to protect information while stored.
Access to sensitive information is limited according to the SOMA feature being used and the permissions associated with that feature.
No online system can guarantee absolute security.
SOMA does not claim that its service is end-to-end encrypted.
Your SOMA PIN is used to protect important safety actions.
Your SOMA PIN is stored on your device rather than on SOMA's servers.
SOMA may use your PIN and related safety controls to distinguish between important protection actions without exposing sensitive safety information unnecessarily.
SOMA is intended for users aged 13 and older.
Users under 13 should not create a SOMA account.
Because privacy and children's data laws differ between countries, additional age or parental requirements may apply depending on where you live.
If we learn that personal information was collected from a child in a way that is not permitted under applicable law, we may take steps to delete the information or otherwise address the issue.
Parents and guardians can contact us at privacy@somasafety.app with privacy questions involving a young person.
SOMA is designed for users in multiple countries.
Your information may be processed or stored in countries other than the country where you live.
Where required, we take appropriate steps to protect personal information when it is processed internationally and to comply with applicable privacy laws.
Depending on where you live, you may have legal rights relating to your personal information.
These rights may include the right to:
These rights may differ depending on your country and may be subject to legal exceptions.
Some confirmed historical safety records may not be directly editable because SOMA is designed to protect the integrity of recorded safety information.
SOMA will continue to develop.
We may add, change, or remove features over time.
If a new feature materially changes how we collect, use, retain, or share personal information, we may update this Privacy Policy and provide additional notice where required.
If GONIALITHOS Technology Limited is involved in a merger, acquisition, restructuring, financing, or transfer of all or part of the SOMA business, information associated with SOMA may be transferred as part of that transaction where permitted by law.
Any new operator would remain responsible for handling personal information according to applicable privacy law and any commitments that continue to apply.
This section does not mean SOMA is currently being sold or transferred.
We may update this Privacy Policy when SOMA changes or when legal or regulatory requirements change.
When we make material changes, we may notify you through SOMA, by email, or through another appropriate method.
The Effective Date at the top of this policy shows when the current version became effective.
Your continued use of SOMA after an updated policy takes effect is subject to applicable law and any consent requirements that may apply.
If you have questions about privacy, your personal information, a data request, or this Privacy Policy, contact:
GONIALITHOS Technology Limited
Email:
privacy@somasafety.app
SOMA is designed to support personal safety by preserving context, providing safety tools, and helping users communicate with people they trust.
SOMA cannot prevent every emergency, crime, accident, disappearance, or harmful event.
SOMA is not a police service, emergency dispatch service, or replacement for local emergency services.
SOMA does not guarantee that an Angel will receive, see, or respond to a Signal immediately.
Where you are able to do so safely, contact the appropriate local emergency service when immediate professional assistance is required.
The public website provides this information without sign-in. It does not include the in-app Delete Account action.