Your data
How your organisation's data is kept separate, who can access it, and what emily can and can't write.
No certification to point to — controls instead
emily doesn't hold a formal GDPR/RGPD certification. The concrete controls are these: your data kept apart from every other organisation's, access controlled per person, and read-only access to your ERP.
Your organisation's data stays yours
Everything emily works with — reports, recordings, conversation history, CRM records — is scoped to your organisation. Nobody at another company using emily can see your figures, your recordings, or your team's conversations with her, and nobody on your team sees another organisation's.
Access is controlled per person
Within your organisation, what any one teammate can ask about is set individually — by company and by topic — not shared by everyone at once. See access by person, company and topic for how that scoping works and what a rep sees when they ask outside it.
Reports follow the same shape: you see your own, and managers see the organisation's.
Your ERP is read-only
Whichever way your ERP is connected, emily reads it. She can look up sales, invoices, balances, stock and purchasing, but she cannot edit or delete anything in your books. The one thing she writes is an order you've confirmed, on Cegid PHC with the direct connection, which lands as an unsigned draft invoice for your back office — see connect your ERP for the two connection options and what each covers.
Traceability
Changes emily makes inside the CRM are recorded with who, what, when and channel, and deletes are reversible and restricted to managers and admins — except for tasks, which any user can delete, and a note you wrote yourself, which you can ask emily to delete — see audit trail.
Next: what emily can't do yet
See limits and what's coming for the current edges of what's connected and what's still on the way.