Data Processing Agreement
For the contact and customer data you keep in Magic CRM, you are the data controller and Magic CRM is your data processor (GDPR Art. 28).
Subject matter, nature, purpose and duration
Subject matter and purpose: we store and process the data your organization keeps in Magic CRM (companies, contacts, deals, notes, tasks, quotes, files, and what your integrations sync) to provide the service to you.
Nature: storing, organizing, showing and searching the data, syncing it with the integrations you connect, and passing it to the AI assistant a user connects, at that user’s request.
Data subjects: your users, and the people your organization keeps records about, such as contacts at your customers, prospects and suppliers.
Types of personal data: names, job titles, business contact details (email, phone, address), notes and activities, deals and quotes, files you add, calendar meetings, and your users’ account data. Do not store special categories of data (GDPR Art. 9) in Magic CRM.
Duration: as long as the contract lasts, and afterwards until the data is deleted as described below.
Our obligations as processor
Instructions: we process your data only on your documented instructions, which are the Terms, this agreement, and what your users do in the app. If we think an instruction breaks data protection law, we tell you.
Confidentiality: everyone at Magic CRM who can reach your data is bound to confidentiality. We do not read your organization’s records to run the service; when a fault can only be investigated in your data, we look at it read-only, and only as far as needed.
Security: we apply the technical and organisational measures in the annex below.
Assisting you: we help you answer requests from data subjects, and with impact assessments and consultations with the supervisory authority, as far as our part of the processing allows. Most requests can be answered in the app; for the rest, write to us.
Breach notification: we tell you without undue delay, and no later than 48 hours after we become aware of a personal data breach affecting your data, with what we know and what we are doing about it, and we keep you informed.
Deletion or return at the end of the contract: on request, we return your data within 30 days in a common machine-readable format, and then delete it, as described in the Terms. Copies in backups are deleted as the backups expire. We keep nothing unless the law requires it.
Audits: we give you the information needed to show that we meet our obligations under Art. 28. You, or an auditor you appoint who is bound to confidentiality, may audit us once a year with 30 days’ notice and at your cost, and after a personal data breach.
Annex: technical and organisational measures
Separation of organizations: every record belongs to one organization, and the database itself decides on every request what the signed-in person can read or change (row-level security). The app’s servers hold no key that bypasses these rules.
AI assistants: an assistant acts with the connecting user’s own sign-in and permissions. Database questions it writes itself run read-only, with limits on rows and on time.
Encryption: connections to the app and to the database use TLS, and emails are sent only over encrypted connections. Our database provider encrypts stored data and backups (AES-256). Outlook access tokens are encrypted again, with a key kept outside the database.
Access: users sign in with Google, Microsoft, an emailed link or a password of at least 10 characters, and an email address must be confirmed first. Sessions expire. When an administrator resets a member’s password, all of that member’s sessions end, and the reset is recorded.
Integrations: the Business Central sync and the calendar sync each have an account of their own that can reach only what they need.
Staff access: production credentials are held only by the people who operate the service, in a secrets store, and are used for deployment and maintenance, not to read customer records.
Development: no secrets in the code; dependencies and container images are scanned for known vulnerabilities; changes are deployed through an automated pipeline.
Recovery: the database is backed up by our database provider.
Sub-processors
You give us general authorisation to use sub-processors. The current list is on the Sub-processors page; changes are announced there 30 days in advance, and you can object as described there.
We bind each sub-processor to data protection obligations equivalent to these, and remain responsible to you for it.
Integrations
Business Central: if you connect it, customer, contact and order data is synced between your Business Central and your organization, through an account of the sync’s own that can reach only what the sync needs. What is sent in each direction is described on the Help page on the Business Central sync.
Outlook calendar: if a person connects their calendar, the meetings assigned to them are kept in their calendar in both directions, and the rest of their calendar is read.
Getting a signed copy
This agreement is part of the Terms and applies as soon as you accept them, without a signature. If you need a signed copy for your records, write to the contact address at the end of this page.
Company details
- Company
- [YOUR COMPANY NAME]
- Fiscal code (CUI)
- [YOUR CUI]
- Trade Register number
- [YOUR TRADE REGISTER NUMBER]
- Registered address
- [YOUR REGISTERED ADDRESS]
- Contact
- contact@magic-crm.ro