Skip to content

Security and privacy

How you sign in, who can see what, where your data is kept, and what Wikidoc does with it.

This page describes how Wikidoc protects your organisation’s information today. If your organisation needs a security questionnaire filled in, contact support.

  • You sign in with your email address and a password, or with your Google account. New accounts verify their email address first.
  • Wikidoc doesn’t offer single sign-on (SAML) or its own two-step verification yet. If you sign in with Google, your Google account’s two-step verification protects your Wikidoc sign-in too.
  • If you forget your password, a reset link goes to your email address. See Reset or change your password.
  • Your organisation is kept apart from every other. Members only see content from their own organisation.
  • Membership is controlled by your Admins. Someone from your email domain joins automatically. Anyone else needs an invitation or an approved request, and an Admin can remove anyone. Removing someone ends their access at once. See How organisations, members and seats work.
  • Roles limit what people can do. Viewers read, Editors create, only Managers and Admins see analytics, and only Admins manage members and billing. See Roles and permissions.
  • Some things are narrower still. Team workspaces are open to their team only. Performance reviews are seen by the person, their reviewer, the people above them and Admins. A personal task board is open to its owner alone: Admins can’t open it either.
  • Portal guests see only what’s in the portal you invited them to, and nothing else of your organisation’s. See Members vs. portal guests.
  • Wikidoc runs on Google Cloud. Your documents, videos, training records and settings are stored in Google Cloud’s storage services.
  • Data is encrypted when it’s stored, using Google Cloud’s standard encryption, and sent over encrypted connections (HTTPS).
  • Card payments are handled by our payment provider, Airwallex. You enter your card details on their payment form, and Wikidoc never sees or stores your full card number.

Wikidoc uses Google’s Gemini AI models to do the work you ask of it: reading the files and recordings you add, writing documents, narration, slides and quizzes, drawing pictures for Scenario videos, translating, and drawing process maps. The content involved, such as your files, recordings, their transcripts and the document text, is sent to Google to be processed.

  • Google processes it under its paid-service terms: it doesn’t use your content or the results to improve its products, and keeps them only for a limited time to detect and prevent misuse.
  • Narration audio is made with Google Cloud’s text-to-speech.
  • Wikidoc removes passwords, API keys and access tokens from the text it writes, but it can’t remove everything personal. Screenshots show exactly what was on screen.
  • The original file is kept with the document, so you can see where each point came from. It stays until you remove the source or delete the document, and it counts towards your storage.
  • Sources are visible to the document’s owner. People the document is shared with see its outputs, not the original files.
  • Recordings often contain other people. A meeting, a toolbox talk or a screen recording can include colleagues’ voices, faces, names and customer details. Only add recordings you’re allowed to use for training, tell the people in them where that’s expected, and remove or blur what shouldn’t be shared before you publish the outputs.

Wikidoc isn’t certified to SOC 2 or ISO 27001. We’ll update this page if that changes.

If you think you’ve found a security issue in Wikidoc, email support@wikidoc.ai with the details. Please don’t share it publicly until we’ve had a chance to fix it.