Back

Privacy policy

Data controller

CCR-Apps, sole proprietorship (Entreprise Individuelle)
Address: 17 Rue D'armaille, 75017 PARIS, France

Data protection officer

No data protection officer has been appointed, as this appointment is not mandatory for CCR-Apps. Any question about your personal data can be sent through the contact form.

Data processed

When you sign in, Microsoft Entra or Google sends your identifier, your email address and your display name; the application stores them to identify you. It then keeps the data you enter: organizations, members and roles, invitations (email address of the invited person), customers, plans, address blocks, tags, and the change log signed with your name. A cloud network scan (Azure, Google Cloud or AWS) stores the analyzed result (subscriptions, projects or accounts, virtual networks, subnets, resources); the IP addresses of resources and the names you gave them may be personal data.

The other data processed is as follows.

  • Profile: the interface language and the last version of the "What's new" window that you have read are stored on your account.
  • Account activity: date of the last sign-in and of the last activity, open sessions (with the sign-in provider) and identities linked to your account (provider, identifier and address of the linked account, no token).
  • Authors of changes: your identity is attached to plan versions, drift decisions, scans and the last changes to IP addresses and DHCP ranges. It becomes anonymous ("deleted user") when the account is deleted.
  • Presence and locks: on an open plan, your presence and the locks you place on blocks are stored to avoid simultaneous changes.
  • Free-text labels: the owner of a block, of an IP address or of a DHCP range is a text entered by the members of the organization. It may contain people's names; the customer organization is responsible for it.
  • Problem reports: the type (bug or incident), the title, the description and up to three attachments that you write or attach, with technical context (application version, page as a route pattern without identifier, browser, browser version and operating system, language, theme, date and time). The page is stored only in the database, with the report: it is not published in the GitHub issue. The report is linked to your account to limit how often you can send reports and so that the platform owner can find the author; this link is cut when the account is deleted. Limit the text and attachments to the data needed to deal with the problem.
  • Contact form: your name, your email address and your message are sent by email to the support address; nothing is stored in the application database.
  • Platform log: locking and unlocking of accounts and deletions of users or organizations made by the platform owner are logged, with the owner's identifier and the readable name of the target.
  • Activity measurement: one row per day and per active user, and an hourly counter of refused demonstration codes (no address, no code). This data feeds the platform charts.
  • Technical logs: the API and the application firewall log requests, including the caller's IP address. Invitation tokens and sign-in codes are masked before being written.
  • Emails: sending an invitation or a support message goes through an SMTP relay, which sees the recipient's address and the content of the message.

Purposes and legal basis

The data is used to authenticate users, to provide the network plan design and comparison service, to keep track of changes and to protect the application against abuse.

Legal bases: performance of the service you use for authentication and provision of the service; the legitimate interest of CCR-Apps in keeping track of changes and securing the application.

Cookies and local storage

The application sets a session cookie (ct_session), which is essential and cannot be read by the page's code, valid for eight hours of activity and shared by the sign-in site and the platform's tools (cloodtools.com and its subdomains) so that a single sign-in serves them all; it protects write operations with an anti-forgery token derived from the session. During a sign-in or an account linking, a technical cookie (ct_oidc, ct_oidc_google or ct_oidc_link) keeps the state of the flow for 10 minutes. In demonstration mode, a dedicated cookie lasts 24 hours. No audience measurement or advertising cookie is used.

The browser keeps, in its local storage (localStorage), on your device only:

  • your display preferences: language (also stored on your account), theme, collapsed menu, panel widths, overview mode, map reference mode and depth, open or collapsed plan tree, collapsed status bar;
  • the last plan opened;
  • in demonstration, the version of the news already seen;
  • the marker of the last change log entry you have seen, per organization;
  • the application notifications, per person and per organization: 30 days and 100 entries at most;
  • the layout of map diagrams, the choices of the AWS scan guide and, in offline demonstration, the demonstration data;
  • the data from before the multi-user version, offered for upload once (and the register of that upload), where applicable.

Session storage (sessionStorage) only remembers that a zoom hint has already been shown in the tab, and the link of a pending invitation for the duration of a sign-in. Notifications kept in the browser are erased at sign-out. You can clear this storage from your browser settings.

Access to cloud providers

The scan runs in your browser, under your Microsoft or Google identity. No token goes through the server and no client secret is kept: only the analyzed result is sent and stored.

Retention periods

No scheduled task purges the data: unless stated otherwise, deletion takes place at the next processing (recording or consultation), as soon as the data exceeds its period.

  • An organization's data (plans, blocks, customers, change log, owner labels, authors of changes): as long as the organization exists; the change log is kept with the plan it relates to.
  • Presence and locks on a plan: as long as the plan exists; a lock is released when its holder is no longer present.
  • Account (profile, linked identities, dates of sign-in and activity): as long as the account exists.
  • Scans: the 20 most recent of each customer, older ones are deleted.
  • Session: eight hours; demonstration cookie: 24 hours; technical sign-in cookies: 10 minutes.
  • Invitations: valid for 7 days. The address of an expired invitation stays stored until the organization is deleted or until a new invitation is sent to the same address.
  • Reports (database): deleted at the next processing as soon as they exceed 90 days. Attachments stored in Azure Blob: deleted by the application with the report, and by an Azure rule after 90 days. In the support email, the link to an attachment stored in Azure Blob is valid for 7 days; without Azure Blob, the link is the API one, reserved to the platform owner and valid as long as the report exists, that is until its deletion at 90 days.
  • GitHub issues created for reports: they contain no entered title, description or attachment and no data about the author; they stay on GitHub until the owner deletes them.
  • Platform log: deleted at the next processing as soon as it exceeds 365 days.
  • Activity measurement (one record per day and per active user) and counter of refused demonstration codes: deleted at the next processing as soon as they exceed 90 days.
  • Notifications in the browser: 30 days.
  • Technical logs (Azure Log Analytics): 30 days, the default period of the workspace.
  • Database backups: 7 days, without geo-replication.
  • Contact and support emails: kept in the publisher's mailbox for as long as needed to handle the request.

Recipients and processors

An organization's data is accessible to the members of that organization, according to their role.

Internal recipient: the platform owner, for the operation and support of the platform. The owner sees the list of accounts (name, email address, account type, dates of creation, last sign-in and activity, status, organizations, with a CSV export), the metadata of organizations (name, creation date, settings, number of members, plans, blocks and scans, last activity) and, in the detail of an organization, the name, email address and role of each member, the reports and the platform log. Contact messages do not go through the application: they are sent by email to the support address.

Processors:

  • Microsoft Azure: hosting of the application, the PostgreSQL database, attachment storage (Azure Blob), secrets and logs. France Central region (France), with no transfer outside the European Union planned for this data.
  • Microsoft Entra and Google: authentication. These providers may process data outside the European Union; transfer covered by the European Commission's standard contractual clauses provided for in the provider's terms.
  • Google (Google Cloud scan): when the Google sign-in of the scan is started, your browser loads Google's sign-in script (accounts.google.com), which sends your IP address to Google; transfer covered by the European Commission's standard contractual clauses provided for in the provider's terms.
  • GitHub (Microsoft group): creation of one issue per report. It contains only the report reference, its type and labels, the application version, the browser with its version and the system, the language, the theme, the date and a link to the platform owner's list of reports, never the entered title, the description, the attachments or a name, email address or identifier of a user or organization. Hosted in the United States: transfer outside the European Union covered by the European Commission's standard contractual clauses provided for in the provider's terms.
  • OVH (France): SMTP relay for invitation, contact and support emails.

The cloud provider scan (Azure, Google Cloud, AWS) runs in your browser: Microsoft, Google or AWS see your requests under your own identity, according to their terms, and are not processors of the application.

Your rights

You can access your data, correct it, export it, erase it, object to a processing or request its restriction. The "Settings" page (user menu entry) offers, in the "My data" card, "Export", which downloads your personal data in JSON format, and, at the bottom of the page, "Delete my account", which erases your identity: your memberships and sessions are deleted, an organization of which you are the only member is deleted with its data, and the log of other organizations shows "deleted user". For any other right, use the contact form.

Complaint

You can lodge a complaint with the supervisory authority of your country; in France, the CNIL (www.cnil.fr).