DRAFT — not yet reviewed by counsel

Data Processing Agreement

This agreement governs how ascai & co, of 1 Kafr El Dawar Street, Heliopolis, Cairo, Egypt ("we", "the processor"), handles the personal data of your customers when you use Social Omni. It forms part of the Terms of Service, and where the two disagree about your customers' personal data, this document wins.

It applies to every workspace from the day it is opened. No signature is required to bring it into effect, and we will sign a countersigned copy on request.

1. Roles

You are the controller. We are the processor. You decide which of your customers are contacted, on which channel, with what message, and for how long their data is kept. We hold that data and act on it because you told us to.

Where you are yourself a processor for someone else, we are a sub-processor, and everything below applies as though "controller" meant your own controller.

Each of us is separately responsible for complying with the data protection law that applies to us. Nothing here shifts your obligations onto us or ours onto you.

2. Scope of the processing

Subject matter. Operating a shared inbox and order workflow for your business.

Duration. For as long as your workspace exists; section 9 says when that ends.

Nature and purpose. Receiving, storing, displaying, tagging and sending messages on your behalf; deriving order details from message text using deterministic rules that run on our own servers; creating, tracking and cancelling orders; sending broadcasts and automated messages you configure; passing order and delivery details to the storefront platforms and couriers you connect.

Categories of data subject. Your customers and prospective customers, and anyone else who writes to one of your connected channels.

Categories of personal data.

Special categories. The service is not designed for special-category data and you must not deliberately put any into it. We cannot prevent a customer typing something sensitive into a chat, and message content is stored as sent.

3. Our instructions

We process your customers' personal data only:

  1. on your documented instructions — which are, in the ordinary case, the settings, rules, broadcasts and actions your team takes in the product; and
  2. where a law we are subject to requires otherwise, in which case we will tell you before processing unless that law forbids it.

We will tell you if, in our opinion, an instruction breaks data protection law. We will not process your customers' data for our own purposes, will not sell it, and will not use it to train our own machine-learning models. Ordinary inbox intent detection remains local. Separately activated Creative & Voice services process the merchant's approved materials and consented voice interactions through the optional sub-processors listed in the Privacy Policy. Provider data-use settings, retention, transfer arrangements and the merchant's instructions must be reviewed before activation; this draft does not establish those arrangements by itself.

An enabled customer automation destination is a separate merchant instruction to send event/workspace identifiers, record references, type and time to that merchant's Zapier or Make workflow. It does not authorize sharing inbox content, voice recordings or creative materials with that destination. The merchant controls downstream workflow actions and any import of downloaded contact or calendar files; those exports do not establish marketing consent.

Everyone of ours with access is bound by a written confidentiality obligation that survives their engagement.

4. Security measures

In place

Committed, and not yet in place

We would rather write this down than let you assume it. Each of the following is planned; none of it exists today, and you should weigh that before putting sensitive workloads into the service.

For counsel: the two lists above should be restated as a dated annex, with the second list carrying target dates, before this document is put in front of a merchant who is themselves regulated.

5. Sub-processors

You give us general authorisation to use sub-processors. The current list, with what each one touches, is in section 4 of the Privacy Policy: the hosting provider, Meta Platforms, Telegram, Resend, Stripe, Sentry (error reporting, when enabled, receiving stack traces and request paths and never message content), and the storefront platforms and couriers you yourself connect. Optional ElevenLabs voice processing and Higgsfield creative generation are included only when explicitly activated for the agreed service; their data scope is stated in the Privacy Policy. Generated assets and voice agents need support-assisted provider cleanup before workspace closure.

Storefront and courier vendors are engaged by you, with your own credentials, under your own agreement with them; we pass them the data your configuration requires and nothing else.

We will give you at least 30 days' notice before adding or replacing any other sub-processor. You may object on reasonable data protection grounds within that period; if we cannot resolve the objection, you may terminate the affected part of the service and we will refund fees paid for the unused period. Every sub-processor is bound by written terms no less protective than these.

6. Personal data breach

If we become aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to your customers' personal data, we will notify you without undue delay and in any event within 72 hours of becoming aware of it, at the workspace owner's email address.

The notification will describe, as far as we know it at the time: what happened, when, which categories and roughly how many records and data subjects are affected, the likely consequences, what we are doing about it, and a contact who can answer follow-up questions. Where we do not have all of that within 72 hours we will send what we have and follow up.

Notifying your regulator and your customers is your decision and your obligation; we will give you what you need to make it. Egypt's Personal Data Protection Law sets a 72-hour notification duty on the controller, so the clock we run is set to leave you time.

7. Assistance

We will give you reasonable assistance, taking into account the nature of the processing and the information available to us, with:

We may charge for assistance that goes materially beyond this, and we will tell you the cost before we incur it.

8. Audit

You may audit our compliance with this agreement once in any 12-month period, and additionally after a breach affecting your data.

In the first instance we will answer a written questionnaire and provide any current third-party report we hold. If that does not satisfy a specific, articulated concern, you or an independent auditor bound by confidentiality may inspect, on 30 days' written notice, during business hours, without disrupting the service, and without access to any other merchant's data — which we will never grant, to you or to anyone. Each party bears its own costs unless the audit finds a material breach, in which case ours are yours.

9. Return and deletion

On termination, and at any time on your written request:

  1. Your workspace stays available to its owner for export, as one machine-readable file, at no charge, for as long as it exists. A workspace whose subscription ends becomes read-only; it is not deleted automatically.
  2. Deletion is carried out through the workspace deletion control, which removes the workspace from live systems in one statement. Where the product refers the owner to support instead — while card billing, creative generation or automation handoffs are in use — we complete the closure after reconciling them; the product has no operator tool for that step yet. We then instruct our sub-processors to delete what they hold for the workspace.
  3. Backups are the database provider's and age out on its schedule, which we have not yet verified (section 4). Until they do, they are not accessed for any other purpose.
  4. We keep only what a law requires us to keep — principally billing records — and it remains subject to this agreement for as long as we hold it.

For counsel: earlier drafts promised a 30-day export window after termination, deletion at its end, and backups that age out within 90 days. Nothing implements or verifies any of the three, so they are withdrawn here until the period is decided and the deletion job and backup facts exist to keep it.

If the workspace owner confirms deletion through the product and the request succeeds, the live workspace data is deleted immediately and is no longer available for export. Export before requesting deletion. The product directs the owner to support before deletion where billing or external services need reconciliation.

We will confirm deletion in writing on request.

10. International transfers

Data is stored in Hostinger managed hosting (server region pending verification); PostgreSQL remains in United States (AWS us-east-2, Ohio). The transfers that happen in normal operation, and the position under Egyptian, Saudi and UAE law, are set out in section 3 of the Privacy Policy. In short: Egypt requires a licence from its Personal Data Protection Centre naming each destination country, and offers no adequacy list and no standard contractual clauses; Saudi Arabia requires the safeguard prescribed for the applicable case in its Transfer Regulation plus a documented risk assessment; the UAE's Executive Regulations have not been issued.

For counsel — this clause is deliberately unfinished. The transfer mechanism between the parties is to be inserted here once the group's structure, the hosting region and the merchant's own jurisdiction are settled. It is likely to differ per market, and it may need to name the Egyptian licence number and the locally appointed representative. Do not treat the descriptive paragraph above as a mechanism; it is a statement of facts, not a safeguard.

11. Liability

Liability under this agreement is subject to the limit in section 9 of the Terms of Service, except where the applicable data protection law does not permit it to be limited.

12. Contact