How your data is stored
- Files you upload to the library, a Bid Room or a chat are stored encrypted at rest (AES-256).
- Your workspace data is separate from other organizations. Public tender data, such as notices and award history, is shared across all customers because it is public.
- Library documents marked as sensitive can be read only by owners and admins. Emma follows the same rule for the person she is working for.
How AI is used
- Reyda prefers EU-hosted AI model routes where they are available.
- AI requests are configured so that model providers do not collect your data.
- Emma treats the content of documents, emails and web pages as information, not as instructions. A tender document that says “ignore your previous instructions” does not change what she does.
- Emma works from what is saved in your workspace: documents, Bid Rooms, Goals and work, the Library and your company profile. She also uses what you share in the current conversation, but she doesn’t see your other conversations.
Connected apps
Each person connects their own SharePoint, Google Drive or Notion account in Settings → Integrations. An admin connects Slack for the whole company.- Emma’s access to SharePoint, Google Drive and Notion is read-only.
- Connected content is read live when Emma needs it. It is not copied into your library.
- Sign-in tokens are held by Reyda’s EU-hosted integration provider. Reyda does not store your passwords for these services.
- Viewers have no access to connected apps through Emma.
AI assistants
You can connect ChatGPT, Claude or another registered AI assistant to read your Reyda data.- Sign-in uses OAuth: you sign in on Reyda’s own page and approve read access. You never give the assistant your Reyda password.
- The assistant can only read, and only what your account can see. It can’t change anything in Reyda or start paid work.
- Review or revoke each connection in Settings → Integrations → AI assistants. Revoking stops access straight away.
Emma’s browser and workspace
When Emma browses the web or runs files, she works in an isolated environment. It can reach public websites only, not your internal network. You can watch Emma’s browser live and take control at any time. See Emma’s browser.Actions that need your approval
Emma can research and draft on her own, but she asks before she acts outside your workspace or makes a consequential change. You see an approval card such as Allow this action? with Yes and No. Examples include:- sending or replying to an email from Emma’s mailbox (you can edit the message first);
- creating a Bid Room;
- searching the web or opening a page, when your workspace is set to ask first;
- changing mailbox settings that widen who can reach Emma or let her send without asking.
Roles and access
Organization roles decide who can see and change what. Per-resource sharing lets you give guests access to one Bid Room or document only. See Roles and permissions.Deleting an account or workspace
You can ask Reyda to delete an individual user account or your whole workspace.- Access is disabled as soon as the deletion is scheduled.
- Erasure includes stored files and is completed within 30 days.
- When one user’s account is deleted, the company’s work in the workspace is kept.
- When a workspace is deleted, the data owned by that workspace is removed.
- Public procurement data stays, because it is not your data.
Sign-in is by email and password. Sign-in with Google or Microsoft is not available.