How Adreviso handles personal data entrusted to it by a business using a workspace.
Last updated
On this page
Status and parties
This agreement is available for review before workspace registration opens. When workspaces open, the organization’s authorized representative will be able to accept the applicable dated agreement before entrusting personal data to Adreviso.
The organisation identified in the order or workspace is the controller. If it acts for its own client, it is a processor and confirms its authority to appoint a subprocessor. Mighty Adv Mateusz Berkowicz, ul. Kazimierza Morawskiego 5/127, 30-102 Kraków, Poland, VAT ID PL6852306158, acts as processor or subprocessor, as applicable. Contact privacy@adreviso.com about personal data or an incident.
The organisation’s contractual claims under this DPA and the workspace terms share the applicable cap and exclusions in the Liability section of the workspace terms, subject to its exceptions. This preserves the rights of individuals, the powers of supervisory authorities and the statutory right of contribution after full compensation described below.
This agreement applies to personal data processed on the organization’s instructions in a workspace. Browsing the website, using a local tool, requesting a quote or opening a client review link does not appoint Adreviso as your processor. Invited team members agree to the terms for their own use.
The operator acts as controller for its own purposes, including account administration, service security and handling support enquiries, as described in the privacy policy.
1. Instructions and confidentiality
The organisation determines the purpose and recipients. Documented instructions comprise this agreement, the order, authorised users’ actions in the application and additional written instructions. The operator follows these instructions, including for international transfers. If EU or Member State law requires processing, it informs the organisation in advance unless that law prohibits notice on important grounds of public interest.
The operator immediately informs the organisation if it considers an instruction to infringe data protection law. Access is limited to authorised persons subject to confidentiality. Entrusted materials are not used in the operator’s marketing or to train models.
2. Subprocessors and transfers
The organisation gives general written authorisation for the subprocessors listed in Schedule C. Before adding or replacing a subprocessor, we will email the workspace owner with its name, services, processing locations and proposed start date. The organisation has at least 14 full calendar days after receiving the email to object on data protection grounds at privacy@adreviso.com. We will not give the new subprocessor access to the organisation’s data during that period or while a substantiated objection remains unresolved.
If a substantiated objection cannot be resolved, the parties agree an alternative or how to end the affected service and return the data. The operator binds each subprocessor to at least the same data protection obligations and remains responsible to the organisation for their performance. A transfer outside the EEA requires documented instructions and compliance with Chapter V GDPR. The hosting region alone does not determine where support personnel can access data.
3. Rights requests, incidents and audits
The operator assists the organisation through appropriate technical and organisational measures, insofar as possible, with requests to exercise individual rights. It forwards requests it receives to the organisation. Taking account of the information available, it also assists with security, breach notifications, impact assessments and prior consultation with the supervisory authority.
On becoming aware of a breach of entrusted personal data, the operator notifies the organisation without undue delay. It provides the available facts, including affected categories and approximate numbers of people and records, likely consequences, a contact and measures taken or proposed. It sends an initial notice without waiting for a complete investigation and supplies further information as it becomes available.
The operator makes information needed to demonstrate compliance with Article 28 GDPR available and allows and contributes to audits and inspections by the organisation or its auditor. Access arrangements protect other customers’ data while preserving statutory audit rights. Send audit requests and urgent incident reports to privacy@adreviso.com.
Data subjects retain their right to compensation under Article 82 GDPR. A party that pays full compensation may recover from other responsible controllers or processors the share corresponding to their responsibility for the damage, as provided in Article 82(5) GDPR.
Schedule A. Processing particulars
The organisation uses the service to manage campaigns and share materials with selected reviewers. On its instructions, the operator collects, stores, organises, validates and converts creatives, generates previews, shares selected versions, records decisions, backs up data and deletes them. Processing lasts for the service and the time needed to return or delete data under Schedule D.
Data may concern team members, employees, contractors, client representatives, guests and people pictured or heard in creatives. They include names, email addresses, roles, assignments, comments and tasks, attachments, file versions, images and voices, technical metadata, approval decisions and timestamps.
The organisation is responsible for its legal basis, rights in the materials and choice of link recipients. Data covered by Articles 9 or 10 GDPR and data requiring safeguards beyond those agreed must not be uploaded.
Schedule B. Technical and organisational measures
Connections to the panel and previews use HTTPS. Access depends on organisation membership and role and the database applies row-level access controls. Two-factor authentication is optional. Client links have a defined scope and can expire or be revoked. Active HTML creatives run on a preview domain separate from the panel.
Service credentials are separated by function. Application backups are encrypted before being written to external storage. The operator monitors availability, backups and disk capacity and tests restoration in an isolated environment. Users should protect credentials, limit recipients and report suspected unauthorised access.
Schedule C. Services and recipients
The following services process workspace data under our instructions to the extent they deliver the functions described. The organisation’s general authorisation, advance notice of a change and opportunity to object are described in section 2.
OVH Sp. z o.o. (Poland) provides our application servers and file storage in France. The application stores original files, previews and working versions there. OVHcloud also hosts this website. Its Zimbra mailbox service receives messages sent to support, privacy and abuse. Each service receives the data needed for its own task.
Supabase provides PostgreSQL and authentication. The production project is in Paris (eu-west-3). Data includes account and membership records, invitation and session information, campaign metadata, tasks, comments and approvals. The public DPA identifies Supabase Pte. Ltd. (Singapore). Support or security personnel outside the EEA may access data under the conditions of the DPA. The DPA provides for standard contractual clauses where applicable. The project region describes hosting, not every place from which support can be provided.
Brevo delivers transactional messages, including login and recovery messages, invitations and workspace notifications. It receives the recipient address, message content and delivery information. Brevo SAS (France) is the entity identified by its standard terms for a customer in Poland. We have configured Brevo to retain delivery logs for one month for all senders and to disable stored previews of new transactional emails.
Hetzner Online GmbH (Germany) provides the Storage Box in Falkenstein, Germany, used for encrypted workspace database and file backups. Backup archives are encrypted before transfer. Access to the repository and decryption keys is restricted.
For a transfer outside the EEA, the applicable basis depends on the recipient, country and onward access. We use an applicable adequacy decision or appropriate safeguards, including the relevant standard contractual clauses where required. To ask which basis applies, or request a copy or description of the safeguards, email privacy@adreviso.com. Current public supplier terms and lists are available from the suppliers; the applicable account contract governs the individual service.
Paddle will act separately as reseller and controller for orders. UptimeRobot checks availability. Neither receives workspace files for these activities.
Schedule D. Return, deletion and backups
At the end of the service the organisation chooses return or deletion. Email privacy@adreviso.com. We verify the requester’s authority, agree the scope and a secure delivery method, and confirm the result. Deleting one login or revoking a link does not instruct us to delete the whole organisation.
The owner or an authorized representative can email support@adreviso.com or privacy@adreviso.com without signing in. After a trial or subscription ends, the deadline for requesting an export is the end of the 30th calendar day after access ends, in UTC. We use the time our mailbox receives the request. For a timely request we preserve the requested materials while we verify authority, agree a secure handover and deliver the export, even after that day.
For an ordinary workspace export, you have at least 14 calendar days to respond once you receive our request to confirm your authority. A separate 14-day collection period starts once you have both the working, secure download and our collection instructions. We send a reminder for each unanswered step and allow at least three further calendar days after it reaches you. If you reply, report an access problem or agree an extension with us, we keep the request open. If you remain silent, an operator may close the request after all these periods and the original request window have ended. Closure requires a separate review before deletion. These limits do not apply to statutory switching or data subject requests, or override a legal duty to preserve data.
If you are moving to another service, contact us before disconnecting your workspace. Include the workspace name, your intended destination or storage environment and the categories of data you need. We will confirm scope, timing, delivery and how to verify your copy. Any mandatory rights to switch providers, receive exportable data or retrieve it after the transition period continue to apply.
Our workspace export includes original files and previews, workspace and campaign records, placements, versions, sets, tasks, comments and decisions. Structured records are supplied in JSON. A file map connects versions to their files and SHA-256 checksums. The export excludes passwords, session credentials and private access tokens. We agree how to deliver any additional material within the requested scope.
For a planned permanent closure, the workspace owner receives at least 60 calendar days’ notice. The panel and client links close on the notified date. An authorized representative may request an export during the notice period and for at least 30 calendar days after closure. We keep timely requests open for secure handover, subject to the ordinary export follow-up procedure in Schedule D. The retrieval window is separate from the backup deletion period.
Once the organisation instructs deletion, after any timely export request has been fulfilled or properly closed under the ordinary export procedure in Schedule D, we verify removal from the live workspace. For residual workspace backups the technical target is 21 days and the maximum is 30 days from that deletion instruction, subject to any retention required by EU or Member State law. Access to residual copies is restricted to recovery. Before reopening a restored service we reapply recorded deletion instructions and verify the result.
Where another organisation independently holds identical file content, we remove the departing organisation’s reference and access. The other organisation retains its authorized copy. A recipient may also have saved a file before a link was revoked.
Recovery layers include the encrypted application repository, infrastructure backups and database-provider recovery points where enabled. Their schedules and scope differ. We keep deletion instructions outside the restored database. Support correspondence has its own retention period in the privacy notice.