Your family records stay in the family.

Who this policy covers

Sulala is a private family platform operated by DataEnabler. This policy applies to the public pages you are reading and to every module inside a family account: family core, family tree, memories, finance, vehicles and Quran.

The family is the boundary of the platform. A family account is created by its first owner, and membership grows by invitation — there is no public sign-up into an existing family.

Account and family identity

To create an account we need an email address, a password and the family and household names. Email is verified with a six-digit code before the family is created. A member may add a display name, phone number and avatar.

Invitations are bound to a household and a role. Only a hash of each invitation token is stored, the link expires after seven days and it can be used once. Roles decide what a member may see and change.

Sign-in sessions are recorded so a member can review active devices, revoke one device or sign out everywhere. Changing a password ends the other sessions.

• Account details: email, password hash, display name, phone, avatar and role.
• Session data: device sessions, revocation state and sign-in timestamps.

Content your family adds

Everything the family records belongs to the family: people and relationships in the tree, photos and videos in memories, accounts and loans in finance, vehicles and their documents, and Quran bookmarks and memorisation progress.

Photos are converted to WebP with thumbnails. The platform reads dates and GPS coordinates already present in the photo's EXIF metadata to place images on the timeline and map. Face detection may suggest identities; names are only applied when the family confirms them.

Finance records are entered by the family, and attachments such as statements stay inside the account. Vehicle documents and photos are stored in the family's file store. None of this content is used for advertising or sold.

How we use information

We use account data to sign members in, verify email, deliver invitations and recovery codes, enforce roles, keep sessions secure and show the right family to the right person. We use family content only to provide the feature that stored it.

We also use operational records — audit events, error logs and usage counts — to secure the platform, diagnose failures, support families and plan capacity. Billing information is used to manage trials and subscriptions.

When information leaves the family

Sulala does not sell family data, does not run advertising and does not publish family records. Access inside the platform is scoped to the family and checked on the server.

We rely on a small number of service providers to operate the platform. They receive only what their service needs: hosting and database infrastructure, an email service for verification and invitations, a payment provider for subscriptions, and a map provider when a map view is opened. Card details are handled by the payment provider and are not stored by Sulala.

We may disclose information when the law requires it, when it is necessary to protect the platform or its users, or with the family owner's instruction. Where a legal request concerns a family account, we aim to notify the account owner unless the law prohibits it.

Cookies and local storage

Sulala uses cookies and browser storage that are needed for the service to work. The language preference (Arabic or English) is kept in a cookie and in local storage so the next page opens in the same language. Authentication uses session cookies, and forms use anti-forgery protection.

There are no advertising cookies and no third-party tracking cookies on the public pages. Opening the billing flow may involve the payment provider's own cookies on its pages.

Security and retention

Family records are isolated by a family scope that is applied in the data layer, not by filters written per screen. Every file view is issued as a signed, expiring link — memory links last between one and sixty minutes — and roles are checked again on each service call.

We keep account and family data while the account is active. Deleted memories wait in a recycle bin before permanent removal, and identity, approval and finance events leave an audit trail that supports investigation and recovery. Backups may retain copies for a short operational period after deletion.

Your choices and rights

A member can view and correct their own profile, change their password and revoke devices. A family owner or clan head can update family records, invite or revoke members and export what the family has stored.

The platform provides exports that make access concrete: GEDCOM, Family.Show, HTML and KML for the tree, a ZIP archive for memories, and CSV for finance and vehicle reports. You can ask us for access, correction or deletion of other data by writing to the contact below. We may need to confirm that the request comes from the account owner before acting.

Some records cannot be erased immediately where they are part of an audit trail or a legal obligation; we will explain what remains and why.

Children in a family account

Children join only through an invitation from a parent or clan head, and the family role decides what they can edit. The family controls the content a child can see and the records a child can change.

We do not offer a separate public sign-up for children, and we do not use family content for advertising or profiling.

Changes and contact

When this policy changes materially we will update the date above and, where appropriate, notify the family owner by email or inside the account. Continuing to use Sulala after a change means the updated policy applies.

Privacy questions and requests can be sent to info@dataenabler.org. We reply within one business day.