Privacy Notice

Version: 2026-10-15-review-2 · Effective date: October 15, 2026

A consolidated convenience copy of the current published documents. Each document retains its own version and effective date. The versioned legal pages and archive remain authoritative.

On this page

Operator and contact

Soteria is currently operated by Daniel Ashraf Ekdawi, an individual based in Cairo, Egypt. Legal/contact address: 1 Amin Al Shamsi Basha Street, Hegaz Square, Heliopolis, Cairo, Egypt. Privacy/legal contact: [email protected]. No incorporated or registered business status is asserted. This notice explains processing; reading it or accepting Terms is not consent to every processing purpose. Arabic is the primary maintained legal text, with equivalent English support.

Information in the service

Accounts hold login identifiers, password hashes, security settings, sessions and recovery records. Persons have stable identities with separate global, Organization and Group profiles. Profiles can include names, contact details, optional birth dates, addresses, locations, relationships, photos and custom fields. Organizations may record memberships, roles, attendance, events, activities, challenges, points, announcements and reservation answers or uploads. These records can reveal religious participation and other sensitive information; collect only what is necessary and lawfully authorized.

Sources and recipients

We receive information from Account holders, Organization users, guardians, invited participants, reservation guests, support correspondents and reviewed imports. A Person’s record may therefore have been created by an Organization rather than by that Person. Authorized Organization/Group users see data permitted by their scope and feature rules; notification recipients receive the information addressed to them. Necessary operational access is available to the operator and service providers. Public images, authorized exports and downloaded/offline copies can leave the original access boundary. We may disclose information where lawfully required or necessary to address a substantiated security or legal claim, subject to applicable safeguards.

Why information is processed

We process information to operate accounts, apply scoped permissions, coordinate community work, deliver requested notifications and email, protect the service, support users and maintain recovery copies. We retain security/audit records, support correspondence and package/subscription history. Manual reservation payment evidence may exist; platform subscription payment processing is not enabled by this legal release. Optional AI import analysis sends selected uploaded information to the configured AI service/provider for a draft that requires review. Avoid unnecessary sensitive data in imports.

Purposes and applicable legal grounds

Account administration and requested platform functions may rely on steps to enter or perform the applicable service contract. Organizations must determine and document the lawful grounds for their own community-data purposes. Specific consent is required where applicable, including Soteria’s under-18 guardian rule and any optional marketing choice. Security, fraud prevention, necessary records and legal requests must have an applicable legal justification; a business interest is not assumed to be a standalone legal basis in every jurisdiction. Sensitive religious/child data and international transfers may require additional safeguards, permits or other legal conditions. Generic Terms acceptance or this notice does not replace them. We do not claim that all regulatory prerequisites have been completed.

Organizations, children and sharing

Organizations determine the information collected for their activities and who may access it. They must provide appropriate notices, establish lawful authority and verify guardian consent. Soteria requires specific, explicit, recorded, versioned, withdrawable and auditable guardian consent to process data of a Person under 18. A managed Person has a stable identity and scoped profiles but may have no Account: creating that record never accepts Terms or grants consent. Optional scoped DOB is not a universal age-verification system. Known minors without evidence are marked as requiring consent; existing data is not automatically consented or deleted. Current profile-write gates are limited, and comprehensive age/guardian verification and gates across all features remain unfinished. Organizations must not use an unguarded feature to bypass the under-18 rule.

Cookies and device storage

Soteria uses authentication/session cookies, locale preferences and local/offline storage for application operation. Push delivery uses device subscriptions when enabled. Maps/location features contact Google when used. This notice does not authorize optional marketing or unrelated tracking.

Providers and international processing

Current hosting, storage, backup and mail providers, and feature-conditional maps/AI services, are described on the Subprocessors / International Data Transfers page. Hosting, email, backups or selected features may involve providers outside Egypt. Confirmed configured regions and unresolved locations are stated separately. Better Stack monitoring is disclosed separately because the application strips user/request content; provider network metadata and contractual treatment still need verification. Disclosure, generic Terms acceptance and guardian consent do not themselves obtain any required cross-border permit/licence or complete provider safeguards. Those regulatory and contractual requirements must be resolved separately before the relevant processing.

Retention criteria

Active Account, Person, Profile and Organization information is retained while reasonably needed to provide the applicable service or fulfill the Organization’s legitimate data-management purpose, subject to a lawful basis. Closed/deleted operational data should be deleted or anonymized when no longer reasonably needed, subject to recovery, security/fraud prevention, legal claims, obligations and backups. Legal acceptance and consent history is preserved as reasonably necessary to demonstrate compliance and resolve disputes; withdrawal does not erase evidence of an earlier grant. Security/audit records are retained only as reasonably necessary for protection, investigation and compliance. Email usage accounting retains minimal delivery/accounting metadata, not message content merely for metering. Future financial records will require reconciliation, dispute and applicable accounting/tax retention. There is no implemented product-wide deletion/anonymization timetable: category review, legal holds and request handling still require operational decisions. Private recovery/history storage exists exceptionally to reconcile identity/profile/media conflicts and restore data; it needs periodic necessity review and deletion when recovery and other justified retention no longer apply. It is not ordinary active-profile storage.

Implemented retention and recovery limits

Local backup archives default to a 30-day cleanup threshold, configurable by operations. Encrypted off-site database backup selection keeps 14 daily, 8 weekly and 12 monthly snapshots. Encrypted R2 object mirrors preserve the current copy and move changed/deleted objects into dated history, with a 365-day history cleanup threshold. These cleanup/selection rules run with successful backup operations; they are not promises of erasure on an exact day. No immediate deletion from existing rotating/immutable recovery copies is promised. Restore procedures must account for approved deletion requests before returning restored data to ordinary use. Security maintenance prunes expired/consumed challenges and rate limits; inactive sessions are eligible after 30 days. Mailbox pruning makes sent-only threads eligible after 180 days and archived threads after 365 days, excluding unresolved deliveries. Offline device storage and authorized exports/downloads may survive server deletion; device clearing and recipient cooperation may be necessary. Other category-specific fixed periods are not yet approved.

Rights, withdrawal and complaints

Contact [email protected], or use the legal/contact address above, to request access, correction, deletion/anonymization where applicable, restriction or objection where available, withdrawal of a specific consent, or to raise a privacy concern/complaint. State the relevant Person/Account, Organization and request using a safe reference; never send passwords or recovery codes. We may verify identity proportionately and coordinate Organization-controlled data with its authorized contact. Do not send identity-document scans unless a defined need and protected channel have been agreed. Withdrawal stops authorization for future consent-dependent processing within its scope; it does not erase prior lawful processing or necessary evidence. You may also complain to the competent authority where applicable. Identity verification, request timelines and escalation procedures need operational confirmation; no unverified response deadline is promised.

Security and changes

We apply scoped access controls, Account security and private-file authorization, but no system guarantees absolute security. Public photos or shared files may have been copied by others. Legal documents have immutable published versions. Material contractual changes require the relevant fresh acceptance; editing a notice does not silently create consent.