This public Data Processing Agreement sets out the proposed standard terms under which Alexandre Geiss, entrepreneur individuel (EI), using the business name App Engineering Design, processes personal data for GOSO customers. The provider’s address is 7 Rue du Ruisseau, 57645 Noisseville, France; SIREN 840 392 013; SIRET 840 392 013 00024.
For each contract, Customer means the professional or organisation identified in the accepted quotation, order form or service agreement. This DPA becomes binding when that agreement expressly incorporates its identified version and the applicable schedules. Publication alone does not form a contract. Customer names, addresses and contacts remain in private contractual records.
1 Roles and instructions
This DPA applies to Customer Personal Data processed to deliver the contracted service. The Customer acts as controller, or as a processor authorised by its controller to appoint the Provider as subprocessor. GDPR terms have the meanings given in Regulation (EU) 2016/679. The parties agree any additional terms required by another applicable regime, including Regulation (EU) 2018/1725, before processing subject to it.
The Provider processes Customer Personal Data only on documented instructions, including instructions about international transfers, unless Union or Member State law requires otherwise. Where permitted, it informs the Customer of that requirement before processing. The agreement, authorised configurations and lawful written support requests form part of those instructions. The Provider immediately informs the Customer if it considers an instruction to infringe applicable data-protection law.
The Provider does not sell Customer Personal Data, use it for advertising or train general-purpose AI models on it. Separate processing for the Provider’s own purposes is not authorised by this DPA. Enquiries, invoicing and business administration are addressed in the Privacy Policy; support and security processing performed on the Customer’s behalf remain within this DPA.
2 Customer responsibilities and confidentiality
The Customer determines lawful purposes and legal bases, provides required information to individuals, appoints authorised users and controls its sharing instructions. It minimises data and excludes special-category and criminal-offence data unless a written supplement expressly authorises the processing and its safeguards. A Customer acting as processor must have authority to issue the relevant instructions.
The Provider ensures that authorised persons are bound by confidentiality and have access only as needed for their tasks. Confidentiality continues after their involvement ends. Customer responsibilities do not reduce the Provider’s own duties under this DPA or applicable law.
3 Security
The Provider implements appropriate technical and organisational measures under Article 32 GDPR, taking account of the processing, risks, state of the art and implementation costs. Annex 2 describes application measures. The Provider shall document the security arrangements for the contracted environment before processing Customer Personal Data. Measures must address confidentiality, integrity, availability, resilience, restoration and regular evaluation.
Changes to safeguards must not materially reduce the agreed overall protection. Specific service levels, recovery targets or certifications apply only if expressly agreed and substantiated. The Customer is responsible for suitable management of its devices, permissions and external recipients, without relieving the Provider of its responsibilities.
4 Subprocessors
The Customer grants general written authorisation to the subprocessors identified in the completed supplier schedule incorporated into its agreement. The Provider gives at least 30 days’ advance written notice of a proposed addition or replacement, including purpose and locations. The Customer may raise a reasoned data-protection objection within 15 days of receipt.
The parties seek a reasonable alternative before the proposed subprocessor processes the affected data. If they cannot resolve the objection, the Customer may terminate the affected service before the change takes effect, without a termination penalty, and receive a proportionate refund of prepaid unused fees for that service. The notice mechanism does not permit use of an unapproved provider before its applicable conditions have been satisfied.
The Provider imposes obligations offering at least the protection required by this DPA for the delegated processing and remains fully liable to the Customer for its subprocessors’ performance of those obligations. Relevant supplier information is made available with appropriate confidentiality protections.
5 Locations and transfers
The Provider shall identify processing, backup and support locations in the supplier schedule supplied to the Customer before the relevant processing begins. Changes follow Section 4. Processing locations and international-transfer safeguards form part of the agreed processing arrangements.
A transfer outside the EEA requires documented instructions, a valid Chapter V GDPR mechanism and any necessary supplementary safeguards. The actual countries, recipients and mechanisms must be identified in the contractual schedules. The Provider assesses legally binding disclosure demands, limits any disclosure to what is required, informs the Customer unless prohibited and challenges unlawful or disproportionate demands where appropriate.
6 Rights requests and compliance assistance
The Provider forwards requests concerning Customer Personal Data to the Customer’s designated privacy contact without undue delay. It responds substantively only on the Customer’s instructions or where required by law. Taking account of the processing, it provides appropriate assistance with access, rectification, erasure, restriction, portability and other applicable rights.
Taking account of the information available to it, the Provider assists with Articles 32 to 36 GDPR, including security, breach notification, impact assessments and prior consultation. The parties coordinate promptly to meet legal deadlines. Any agreed charge for exceptional assistance must not obstruct mandatory obligations.
7 Personal data breaches
The Provider notifies the Customer without undue delay after becoming aware of a breach affecting Customer Personal Data. An initial notification is not delayed until the investigation is complete. The Provider describes, as information becomes available, the nature of the breach, affected data and individuals, likely consequences, measures taken or proposed and a contact for follow-up.
The Provider contains and investigates the incident, preserves relevant evidence and provides updates without undue delay. The Customer determines its notifications to authorities and individuals unless law requires the Provider to act separately. Notices go to the Customer’s designated incident contact or, if none is designated, its primary contractual contact, using an agreed backup channel where necessary.
8 Information and audits
The Provider makes available information necessary to demonstrate compliance with Article 28 GDPR and this DPA and allows and contributes to audits, including inspections, by the Customer or its appointed auditor. Reports may assist the review but do not replace audit rights that remain necessary.
The parties coordinate reasonable notice, scope, confidentiality and secure access to protect other customers and avoid unnecessary disruption. Urgent incidents and supervisory-authority access are not obstructed by these arrangements. Each party ordinarily bears its own internal costs; exceptional external costs may be agreed in advance without restricting mandatory rights.
9 Return deletion and duration
At the Customer’s choice, the Provider returns or deletes Customer Personal Data at the end of the processing service and deletes existing copies, unless Union or Member State law requires retention. Annex 4 sets out the exit requirements. Legally retained data is restricted to the required purpose and period.
Backup copies awaiting expiry remain protected and are not used for another purpose. If a backup is restored, applicable deletion instructions must be reapplied. On request, the Provider confirms completed return and deletion activities and explains lawful remaining retention. It does not represent that it can erase independent copies on Customer devices or held by external recipients.
This DPA continues while the Provider processes Customer Personal Data. Confidentiality, return, deletion and assistance duties survive as necessary. It prevails over inconsistent service terms on personal-data processing. Mandatory law and binding transfer clauses retain priority. Website changes alone do not amend an agreed DPA or remove individuals’ statutory rights.
Annex 1 Processing and contacts
Subject and purpose: providing the contracted GOSO observation, corrective-action, work-order, collaboration and reporting functions. Operations include collection, recording, organisation, storage, retrieval, authorised display and sharing, notifications, synchronisation, support, export and deletion, with backup where specified in the production schedule. Processing is continuous or event-driven during the service and agreed exit period.
Individuals: authorised users, customer and contractor personnel, external work-order recipients, and other people lawfully mentioned or depicted in project content, including occupants or visitors. Data includes names, professional contact details, identifiers, memberships, permissions, operational records, form values, comments, assignments, history, documents, quotations, photographs, video, audio, asset and location references, and associated access or delivery metadata.
Special-category and criminal-offence data are excluded from the standard scope. Any exception requires a prior written supplement specifying categories, purposes and safeguards. The contracted modules and integrations determine which of the described operations apply.
Customer identity, address and role are those in the accepted service agreement. Privacy and incident contacts are designated there or subsequently notified by an authorised representative. If no separate contact is designated, the primary contractual contact is used. The Customer keeps these details current.
Provider privacy and incident contact: Alexandre Geiss, contact@goso.cloud. Alternative business contact: contact@appengineering.design; telephone +33 6 31 22 81 00. These contact details do not create a 24-hour response commitment; any specific escalation arrangement is agreed privately.
Annex 2 Application security measures
Passwords and sessions: password credentials are hashed using Argon2. Access tokens are signed and time limited; the API validates their signature, issuer, audience and expiry. Refresh secrets are stored as hashes on the server, rotated on renewal and revocable. Revoking a refresh session is not a promise that every already-issued access token is immediately invalidated.
Authorisation: project access checks consider user status, active membership, project and customer-account status, enabled modules and assigned capabilities. Dedicated support functions require an active account designated as a support operator. Permissions and sharing choices must be configured appropriately by authorised administrators.
External work-order access: invitation tokens are stored as hashes, linked to a work order and subject to validity checks. External actions are restricted by their authorised scope, and the protected workflow checks that the entered email address matches the designated recipient. This address check is not a separate proof of control of the recipient’s mailbox. Customers choose recipients and should treat invitation URLs and downloaded files as confidential.
Files and devices: the storage integration supports time-limited signed download links. Mobile credentials use the operating system’s credential service; an optional device biometric app lock is separate from server authentication. Offline project databases and media are separate stores. This annex does not claim application-level encryption of every local file or remote erasure of downloaded copies.
Operational history: relevant work-order and collaboration actions create application history records. Those records are not represented as immutable security logs or a certified audit trail. One-time verification-code functions include expiry and attempt checks; their presence is not a claim that multi-factor authentication is enforced for every login.
Annex 3 Supplier schedule
OVH SAS, 2 rue Kellermann, 59100 Roubaix, France. Service: MX Plan. Purpose: production email delivery, including service messages and authentication emails. Data: recipient addresses, message contents and delivery metadata needed for those communications. OVH’s data-processing annex and service-specific terms are available at www.ovhcloud.com/fr/terms-and-conditions/contracts/.
Amazon Web Services EMEA SARL, succursale française, 31 Place des Corolles, Tour Carpe Diem, 92400 Courbevoie, France. Service: Amazon SNS, using AWS End User Messaging for SMS delivery. Purpose: authentication messages. Data: recipient phone numbers, message contents and delivery metadata. Delivery involves telecommunications providers and the recipient’s mobile network.
The public website uses Amazon S3 and CloudFront. OVH is the registrar for goso.cloud, and Amazon Route 53 provides DNS. These website and domain services do not by themselves authorise processing of Customer project records.
The AWS Service Terms incorporate the AWS Data Processing Addendum and its applicable transfer provisions, including Standard Contractual Clauses where required. References: aws.amazon.com/service-terms/ and aws.amazon.com/compliance/gdpr-center/.
Map-tile services, app stores and Customer-appointed services must be assessed according to their actual role. Direct browser requests to OpenStreetMap are described in the Privacy Policy and are not automatically classified as hosting subprocessors.
The Provider supplies the Customer with the applicable processing and support locations, relevant downstream providers and transfer safeguards before using a supplier to process Customer Personal Data. Any hosting provider for the contracted application is included in that customer-specific schedule. Supplier changes follow Section 4.
Annex 4 Exit and deletion schedule
An authorised Customer representative requests return or deletion at contact@goso.cloud. The parties agree a secure return plan covering exportable records, attachments, relationships, relevant history and metadata, available formats and any justified exclusions. The Provider must make the agreed package available and provide any assistance required by the applicable agreement and mandatory law.
Unless a lawful customer-specific arrangement provides otherwise, the standard schedule is: at least 30 calendar days for retrieval after the agreed transition period; deletion of active Customer Personal Data without undue delay and no later than 30 days after that retrieval period; and expiry of residual backup copies no later than 90 days after active-data deletion. Backup copies are retained for no more than 90 days from creation, remain protected and are not used for routine processing. If a backup is restored, applicable deletion instructions must be reapplied.
Temporary report and export files are subject to a 7-day retention period from creation. An exit package is retained throughout the applicable retrieval period, even if that exceeds 7 days. A customer’s explicit deletion instruction applies subject to mandatory retrieval and preservation requirements.
The plan preserves all applicable Data Act switching and retrieval rights. Mandatory shorter deletion deadlines and lawful preservation duties take priority; any retained data is restricted to the required purpose. The Customer manages the protection and deletion of copies it controls, including offline devices and exports. The Provider confirms completed return and deletion on request.