Privacy Policy

1. Who is responsible for your data

2. What we collect and why

3. Who can see what

• •

  Other members in your workspace see your profile, your public contributions and what you post.
• •

  Project leads and members see your activity in their project.
• •

  People you send a share link to can view your profile without signing in. A named link expires (7, 30, 90 or 365 days; 90 by default) and can include contributions you have marked private. You can revoke links at any time.
• •

  Recruiters and partners in your workspace can search members and view their profiles, including credibility (shown to them as "Reliability"). Contact through Provenance is mediated.
• •

  Workspace administrators see usage analytics for their workspace, including a per-member activity timeline (last 90 days) and pattern flags such as "at risk of leaving".
• •

  We do not sell your data, and we do not use it for advertising.

4. Service providers and where your data goes

5. Automated processing and profiling

• •

  Credibility is calculated automatically from verified contributions and the network of people who verified them. It affects how you appear to recruiters.
• •

  Proficiency tests are partly graded automatically, including by an AI model, and integrity signals can flag a result. A person reviews every flagged result; you can see a flag on your own record, and it can be overturned.
• •

  Usage patterns (for example inactivity) are flagged for administrators, and the wording of reminders is chosen automatically based on what members respond to.

6. Calls, messages and security

• •

  Calls are encrypted in transit using the standard WebRTC protection (DTLS-SRTP). One-to-one calls go directly between devices where the network allows; otherwise they pass through Cloudflare's relay, which forwards them without decrypting them. Group calls pass through a Cloudflare media server that decrypts and re-encrypts the audio and video in order to route it. Calls are therefore not end-to-end encrypted. We do not record calls.
• •

  Messages are encrypted in transit and stored on our servers so that they appear on all your devices; they are not end-to-end encrypted. There are no read receipts.
• •

  Files are stored privately and served through short-lived signed links.
• •

  We protect your data with access controls, per-workspace data isolation, hashed passwords and encryption in transit.
• •

  If a breach is likely to put you at risk, we will tell the NDPC within 72 hours of becoming aware of it, and tell you promptly if the risk to you is high.

7. How long we keep data

8. Your rights

• •

  find out whether we hold your data, and get a copy of it;
• •

  have it corrected, or deleted;
• •

  restrict how we use it while a request or objection is being dealt with;
• •

  object to processing based on legitimate interest, including profiling;
• •

  withdraw consent at any time (for example Firebase Analytics, under Privacy settings);
• •

  receive your data in a structured, machine-readable format and have it sent to another service;
• •

  not be subject to decisions based solely on automated processing that significantly affect you, and ask for a person to review one.

9. Cookies and device storage

• •

  The web app stores your sign-in session in your browser's local storage. This is necessary to keep you signed in.
• •

  Google Firebase Analytics (web and phone) is off until you choose "Allow". On the web its script is not even downloaded until then. Advertising identifiers and ad-personalisation signals are always off.
• •

  Firebase Cloud Messaging and Remote Config use an app-instance identifier to deliver notifications and app settings.
• •

  The desktop app checks for updates.

10. Changes

11. Contact