SECURITY
Who can access what? You decide.
Choose who can access which tools and data.
Leadership
- Silae
- Monthly totals
- Headcount
- Hidden :Payslips
- PostgreSQL
- sales
- subscriptions
- Hidden :users
- Sellsy
- opportunities
- quotes
- invoices
- Aircall
- Volumes
- Missed calls
- Hidden :Recordings
- Silae
Sales
- Sellsy
- customer records
- quotes
- Hidden :payments
- Aircall
- Own calls
- Call notes
- Hidden :Other teams
Closed : Silae, PostgreSQL
- Sellsy
Support
- PostgreSQL
- subscriptions
- Hidden :payments
- Aircall
- Support line
- Missed calls
- Hidden :Recordings
Closed : Silae, Sellsy
- PostgreSQL
HR
- Silae
- Payslips
- Monthly totals
- Headcount
Closed : PostgreSQL, Sellsy, Aircall
- Silae
| Team | Silae | PostgreSQL | Sellsy | Aircall |
|---|---|---|---|---|
| Leadership |
|
|
|
|
| Sales | Closed | Closed |
|
|
| Support | Closed |
| Closed |
|
| HR |
| Closed | Closed | Closed |
ACCESS PER MEMBER
The same tools, different access
Choose the sources
The admin grants connectors to the members who need them. A closed tool stays inaccessible from their assistant.
Limit the data
On connectors that support it, access can be scoped to payroll folders, projects or tables. Access to a tool does not grant access to everything.
Revoke access
Rights are checked on every call. Removing access takes effect on the next call, whichever assistant is connected.
WHAT PERSYST KEEPS
Only what it needs, encrypted when sensitive
Your tools' credentials
OAuth tokens, API keys and database access are encrypted (AES-256-GCM). They are only used for authorized calls.
The call log
Every call is traced: who, from which assistant, which tool, when and with what status.
A search index
A repository's code or a project's tasks are copied when search requires it. They remain your organization's property.
WHERE DATA GOES
To the assistant you chose
The conversation stays with the assistant
Persyst only receives tool calls, never the exchange between the member and their assistant.
The result goes to its provider
OpenAI, Anthropic or another provider processes it under its own terms. Persyst does not provide a model.
No training
Persyst does not use your organization's content to train AI models.
HOSTING AND GDPR
Hosted in France
Clever Cloud, in France
All Persyst infrastructure is hosted by Clever Cloud, in France.
Retention set by plan
The call log is kept for 30 days, 12 months or an agreed period, depending on the plan.
Your GDPR rights
TILTED SAS is the data controller. Write to rgpd@persyst.ai to access your data or have it deleted.
Questions
Frequently asked questions
Can access be cut off right away?
Yes. An admin removes a right, disables a source or cuts off a member's assistant; the change applies from the next call. Data an assistant has already received is not erased.
Can the AI change our tools?
With the company's access, members read. To create or edit, on connectors that allow it, the member connects their own account: the AI then acts with that account's rights, and the account is not shared.
Is our data used to train an AI?
Not by Persyst. With the assistant's provider, it depends on its plan and your settings: check its terms, especially for consumer plans.