Data Processing Agreement

Version 1.1 · in force since 3 November 2026
This is an English translation provided for information only. The Spanish version is the binding one and prevails in case of any discrepancy.

This Data Processing Agreement (the “DPA”) forms part of the General terms of contract of the StaffControl service and is entered into between the Customer, as controller (the “Controller”), and [To be completed], as processor (the “Processor”), in compliance with article 28 of Regulation (EU) 2016/679 (GDPR) and article 33 of Spanish Organic Law 3/2018 on Personal Data Protection and guarantee of digital rights (LOPDGDD).

Its content follows the European Commission’s standard contractual clauses between controllers and processors (Implementing Decision (EU) 2021/915, section II) and the guidance of the Spanish Data Protection Agency (AEPD), made specific to the service the Platform provides. The annexes form part of the agreement: Annex I (parties), Annex II (description of the processing by module), Annex III (security measures) and Annex IV (sub-processors).

In case of conflict between this DPA and the Terms of contract, the Terms of use or the Privacy policy, this DPA prevails on matters of personal data protection.

1. Subject matter and duration

The Processor processes on behalf of the Controller the personal data needed to provide the Platform service, to the extent described in Annex II. The processing lasts as long as the main contract and, afterwards, the time needed for the return and deletion set out in clause 11.

This agreement does not cover the processing the Provider carries out as controller of the contact and billing data of the Customer itself and of the people who represent it, or of technical data on use of the Platform for its security, which is governed by the Privacy policy.

2. Documented instructions

The Processor processes the data only on documented instructions from the Controller. Documented instructions are: (a) this DPA and the Terms of contract; (b) the configuration the Controller sets on the Platform: active modules and features, including artificial intelligence ones, access levels and permissions, location check on clock-in, retention periods for applications and recipients such as its payroll advisor or its technicians; and (c) the actions its users take on the Platform, for example ordering a new hire’s details to be sent to its payroll advisor. Any other instruction will be given in writing to hola@staffcontrol.app.

The Processor will immediately inform the Controller if, in its opinion, an instruction infringes the GDPR or other data protection rules, and may suspend carrying it out until the Controller confirms or changes it.

If Union or Member State law required the Processor to process the data differently, it will inform the Controller before processing, unless that law prohibits it on important grounds of public interest.

3. Purpose limitation

The Processor processes the data only for the purposes in Annex II. It does not use them for its own purposes, does not disclose them to third parties except to authorised sub-processors and to recipients designated by the Controller, and does not use them to train artificial intelligence models, whether its own or third parties’.

4. Confidentiality

The Processor only gives access to the data to the people in its organisation who need it to provide, maintain and support the service, and only to the extent strictly necessary. Those people have committed in writing to confidentiality or are under a statutory duty of secrecy, which continues after their relationship with the Processor ends.

The Processor’s staff only enter the Controller’s account (for example, viewing the Platform as the Customer sees it) to handle a request from the Controller, resolve an incident or protect the security of the service.

5. Security of processing

The Processor applies the technical and organisational measures in Annex III, which it considers appropriate to the risk under article 32 GDPR, bearing in mind that the Platform processes data about workers, location data at the moment of clocking in and, in some cases, special categories of data. It may replace them with others that provide an equal or higher level of security, without lowering the level described.

Special categories of data. The Platform does not ask for health data, but it may be revealed by the type of an absence (for example, sick leave) and by documents the Controller or its staff upload (sick notes, medical certificates). Documents are kept in private storage and are only visible to the person concerned and to those who manage the team’s documents. If the Controller has enabled the artificial intelligence feature that suggests a document’s type and expiry date, documents uploaded to the Documents module (except payslips) are sent once to the AI provider to make that suggestion; the Controller can switch it off.

The Controller configures its team’s access and thereby decides which user sees each piece of data. It is responsible for assigning appropriate levels and permissions, keeping accounts up to date and not uploading more data than necessary to the Platform.

6. Sub-processors

The Controller gives its prior general authorisation for the Processor to engage the sub-processors in Annex IV.

The Processor will inform the Controller in writing (by email and with a notice on the Platform) of any addition or replacement of sub-processors at least thirty (30) calendar days in advance, stating who it is, what processing it will carry out and where. Within that period, the Controller may object on reasonable grounds relating to data protection. If it objects and the parties cannot find a solution, the Controller may terminate the contract at no cost before the change takes effect, with a refund of the unused part of the annual fee.

If a sub-processor stops providing its service or seriously breaches its obligations, the Processor may replace it with shorter notice, informing the Controller immediately and preserving its right to object.

The Processor imposes on each sub-processor, by contract, data protection obligations equivalent to those of this DPA, in particular sufficient security guarantees; it is liable to the Controller for the sub-processor’s compliance; and it will provide the Controller, on request, with information about those contracts (and may redact confidential commercial information).

Recipients that the Controller itself designates on the Platform (its payroll advisor, its maintenance technicians, its point-of-sale provider) are not sub-processors of the Processor: the Controller decides on and manages the relationship with them.

7. International transfers

Some sub-processors are established outside the European Economic Area or may process data outside it. The Processor only makes or allows such transfers with one of the safeguards in Chapter V GDPR: an adequacy decision of the Commission (including the EU-U.S. Data Privacy Framework for certified entities) or the Commission’s standard contractual clauses (Implementing Decision (EU) 2021/914, module three, processor to sub-processor), with any supplementary measures required. Annex IV states the country and safeguard for each sub-processor.

Any other transfer requires a documented instruction from the Controller.

8. Data subjects’ rights

If a data subject contacts the Processor to exercise their rights (access, rectification, erasure, objection, restriction, portability or not being subject to automated individual decisions), the Processor will forward it to the Controller within five (5) working days at most and will not reply on its own unless the Controller asks it to.

The Processor assists the Controller in handling them, primarily with the Platform’s own tools, which allow the Controller to view, correct, export and delete the data of its employees, candidates and contacts. Where these are not enough, the Processor will help as far as reasonable.

9. Assistance to the Controller

The Processor helps the Controller meet its obligations on security (article 32 GDPR), notification and communication of personal data breaches (articles 33 and 34), data protection impact assessment (article 35) and prior consultation (article 36), taking into account the nature of the processing and the information available to it. In particular, it provides the description of the processing, the security measures and the technical information the Controller needs for its record of processing activities and its impact assessments (for example, on working-time records with location or on the use of artificial intelligence features with its staff).

It also provides documentation to inform its staff and the workers’ legal representatives, such as the template privacy notice for the team available on the Platform.

10. Personal data breaches

The Processor will notify the Controller, without undue delay and in any case within forty-eight (48) hours of becoming aware of it, of any security breach affecting the data it processes on the Controller’s behalf. The notification is sent to the email address of the Owner of the Customer’s account and, where possible, also as a notice on the Platform.

The notification will include, at least and as far as known: the nature of the breach, with the categories and approximate number of data subjects and records concerned; a contact point; the likely consequences; and the measures taken or proposed to address it and mitigate its effects. If not all the information can be provided at once, it will be provided in phases without further delay.

It is for the Controller to notify, where applicable, the supervisory authority within seventy-two (72) hours and to communicate the breach to data subjects where required; the Processor will assist with the information available to it. The Processor documents all security breaches, their effects and the measures taken.

11. End of processing: return and deletion

When the contract ends or the Controller closes its account, its data are kept for ninety (90) calendar days with no use other than allowing it to recover them. During that period it may ask for its data to be returned: a copy of all of them in a structured format (JSON) and the stored files, which the Processor will deliver within fifteen (15) days at most. If it signs up again within that period, it can recover its account as it was.

After those ninety days, the Processor permanently deletes the Controller's personal data, files and user accounts on the Platform. It only keeps, blocked and with no use other than meeting its own liabilities towards the Controller (article 33.4 of the LOPDGDD), the invoices and the billing and subscription data, for the period of its tax obligations (six years), and the proof of acceptance of the Terms and of this Agreement. In backups, the data are erased when their rotation cycle completes, at most thirteen (13) months later, and until then are not used except to recover the service after a disaster; if a backup had to be restored, the deletion is applied again. When finished, the Processor issues a deletion certificate listing what was deleted and what was kept, and gives it to the Controller on request.

Before that period ends, the Controller must keep the data the law requires it to retain, such as working-time records for four years: the Processor does not keep them on its behalf.

12. Information and audits

The Processor makes available to the Controller all the information needed to demonstrate compliance with this agreement and article 28 GDPR, and answers its questions within a reasonable time. It keeps the record of processing activities it carries out as processor (article 30.2 GDPR).

The Controller may audit compliance, itself or through an independent auditor bound by confidentiality, giving at least thirty (30) days’ notice, during working hours, without endangering the security or the data of other customers and at most once a year, unless there are well-founded indications of non-compliance or an authority requires it. Each party bears its own costs. The Processor may first address the audit with documentation: answers to questionnaires, a description of measures and reports or certifications from its sub-processors.

The Processor will cooperate with the supervisory authority when requested.

13. Controller’s obligations

The Controller is responsible for:

  • Having a legal basis for each processing operation it entrusts and fulfilling the duty to inform data subjects (employees, candidates, end customers and contacts). The Platform provides a template privacy notice for the team.
  • Informing its staff of the working-time records and, where applicable, of the location check on clock-in (article 90 LOPDGDD) and of the artificial intelligence features it uses with its staff (article 64.4.d) of the Spanish Workers’ Statute).
  • Configuring its team’s access and permissions according to what each person needs, and reviewing the configuration of the features (artificial intelligence, location, retention).
  • Assessing whether its processing requires an impact assessment and, if so, carrying it out.
  • Making sure that the recipients it designates (payroll advisor, technicians, point-of-sale provider) offer adequate guarantees.
  • Supervising the processing, including the audits in clause 12.

14. Liability

Each party is liable for its breaches of this DPA and of data protection law under articles 82 and 83 GDPR. If the Processor processes the data for its own purposes or breaches the Controller’s instructions, it will be considered a controller of that processing. Between the parties, the limitation of liability in the Terms of contract applies, with the exceptions set out there and without prejudice to data subjects’ rights.

15. Data protection contact

For any matter relating to this DPA, the Controller may write to hola@staffcontrol.app. The Processor has not appointed a data protection officer; if it does, it will inform the Controller and state it here.

16. Duration, changes and governing law

This DPA lasts as long as the Terms of contract. Confidentiality, deletion and any other obligations that by their nature must survive remain in force afterwards. It is amended under the procedure in clause 9 of the Terms of contract; changes to Annex IV, under clause 6. It is governed by the same law and jurisdiction as the Terms of contract.

Annex I. Parties

  • Controller: the Customer, identified by the details of its account on the Platform at the time of acceptance (company name, tax ID and registered office of its entity or entities). The person who accepts on its behalf is recorded with their name, email address, date and time, IP address and browser.
  • Controller contact: the email address of the account Owner, unless the Controller indicates another.
  • Processor: [To be completed], with tax ID [To be completed] and registered office at [To be completed]. Contact: hola@staffcontrol.app.
  • Activities: provision of the StaffControl service described in the Terms of contract; electronic acceptance together with the Terms of contract.

Annex II. Description of the processing

Nature of the processing: hosting, recording, organisation, storage, consultation, report calculation, export, disclosure on the Controller’s instructions and erasure of data, automatically and continuously while the contract lasts, through the Platform.

Data subjects: employees and other people who work for the Controller and use the Platform; candidates for its job offers; the Controller’s end customers who make reservations or orders; contact people at its payroll advisor, technicians and suppliers; and Platform users in general.

Duration and retention: that of the contract. During the contract, data are kept until the Controller deletes them, except for the automatic deletions indicated; when it ends, clause 11 applies.

By module (only data of the modules the Controller has active are processed):

Team and accounts (always)

Data: first name and surnames, nickname, ID card, foreigner ID or passport number, email address, phone number, photo (optional), store or workplace, employing entity, positions, access level and permissions, type of contract and working day, weekly hours, working days, start and end dates, hourly labour cost (visible only to those with that permission) and reason for leaving. Private onboarding data, with restricted access: Social Security number, date of birth, postal address and IBAN. Purpose: managing the workforce and access to the Platform; if the person allows it, birthday greetings in the internal inbox.

Shift planning (always)

Data: planned and published shifts, availability and unavailability, hours each person can work, rest-day patterns and shift swaps. Purpose: organising work. The schedule generator proposes rotas that a person reviews and publishes; it does not use artificial intelligence.

Time clock

Data: clock-ins, clock-outs, breaks, overtime, corrections and clock-in proposals and, if the Controller enables the location check, the device’s coordinates at the moment of clocking in, which are stored with the clock entry. There is no continuous location tracking. Purpose: working-time records (article 34.9 of the Spanish Workers’ Statute), calculation of hours and checking that people clock in at the workplace.

Absences

Data: requests, types, dates, balances and approvals of holidays, leave and sick leave. The type of absence may reveal health data (special category). Purpose: managing holidays, leave and sick leave.

Documents and contract signing

Data: contracts, payslips, copies of identity documents, certificates, supporting documents and other employment documents, with their expiry dates; for contract signing, the handwritten signature drawn on screen, the date and time, the signer’s IP address and browser, and the cryptographic fingerprints (SHA-256) of the original and signed document. Purpose: keeping and delivering employment documentation and evidencing the signature. Payslips may be read with AI to extract amounts, always with human review.

Recruitment

Data: the candidate’s first name, surnames, email address and phone number, CV, cover letter or comments, answers to screening questions, stage of the process, interview notes and, if the Controller uses it, a descriptive summary of the CV produced with AI, without any score or ranking. Purpose: managing recruitment processes. Retention: applications are deleted automatically when the period configured by the Controller ends.

Onboarding

Data: the new hire’s details and, if the Controller orders it, sending them by email to the payroll advisor the Controller designates (identification, identity document, Social Security number, date of birth, address, IBAN, contract terms and workplace), after approval by an authorised manager; contact details of the payroll advisor. Purpose: formalising the hiring and payroll.

Incidents and maintenance

Data: who reports, description, photos (in which people may appear) and history; contact details of the technicians (name, company, email and phone). Purpose: fixing breakdowns and maintaining the premises.

Tasks, checklists and internal inbox

Data: assigned tasks and who completes them, checklist answers, announcements, messages and reads, notifications and browser notification subscriptions. Purpose: internal communication and organisation. Retention: read notifications are deleted automatically after 30 days.

Reservations and orders

Data: the end customer’s name and phone number, products, dates and notes of the order. Purpose: managing the Controller’s reservations and orders.

Tips, profitability and reports

Data: tip amounts allocated to each person, hours and labour cost, and sales figures. Purpose: sharing out the tip pool and analysing the business’s profitability.

Point-of-sale integration

Data: daily readings of the Controller’s point-of-sale system (cash closings and tickets), from which employee identification, invoice customer data and free text are removed before storing them, except the reason for cash movements, which is free text and may contain a name if it was written that way in the point-of-sale system. Purpose: sales and production summaries, without assessing specific people. Retention: the copy of the readings and the cash reasons, two years.

Production, inventory, purchasing and suppliers

Data: mostly business data; regarding people, who records counts, waste, orders and deliveries, and the contact details of suppliers’ staff. Purpose: managing production, stock and purchasing.

Artificial intelligence features

Data: whatever each feature needs, sent once to the AI provider (for example, the document whose expiry date is suggested, the CV being summarised or the business data the assistant queries); for each use only metrics are recorded (feature, model and volume), never the content. Purpose: the assistive features described in the Terms of use, always with human review and switchable off by the Controller.

Annex III. Technical and organisational security measures

Measures the Processor applies today:

Access control

  • Separation of each customer’s data in the database through row-level security rules (Row Level Security): each user can only read and write their own company’s data.
  • Access levels (employee, manager, administrator, owner) and permission profiles configurable by the Controller, also enforced in the database for sensitive tables (contracts, payroll advisors, subscription, tax details, employees’ private data).
  • Employees’ private onboarding data (Social Security number, date of birth, address and IBAN) in a separate table, visible only to the person concerned and administrators, and masked on screen by default.
  • Critical operations only from the server (contract signing, sending to payroll advisors, subscription changes), with service keys kept only on the server, never in the browser.
  • Password authentication managed by the authentication provider (passwords stored as hashes, never in clear text), sessions with signed tokens of limited duration and a limit on attempts when signing in with an identity document.
  • Access blocked when a person leaves, with an optional read-only window for their own documents.

Files and encryption

  • Files (documents, payslips, contracts, CVs, incident and task photos) in private storage, accessed through short-lived signed links generated after checking permissions. Profile photos, which are optional, are served through a hard-to-guess public link.
  • Cryptographic fingerprints (SHA-256) of the original and signed version of each signed contract.
  • Encryption in transit (HTTPS with TLS) for all communications with the Platform.
  • Encryption at rest of the database, files and backups by the infrastructure providers.

Backups and continuity

  • Automatic backup every night of the database and all files, stored outside the main provider in storage located in the European Union.
  • Backup retention: daily, 35 days; monthly, 13 months; deleted or modified files are kept for one year.
  • Automatic alert to the Processor if a night’s backup fails.

Traceability and minimisation

  • Audit log of the administrative actions of the Processor’s staff on customer accounts (creation, data changes, modules, exports and deletions).
  • Prior approval by an authorised manager of the Customer to send data to the payroll advisor or notify a technician.
  • Location only at the moment of clocking in and only if the Controller enables it, with no continuous tracking.
  • Removal of employee and customer identification from point-of-sale readings before storing them.
  • AI features that can be switched off one by one, one-off sending of data, a provider that does not train on them and a usage log without content.
  • Automatic deletion of applications when the configured period ends, of read notifications after 30 days and of all of a company's data 90 days after it closes its account, with a final check that no record of it remains and a deletion certificate.

Organisational measures

  • Access by the Processor’s staff limited to those who need it, with a duty of confidentiality.
  • Periodic security reviews of the code and of the database access rules (the latest in June and October 2026), with the findings fixed.
  • Selection of sub-processors with a data processing agreement and safeguards for transfers (Annex IV).

Annex IV. Sub-processors

Authorised sub-processors, with the service they provide, where they process the data and the safeguard for transfers outside the European Economic Area:

Sub-processorServiceData locationSafeguard
Supabase Pte. Ltd. (Singapore)Database, authentication and file storageEuropean Union (Frankfurt, Germany), on Amazon Web Services infrastructure [confirm project region]Standard contractual clauses (Decision 2021/914) incorporated in its data processing agreement
Vercel Inc. (USA)Hosting of the web application and execution of server functions[confirm functions region: by default, USA (Washington D.C.)]; global delivery networkEU-U.S. Data Privacy Framework (certified entity) and its data processing agreement
Anthropic, PBC (USA)One-off processing for the artificial intelligence features; does not train models on the dataUSAStandard contractual clauses (Decision 2021/914) incorporated in its data processing agreement [confirm whether certified under the Data Privacy Framework]
Resend, Inc. (USA)Sending the Platform’s emails (invitations, alerts, messages to payroll advisors and technicians)USAEU-U.S. Data Privacy Framework (certified entity) and its data processing agreement
Cloudflare, Inc. (USA)Storage of backups (Cloudflare R2)European Union (storage with EU jurisdiction)Its data processing agreement with standard contractual clauses; EU-U.S. Data Privacy Framework [confirm]
GitHub, Inc. (USA)Running the nightly backup job: data pass through its runners, encrypted in transit, without being kept thereUSA [confirm]Standard contractual clauses in its data processing agreement [confirm the plan and applicable agreement]

Third-party services loaded in the browser

OpenStreetMap Foundation (United Kingdom): maps and address search when an administrator places a store on the map. That person’s browser requests the maps directly from its servers, which receive their IP address and the searched address. Safeguard: Commission adequacy decision for the United Kingdom.

Browser notifications: push notifications are delivered through the messaging service of each user’s browser vendor (for example, Google, Apple, Mozilla or Microsoft), end-to-end encrypted under the Web Push standard, so that service cannot read their content.

Card payment: if enabled in the future, the payment provider will process the Customer’s payment data to collect the subscription, as part of the relationship between the Provider and the Customer; it will not process data of employees or of the other data subjects of this agreement.