This policy covers goso.cloud, app.goso.cloud, the GOSO mobile applications and marketing subdomains displaying this policy. It explains who is responsible for personal information, why it is used and how individuals can exercise their rights.
Who is responsible
GOSO is operated by Alexandre Geiss, entrepreneur individuel (EI), using the business name App Engineering Design, at 7 Rue du Ruisseau, 57645 Noisseville, France. SIREN: 840 392 013. SIRET: 840 392 013 00024.
For privacy matters, contact Alexandre Geiss at contact@goso.cloud or write to the address above. The alternative business contact is contact@appengineering.design.
We act as controller for enquiries, quotations, billing, business correspondence and the administration and protection of our own business. When we host and process project information on an organisation’s instructions, that organisation is normally the controller and we act as its processor under the Data Processing Agreement. Where the customer itself acts for another controller, our role is that of subprocessor.
Account administration, support and security information are assessed according to their purpose: activities performed on the customer’s behalf remain within the DPA. This policy does not replace the customer’s own privacy information for employees, contractors or other people mentioned in its projects.
Information and sources
We receive the professional contact details and information you provide when requesting a demonstration, exchanging emails, obtaining a quotation or contacting support. These may include your name, organisation, position, email address, telephone number and the content of your request. The website’s contact form prepares an email in your own email application; sending that email transmits its contents to us.
The service processes account identifiers, professional contact details, project memberships and permissions. Customer content may include observations, work orders, comments, assignments, activity histories, custom form values, documents, quotations, photographs, video or audio, and references to assets, buildings or locations. A customer, colleague or authorised project participant may provide information about you when creating a project, inviting you or assigning work.
Requests to online services also involve connection information such as IP addresses, request dates, browser information and access or delivery records where the relevant services produce them. We limit support information to what is needed for the request. Do not send passwords or unnecessary sensitive information to support.
GOSO is intended for professional use, not services directed at children. Customers must avoid uploading special-category or criminal-offence data unless a specific written arrangement and suitable safeguards have been agreed.
Purposes and legal bases
We use enquiry and quotation information to respond and prepare a contract. Where you personally are the prospective contracting party, the basis is taking steps at your request before a contract. Where you act for an organisation, our legitimate interest is communicating with its representatives and managing a professional relationship.
We use contractual and billing information to perform contracts with individual professionals, administer relationships with organisational customers and meet accounting and tax obligations. The corresponding bases are performance of a contract, legitimate interests in business administration, and compliance with legal obligations, as applicable.
We use necessary support and security information to resolve problems, maintain access and protect the service. For processing for our own purposes, the basis is our legitimate interest in running a reliable service, balanced against individuals’ rights. Customer project processing follows the customer’s instructions and legal basis under the DPA.
Any promotional communication must have the legal basis required for its audience and offer a simple way to object. Where consent is required, it may be withdrawn at any time without affecting earlier lawful processing. We do not treat acceptance of service terms as consent to optional marketing. These documents do not authorise sale of customer personal data, advertising use of customer project content or training general-purpose AI models on that content.
Recipients and hosting
Information is available to authorised persons who need it for their tasks, project participants according to their permissions, and external recipients selected by the customer. A customer’s administrators manage its users and sharing choices. An exported file or information sent to an external recipient may subsequently be handled under that recipient’s own responsibilities.
Technical providers process information as needed to deliver the service. OVH SAS, 2 rue Kellermann, 59100 Roubaix, France, provides production email delivery through MX Plan and is the registrar for goso.cloud. Amazon Web Services provides public website hosting, DNS through Amazon Route 53 and SMS delivery through Amazon SNS. Professional advisers and public authorities may receive information where necessary for their functions or a legal obligation. Providers acting on our behalf are subject to applicable data-processing terms.
The public website is hosted by Amazon Web Services EMEA SARL, succursale française, 31 Place des Corolles, Tour Carpe Diem, 92400 Courbevoie, France, using Amazon S3 and CloudFront. SMS delivery involves telecommunications networks. Any transfer outside the European Economic Area requires an applicable legal mechanism and any necessary supplementary safeguards. The supplier schedule in Annex 3 of the DPA describes the relevant services and contractual references.
Maps and third party services
Some website and application maps request map tiles directly from OpenStreetMap servers. Displaying those maps sends the visitor’s IP address and normal browser request information to that service, together with the requested map area. This is separate from sending GOSO project records to another project participant. OpenStreetMap’s privacy policy explains its handling of these requests: osmfoundation.org/wiki/Privacy_Policy.
App stores, the email application used to contact us, and services independently selected by a customer operate under their own terms and privacy information. Their presence does not automatically make them GOSO subprocessors.
Cookies and storage on your device
On the marketing website, the optional Google Analytics 4 service counts visits to our public pages in English and French. With your consent, Google receives the public page path and language, a pseudonymous cookie identifier and technical data such as browser and connection information. We exclude forms, contact details, referrer URLs, URL parameters and fragments. Advertising and personalization are disabled.
Klaro runs on our website. Before you accept, the Google tag stays blocked. Accepting or refusing stores your choice for 180 days in a cookie restricted to the current hostname. Closing the notice leaves the choice open. A material change to the notice or a change of hostname prompts a fresh choice. Use Cookie settings in the footer to change your choice. Withdrawing stops measurement and clears this site’s analytics cookies. It applies to future collection.
The analytics cookies use the gosomkt prefix and are configured for up to 180 days. Google Analytics is configured to retain event-level data for 2 months and user-level data for 14 months, with the user period restarting on new activity. Aggregate reports have separate retention rules. Google’s information about its use of data from partner sites is available at policies.google.com/technologies/partner-sites.
The authenticated GOSO application uses a single cookie, goso-refresh, to maintain and renew authentication. This application uses no advertising or audience-measurement cookies. The web application also uses local storage for sign-in and the workspace and display choices you request. Local storage is distinct from cookies and has no automatic browser expiry: entries can remain until replaced, removed by the application or cleared in your browser. The validity of a stored access token is limited separately by the server.
Sign-in storage includes goso_access_token, goso_login_flow and goso_oauth_states, with related OAuth state and PKCE entries where used. These hold authentication credentials or the state needed to complete sign-in. The application removes selected authentication entries during sign-in completion or logout; this does not erase every saved preference or every copy of login-flow state.
Workspace storage includes goso_current_project, goso-observation-filters, goso-observation-browse-v1, goso-observation-table-v1 and goso.workOrders.view. These remember the selected project, filters, sort order, chosen view, table layout and browsing position. Some keys contain a user or project identifier. Display preferences are stored under goso_text_size, goso_theme_mode and lang. These entries are kept until changed or cleared; they are not an advertising profile.
The goso-refresh cookie lasts until its configured expiry or removal on sign-out; renewing the session can reset its expiry. Its current expiry is visible in your browser’s cookie settings. You can remove cookies and other site data through your browser. Clearing authentication data can require you to sign in again; clearing preferences resets your saved choices.
The mobile application stores credentials using the operating system’s credential service and stores project data and media locally for offline use. Where enabled, the biometric app lock uses the device’s authentication mechanism; GOSO receives an authentication result, not the biometric template. Signing out must not be understood as a guarantee that all offline project files or exported copies have been erased.
The application storage described above is used for authentication and requested interface functions. Any additional non-essential tracking that requires consent must remain inactive until you have made the required choice.
Retention
Enquiry and prospect details are kept for up to three years from collection or the last active contact from the person concerned, unless a shorter period is appropriate. Necessary contractual correspondence is archived for five years after the relationship ends, subject to a different legally applicable period or an actual dispute. Invoices and accounting evidence are kept for ten years under applicable accounting requirements.
Our standard retention policy provides for deletion or anonymisation of support records 12 months after a request is closed, routine security and access logs 6 months after the event, and temporary report or export files 7 days after creation. Necessary evidence of a contract, dispute or security incident may be kept separately, with restricted access, for the justified period. A documented legal obligation may require longer retention.
Account and project information processed for a customer follows the service duration, the customer’s lawful instructions and the DPA exit schedule. Unused user access is reviewed after 12 months of inactivity and disabled when no longer needed. Inactivity alone does not trigger deletion of customer project records. Browser preferences remain until changed or cleared, as described above.
The standard exit schedule provides at least 30 calendar days to retrieve data after the agreed transition, deletion of active data without undue delay and no later than 30 days after the retrieval period, and expiry of residual backup copies no later than 90 days after active-data deletion. Backup copies are subject to a maximum retention of 90 days from creation. Mandatory shorter deadlines, lawful preservation duties and expressly agreed customer arrangements take priority. Exit packages remain available throughout the applicable retrieval period; the 7-day temporary-export rule does not shorten that right.
Your rights
Depending on the applicable conditions, you may request access, correction, erasure, restriction or portability of your personal information, and object to processing based on legitimate interests, including direct marketing. Where processing relies on consent, you may withdraw it. We do not make decisions producing legal or similarly significant effects about individuals solely by automated processing under this policy.
Write to contact@goso.cloud with enough information to identify your request. We may seek proportionate verification if there is reasonable doubt about identity. We respond within one month, subject to a permitted extension of up to two further months for complexity or number of requests; if an extension is needed, we explain it within the first month.
For customer-controlled project data, contact the organisation responsible for the project. If you contact us, we forward or coordinate the request with that organisation and assist under the DPA. You can complain to the CNIL at www.cnil.fr/fr/plaintes or to another competent supervisory authority.
Required information and updates
Information necessary to answer an enquiry, create an authorised account or perform the contract must be supplied for that purpose; optional information can be omitted. The relevant request or agreement identifies what is needed. We will explain any materially new purpose before using information for it and meet the applicable legal requirements.
The version and review date appear at the top of this policy. Material changes will be communicated appropriately. Updating this website does not retrospectively change a customer’s agreed DPA or remove statutory rights.