Privacy Policy

1. Scope

El Solh Family OS is a private family coordination system. It is used by a small number of authorized family members to organize family information: calendars and events, tasks, reminders, school-related information, documents, and the family communications those records are built from.

It is not a public consumer product and it is not open to general sign-up. Access is by invitation into a specific family, and a person who is not an authorized member of a family does not create or read that family’s records.

2. Information we process

Not every category below applies to every family or every member. What is actually processed depends on which parts of the service a family has enabled and which integrations, if any, that family has connected.

• Account and profile information — the email address used to sign in, a display name, and the role a person holds within their family.
• Family and member information — which people belong to a family, invitations to join it, and how members relate to the records they own or are responsible for.
• Coordination records — calendar events, tasks, reminders, and the schedules built from them.
• School-related information — school profile details, communications from a school, and documents a school or a family member provides.
• Documents— files a family member uploads or files into the family’s document library, and information extracted from them for review.
• WhatsApp messages and supported media— where the WhatsApp integration is enabled for a family, the content of messages sent to the Family OS WhatsApp account, the sender’s WhatsApp identifiers and display name, message identifiers and timestamps, and delivery or webhook metadata.
• Email-derived school communications — where a family has configured the Gmail integration, messages and attachments from approved school senders in the connected mailbox.
• Technical, security and audit metadata — sign-in events, message and delivery identifiers, timestamps, webhook metadata, and records of which member reviewed, approved, corrected or rejected what.

3. Why we process it

• To coordinate a family’s schedules, tasks and reminders.
• To organize school information and family documents in one place.
• To interpret trusted family inputs and propose events, tasks, reminders and family facts for a family member to review.
• To present that information to authorized family members for human review and decision.
• To operate, secure and audit the service, including preventing duplicates, abuse and unauthorized access.

4. How AI is used

AI is used to interpret and summarize information a family sends to Family OS. It is not used to decide who may see or change anything. Authorization, identity resolution, validation, execution and audit are handled by deterministic server-side code rather than by a model.

Where the review gate applies, a durable family fact derived by AI — for example a child’s year group read from a school letter — is stored as a proposal together with the passage it was drawn from, and a family owner or administrator must review it before it becomes a canonical family record. AI does not apply those facts itself.

Providing this functionality means family information may be sent to a third-party AI provider for interpretation. It is not used to advertise to you.

5. WhatsApp and Meta

Where the WhatsApp integration is enabled for a family, messages sent to the Family OS WhatsApp account — and supported media attached to them — may be processed to provide the family-assistant functionality that was asked for: recognizing the sender as an authorized family member, and proposing events, tasks, reminders and related records for a family member to review.

Media handling is gated separately from message handling and is not enabled by default. Where it is not enabled, media sent to the service is not downloaded or interpreted. Messages from senders who are not authorized family members do not create family records.

Family OS also uses a separate, non-production Meta application for technical verification of this integration. It exists so the integration can be confirmed to behave as expected; it is not a feature offered to family members and it is not part of the family service.

6. How information is shared

We do not sell personal data. We do not share personal data with advertisers, and we do not use it for advertising or ad targeting. One family’s data is not shared with another family.

Service providers process data on our behalf only as needed to run the service — for example hosting and application delivery, database and file storage, authentication, transactional email, messaging delivery, and AI interpretation.

We may also disclose information where we are legally required to do so, or where it is necessary to protect the security and integrity of the service.

7. Access and security

Access to family data is restricted to authenticated members of that family, according to the role each member holds. Authorization is enforced on the server rather than in the browser, and privileged actions are recorded in audit records.

No system can be guaranteed to be completely secure, and we do not claim otherwise.

8. Retention

There is no single retention period that applies to everything in Family OS. Information is kept for as long as it is needed to run the family service and to meet operational, security and audit requirements, subject to the retention and deletion controls the service provides.

Retention of stored media is configurable for a family and is applied by a retention process that is turned on deliberately rather than by default. Where it has not been enabled for a family, stored media is not deleted automatically on a schedule, and you should not assume that it is. Content that fails admission — the check that decides, from the file itself, whether it is a type Family OS stores at all — is purged rather than kept. Family OS does not scan files for malicious content, and you should not treat a stored file as having been checked for it.

Where media is purged, the record of where information came from — which document it came from, and the short excerpt a decision was based on — may be kept so that a record created months earlier can still be explained. Records kept for security, audit and integrity reasons are retained on their own terms, and are not removed simply because the content they describe was deleted.

9. Your choices and deletion

You can ask us to delete the Family OS data that relates to you. Requests are handled manually, and the process — what to send, how we verify a request, and what we may need to keep — is described on the data deletion instructions page.

10. Children’s information

Information about children is processed only inside the private family system, under the control of the adult family members who administer that family.

11. Changes to this policy

We may update this policy. Changes are published on this page with a revised “last updated” date.

12. Contact

For privacy questions, or to make a deletion request, contact elsolhfamily@gmail.com.