Privacy policy

This policy describes the data AVANELDO processes, including data received from Google when an administrator connects Google (section 5). It is published in French first; the French version prevails.

1. Who we are

AVANELDO is a customer relationship management (CRM) software service for freelancers, agencies and small service teams, published by Henan ZHANG, sole proprietor (SIREN 935 311 423 (National Business Register, RNE)) (“we”). Point of contact for any question about personal data: contact@avaneldo.com.

2. Two distinct roles

  • Controller: for users’ account data (identity, sign-in, security).
  • Processor (GDPR Article 28): for the data our clients record in their workspace about their own clients, contacts and prospects. The client (the company that holds the workspace) is the controller for that processing, its legal basis and informing the people concerned. We process this data only on its instructions.

If your data appears in one of our clients’ workspaces (for example as a contact or prospect), please send your request to that client first. We will assist them in responding.

3. Data processed as controller

DataPurposeLegal basis
Email address, name, password (stored only in hashed form), role and workspaceCreate and manage your account, authenticate you, apply access rightsPerformance of the contract (GDPR Art. 6.1.b)
Sign-in session (session identifier, creation, expiry and revocation dates)Keep and secure your sign-inPerformance of the contract; legitimate interest in securing the service (Art. 6.1.f)
Technical logs (request identifier, route, status, duration, internal user and workspace identifiers), without request content, passwords, cookies or email addressesSecurity, diagnostics, abuse preventionLegitimate interest (Art. 6.1.f)
IP address (in memory only, to limit sign-in attempts, with no durable storage)Preventing brute-force attacksLegitimate interest (Art. 6.1.f)
If an administrator connects Google: a stable Google account identifier and an encrypted access token (see section 5)Run the Google integration that was requestedPerformance of the contract

No payment is currently accepted by the service.

4. Data processed on behalf of our clients (processing)

Depending on how the client uses the service: client companies (name, email, telephone, website, industry, notes), contacts (name, email, telephone, position, notes), sales opportunities, services, tasks, activities and notes, internal notifications, external links and team members. When a client imports contacts or clients from a Google Sheets spreadsheet, it is responsible for having the rights to that data and for informing the people concerned where the law requires it (GDPR Art. 14). Records created by an import become data of the client’s workspace.

We do not analyse the content of our clients’ data for our own purposes, we do not sell it and we do not use it for advertising. Other third-party connectors may be offered later; this policy will be updated before they are enabled.

5. Google user data

This section applies only if a workspace administrator chooses to connect a Google account. The connection is optional and is never enabled by default.

Permissions requested and why

  • openid: obtain a stable identifier of the Google account (the “sub” claim), so that the connection can be tied to one workspace and so that two workspaces cannot revoke each other’s shared authorization. We do not request the name, the email address or the profile.
  • https://www.googleapis.com/auth/drive.file: access only the files the user explicitly selects with the Google file picker. We have no access to the other files in your Google Drive.

What we do with this data

  • Google Drive and Google Docs: attach a selected file to a client, opportunity or service record as a link (label, address, category, provider).
  • Google Sheets: read the cells of the selected spreadsheet and tab, show a preview to the user and, only after the user confirms, create the corresponding clients or contacts in the workspace.
  • Access to Google Sheets is read-only. AVANELDO never creates, modifies, deletes or shares any of the user’s Google files.

What we keep

  • the stable Google account identifier (“sub”), which stays attached to the workspace’s connection record, including after a disconnect, until the workspace is deleted;
  • the refresh token, stored encrypted (AES-256-GCM) and deleted on disconnect;
  • the clients, contacts and links created at the user’s request (they become workspace data);
  • a technical record of each import (operation identifier, number of rows read, imported and skipped), with no copy of the spreadsheet content; it is deleted on disconnect.

We do not keep a separate copy of the content of your spreadsheets or of your Google files. The content that is read is shown to the user for review and then used only to create the records the user confirms.

Sharing, use and Limited Use

  • We do not sell Google user data and do not share it with any third party, other than our hosting provider (section 6), which processes it on our behalf.
  • We do not use it for advertising, and we do not use it to develop, improve or train generalized artificial intelligence or machine-learning models.
  • No human reads this data, except with the user’s explicit consent, for security purposes (for example investigating abuse), to comply with the law, or when it is aggregated and anonymized.
  • AVANELDO’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting and deletion

An administrator can click “Disconnect” in the workspace settings at any time: the stored token and the technical import records are then deleted and, when no other connection depends on the same Google authorization, the authorization is also revoked at Google (the Google account identifier “sub” stays attached to the connection record, marked “disconnected”). You can also remove AVANELDO’s access from your Google account (myaccount.google.com/permissions). Clients and contacts that have already been imported stay in the workspace until the client deletes them.

6. Recipients and sub-processors

ProviderRoleData location
Render Services, Inc.Hosting of the API, the PostgreSQL database, the logs and the static sitesFrankfurt region (EU) for the API, the database and application logs; Render’s global CDN for the static sites (public files only)
GoogleThird-party provider connected by the administrator (section 5)As determined by Google
Email provider of the contact addressReceiving the messages sent to the contact addressAs determined by the provider

Workspace members access data according to their role (Admin, Manager, Viewer).

7. Transfers outside the European Union

Render Services, Inc. and Google are companies established in the United States. Transfers to Render are covered by Render’s data processing agreement, which relies on the EU-U.S. Data Privacy Framework and, in the alternative, the European Commission’s standard contractual clauses. Processing carried out by Google is subject to Google’s terms.

8. Retention periods

DataPeriod
User accountAs long as the account exists. No automatic deletion is in place: deletion is carried out manually on request at contact@avaneldo.com; we reply to requests to exercise rights within one month.
Workspace data (processing)During the contract. At the end, the client chooses the return and/or deletion of its data. During the preview, these operations are carried out manually by us, on the written instruction of a workspace administrator.
Sign-in sessionThe session expires after one hour. Technical records of expired sessions and of expired verification or reset tokens (without content) are kept as long as the account exists; no automatic purge is in place today.
Google connectionThe token and the technical import records are deleted on disconnect. The Google account identifier (“sub”) stays attached to the connection record, marked “disconnected”, until the workspace is deleted.
Technical logsAbout 7 days (the log retention applied by our host, Render, for our current plan).
BackupsDeleted data may remain in the host’s backups for up to 7 days.

9. Security

Encrypted connections (HTTPS), hashed passwords, an authentication cookie that JavaScript cannot read (HttpOnly), encrypted integration tokens (AES-256-GCM), per-workspace data isolation, server-side access control, logs without sensitive content.

10. Your rights

You have the rights of access, rectification, erasure, restriction, portability and objection (GDPR Articles 15 to 21), and the right to set instructions about what happens to your data after your death. To exercise them: contact@avaneldo.com. We reply within one month. We may ask for information that lets us verify your identity. You may lodge a complaint with the CNIL (www.cnil.fr).

11. Cookies and trackers

Only strictly necessary trackers are used. See the Cookies and trackers notice.

12. Changes

The date and version number of this policy are updated each time it changes.