DRAFT — not yet reviewed by counsel

Privacy Policy

This policy explains what ascai & co, of 1 Kafr El Dawar Street, Heliopolis, Cairo, Egypt, does with personal data in Social Omni — a shared inbox that businesses use to talk to their customers on WhatsApp, Instagram, Messenger, Telegram and a chat widget on their own website.

There are two very different kinds of personal data here, and almost every question about this service has a different answer depending on which one you mean.

If you messaged a shop, ask the shop. It decides what it holds about you and whether to delete it. We will help them answer you, and we cannot answer for them. Section 7 says what to do if you cannot reach them.

1. Merchant data: what we collect and why

When you open or use a workspace we hold:

We do not use behavioural advertising, we run no third-party analytics or advertising trackers in the product. The dashboard uses a session cookie to keep you signed in and a short-lived confirmation cookie to protect the sign-in step. The confirmation cookie expires after ten minutes and is cleared when sign-in completes.

2. Customer data: what we process for merchants

On a merchant's instructions, and only for them, the service holds:

We do not sell it. We do not use it for our own purposes. We do not use it to train our own machine-learning models. Ordinary inbox intent detection runs on our own servers. Optional Creative & Voice services are different: when enabled and deliberately used, approved briefs, reference materials, scripts and voice conversations are processed by the providers described below.

Voice visitors receive an AI and processing notice before starting. Audio is processed to conduct the conversation; the supplied agent configuration disables stored voice recordings and limits provider transcript retention to seven days. A summary remains in the merchant's workspace for follow-up until removed under its retention instructions. This is not a promise that audio is never processed or that a provider keeps no records. Provider privacy settings, data-use terms, location and applicable transfer arrangements must be reviewed before the optional service is activated.

The merchant chooses the lawful basis for holding it and for messaging their customers, and the merchant must be able to show it. That obligation is set out in the Terms of Service, section 5.

Optional automation handoffs send only workspace/event identifiers, a creative or voice record reference, event type and time to the merchant's configured Zapier or Make workflow. They exclude customer names, contact details, messages, prompts and audio. The merchant controls the receiving workflow and its further actions. Booking links open the merchant's chosen service without automatically prefilling customer details. Contact and calendar exports are downloaded to an authorized team member's device; any subsequent import is that team's action.

The website chat widget keeps two values in the visitor's browser storage (localStorage) on the merchant's own site: a session token that expires after a day, and a visitor key that lets a returning visitor carry on the same conversation for up to 90 days after the widget last renewed it. Both are signed values tied to that one chat channel and a random visitor identifier; neither holds the visitor's name, contact details or messages. Clearing the site's stored data removes them, and the next visit starts a new conversation. A merchant whose own notice must describe device storage should describe these.

3. Where it is hosted, and what crosses a border

Data is stored in Hostinger managed hosting (server region pending verification); PostgreSQL remains in United States (AWS us-east-2, Ohio). Where that is outside the country a merchant is established in, storing the data there is itself a transfer out of that country, before any of the flows below.

Some data necessarily travels outside that region because the channels themselves are elsewhere:

Egypt

Egypt's Personal Data Protection Law 151/2020, with the Executive Regulations issued by Ministerial Decree No. 816 of 2025, treats transfer, storage or sharing of personal data outside Egypt as requiring both an adequate level of protection in the destination and a licence or permit from the Personal Data Protection Centre naming that destination. That obligation is in force today; the statutory grace period for reconciling an existing position ends 31 October 2026. There is no adequacy list and no standard-contractual-clause route: the licence is the mechanism.

This service is not that licence and not a substitute for one. If you are a merchant established in Egypt, the transfers described above — including storage in Hostinger managed hosting (server region pending verification); PostgreSQL remains in United States (AWS us-east-2, Ohio), where that is outside Egypt — are your transfers, and the licence, the registered data protection officer and — if you are established outside Egypt while processing Egyptians' data — the locally appointed representative are yours to obtain. We will give you the details of every destination, recipient and category of data you need to make that application, on request.

Saudi Arabia

The Saudi PDPL permits transfer outside the Kingdom without prior approval, subject to purpose limitation, no prejudice to national interests, a minimisation test, and the safeguard prescribed for the applicable case in the Transfer Regulation, together with a documented transfer risk assessment. The Saudi authority has published no adequacy list. Marketing without consent is among the things it has actively enforced.

United Arab Emirates

Federal Decree-Law 45/2021 has been in force since 2 January 2022. Its Executive Regulations have not been issued, and the parts of the law that depend on them — including the penalties schedule — are not yet operative. A merchant established in the DIFC or the ADGM is instead under that zone's own data protection regime, which is separate and stricter.

We do not claim to be "compliant with", "adequate under" or "in-region for" any of these laws. Where this policy says what a law requires, it is describing the merchant's obligation and ours, not asserting that either is discharged.

4. Who else touches the data

Our sub-processors, and why each one exists:

The last two categories exist only where a merchant has connected them, with that merchant's own credentials, under that merchant's own agreement with the vendor. We will give merchants at least 30 days' notice before adding or replacing a sub-processor in the first five categories.

5. How long we keep things

6. How it is protected

The full list, with what each measure actually is, is in section 4 of the Data Processing Agreement. In summary: connected vendor credentials are encrypted at rest with AES-256-GCM; the database connection is TLS with the server's certificate verified, against a pinned certificate authority or, for a publicly signed certificate, the standard trust store; sign-in is by single-use emailed link with no passwords to steal; queries made for a workspace go through a handle bound to that workspace, and the core records — contacts, conversations, messages, orders and shipments — reference each other through composite foreign keys, so the database refuses a link from one workspace's record to another's (some secondary links are single-column and rely on the bound query alone); and the dashboard is served with a content security policy, HSTS and same-origin form actions.

7. Your rights

If you are a merchant user, you can ask us to give you a copy of your account data, correct it, delete it, or restrict what we do with it. Write to hello@socialomni.online. We will answer within 30 days.

If you are a customer of a merchant — you messaged a shop, and the shop uses this service — the shop is the controller of your data. Ask the shop. They can export contact data, and the workspace owner can export workspace records. The current product does not provide individual correction or erasure controls; the merchant can contact hello@socialomni.online for help handling those requests. The workspace deletion control removes the entire workspace. We are obliged to help the merchant respond to your request. If you have asked the shop and had no answer, write to hello@socialomni.online with the shop's name; we will pass your request on and tell you we have. We cannot decide the request ourselves, because it is not our data to decide about.

You can also complain to the data protection authority where you live: in Egypt the Personal Data Protection Centre, in Saudi Arabia SDAIA, and in the UAE the UAE Data Office (or the DIFC or ADGM Commissioner if the business is in one of those zones).

8. Children

The service is not intended for children, and merchants must not use it to market to them.

9. Changes

We will post a new version here and email workspace owners before a material change takes effect.

10. Contact