Privacy policy

10 November 2026

This policy covers the HUWiki OAuth web application linked from this website and this public information website. School-managed Enterprise installations and other deployments may have different administrators and settings.

The public OAuth app is intended for people aged 13 and over, including adults, who meet Google’s account requirements. It is not intended for children under 13. External AI services may have higher age requirements.

Who operates HUWiki?

HUWiki is an independent, non-commercial project by Måns Mårtensson. For privacy questions, access requests or help with deletion, contact humamamm@gmail.com. Do not send passwords, API keys or confidential wiki content by email. A wiki owner or organisation determines the content and sharing of its own wikis; contact that owner about content they manage.

What information is used, and why?

• Account information: your Google account name, email address and profile picture identify you in the dashboard and support ownership and sharing.
• Wiki content: tiddlers, files, images, indexes, revisions and sharing information are used to open, edit, synchronise, search and share your wikis. Saved AI conversations are also wiki content.
• Calendar information: calendar lists and event information are read for calendar features. Calendar content copied into a wiki follows that wiki's sharing permissions.
• Forms and responses: Google Forms, questions, submitted responses and linked response spreadsheets are used for surveys and Shop order forms when you choose those features. Responses may contain information supplied by participants.
• Invitations: recipient email addresses and wiki links are used to send sharing invitations you request.
• Settings and technical information: application preferences, connection settings, cached navigation data and diagnostic events support operation, performance and troubleshooting.

Google permissions

HUWikiOAuthLab uses two Google Apps Script clients. The standard client requests drive.file, script.external_request, script.send_mail, calendar.readonly and forms. The separate Full Drive client requests drive, script.external_request, script.send_mail and calendar.readonly. Google's consent screen shows the permissions of the specific client you authorise. The standard client does not silently gain Full Drive access.

• drive — full Drive access: permits viewing, creating, editing and deleting all Google Drive files your account can access, subject to your permissions on those files. This is a broad account permission, not a permission limited to a selected wiki folder. HUWiki uses it to manage wiki folders, separate tiddler files, images, documents and indexes, including shared wiki files created by collaborators.
• drive.file — existing limited-access version: permits creating, reading, editing and deleting specific Drive files created by or opened with HUWiki. It does not grant access to every file in your Drive. This is the alternative used by the existing limited-access deployment.
• forms — Google Forms: allows creating and editing forms, managing their settings and reading responses within your Google account's permissions. HUWiki uses it for user-requested surveys and Shop order forms, including linking response spreadsheets.
• script.external_request: connect to Google APIs, retrieve application resources and contact the external services used by enabled features, including an AI provider you select.
• script.send_mail: send email, including wiki invitations, as part of requested features. HUWiki does not obtain inbox-reading access through this permission.
• calendar.readonly: read calendars and events you can access for calendar features. This permission does not allow changes to Google Calendar events.

Where information is stored and who receives it

Wiki content and supporting files are stored in Google Drive, including spreadsheets used as indexes. The app runs on Google Apps Script under the accessing user's authorisation. Google processes account, hosting and storage information under its own terms and privacy policy.

Application settings and personal cloud AI connections are stored in Apps Script user properties. Some Site and Community publication metadata is held in Apps Script script properties. Temporary server caches and browser storage are also used. These are not an end-to-end encrypted vault. Access is controlled through Google accounts, application permissions and the configuration of the service.

Sharing makes content available to the recipients and roles you choose. Publishing a site or reusable package can make a separate copy accessible to its intended audience, including the public. People who already received an export or copy may retain it. The app's administrator can manage application code and technical logs; support access to particular private content should be agreed with you before you share it.

How HUWiki protects sensitive information

HUWiki is based on the open-source TiddlyWiki engine and runs on Google's Apps Script infrastructure. It does not operate an independent developer-hosted server or database containing users' Drive files. Its web apps execute as USER_ACCESSING: Google authorises operations under the identity and permissions of the person using HUWiki.

• Access control: Google OAuth controls the permissions granted to each client. Google Drive's file and folder permissions govern cross-account sharing, including personal and Workspace accounts. HUWiki also checks wiki-specific access for supported operations. Full Drive is a broad permission used for finding shared wikies and new files added by collaborators; it does not override Google's sharing rules.
• Transport protection: The Google-hosted web app uses HTTPS. The reviewed server requests to Google APIs and supported cloud AI providers also use HTTPS. The security of connections to user-configured local AI servers depends on that local configuration.
• Separated storage: Wiki files remain in Google Drive. Personal cloud AI keys are stored in the user's Apps Script user properties, not in shared tiddlers, and the server-side AI handler does not return stored API keys to the browser. Browser storage and caches may contain wiki metadata and recovery data; this is not end-to-end encryption.
• Control and deletion: Users can manage Drive permissions, remove content and publications they control, delete AI connections and revoke HUWiki's Google access. Previously exported copies and data held by other providers must be managed separately, as described below.

Google operates and protects its underlying services; HUWiki remains responsible for how its application code handles the access granted by users.

Network requests and external resources

Core Workspace functionality contacts Google endpoints: www.googleapis.com for Drive, docs.googleapis.com for Docs, sheets.googleapis.com for Sheets, and drive.google.com for published or link-shared files. In the reviewed Drive REST calls, Google OAuth tokens are sent to Google API endpoints, not to AI providers or public software download hosts.

Some features download publicly available TiddlyWiki software, plugins or optional music resources from tiddlywiki.com, tiddlytools.com, cdn.jsdelivr.net, raw.githubusercontent.com and codeload.github.com. The reviewed public-resource requests do not include the user's private wiki content or Google OAuth credentials. Optional maps may load OpenStreetMap or Google Maps assets in the user's browser; those providers may receive connection details such as an IP address. Optional AI requests are described next.

Optional AI connections

If you choose an AI feature, HUWiki sends your request to OpenAI, Anthropic Claude or a local server such as Ollama or LM Studio, according to your choice. Depending on the feature, you explicitly select conversation messages, tiddlers or wiki context, instructions and images. Selected content may originally have been stored in Google Drive. The AI request handler does not independently browse Google Drive or forward your Google OAuth token to the AI provider. Cloud requests instead use your provider-specific API key and pass through Apps Script; local model requests go from your browser to the server you configure.

Cloud API keys are stored in your app-specific user properties until you delete the connection. Local connection settings are stored in the browser. Saved conversations and generated results can be seen by people with access to the wiki. Deleting a conversation in HUWiki does not delete a provider's records. The provider's retention, processing and account settings apply separately; do not assume a request has zero retention. Review the selected service's data controls before sending information. Use of an external AI service is optional.

Personal AI access

HUWiki is a public wiki application for Google-account users, not restricted to one school or Workspace domain. AI is optional. Sharing a wiki does not share the owner’s private connection or API key. Cloud AI requires your own provider account and API key and compliance with that provider’s age and any parental-consent requirements. HUWiki asks you to confirm these conditions before sending a request; this declaration is not independent age verification. Each request identifies the recipient and data involved and can be cancelled. The Gemini API is not enabled in this OAuth edition. You can instead open Google’s separate Gemini app as described below. Public availability of AI for minors requires additional safeguards; a personal API key alone does not establish eligibility.

Open Gemini and copy text

“Open Gemini” opens gemini.google.com in a new tab without sending your message, conversation history, images or API keys. “Copy text” copies only the text in the AI chat’s current message field to your device clipboard after your click. You decide whether to paste and send it in Gemini; the response is not automatically retrieved by HUWiki. Your device manages the clipboard, which may be subject to its synchronisation settings.

Gemini is a separate Google service with its own account and age requirements, privacy information, activity settings, retention and content-use rules. HUWiki cannot control these settings or delete a Gemini conversation. Read the Gemini privacy information before pasting content. Share only information you are entitled to share and avoid confidential information about other people. Access to a wiki does not itself grant access to Gemini.

Retention and deletion

• Wiki files: kept until you or the responsible owner delete them. Deleting a wiki moves its data to Drive Trash, marks its registry entry deleted and revokes its app access records. This is not immediate permanent deletion of every record. Check any cleanup warning. Google's Trash handling and your organisation's retention rules may also apply.
• Published and exported copies: manage publications separately. Some independently published Studio or Community releases survive deletion of the source wiki. Copies held by other recipients cannot be removed by deleting your original.
• Dashboard browser cache: includes wiki titles, links, roles and profile information. It is separated by app and account. A saved cache older than 30 days is removed when the dashboard next tries to restore it. A fresh list replaces it; there is no background deletion while the browser is closed. You can also clear site data in your browser.
• Settings and AI connections: user properties have no universal automatic expiry. Delete unwanted connections in HUWiki and clear local browser settings when appropriate. Ask for help if a setting has no removal control. Revoking Google access does not itself delete stored wiki files, settings or provider records.
• Technical logs: the current Cloud project's ordinary log bucket retains entries for 30 days; Google's required audit-log bucket retains entries for 400 days. Automatic exception logging is enabled. Selected application error paths use fixed codes rather than raw API responses; errors and platform metadata can still appear in technical logs. Temporary application caches expire separately.

Google data and permitted use

HUWiki's use and transfer of information received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. HUWiki uses Google user data for the user-facing features you choose. HUWiki does not sell that data, use it for advertising or use it to develop, improve or train general-purpose or non-personalised AI/ML models. Only when you explicitly submit selected wiki content to an optional AI provider can that content, including material previously stored in Drive, be transferred for the requested feature; the provider's separate terms also apply. Other transfers are limited to disclosed functions with your consent, necessary security work or legal obligations. Human access is limited to your agreement to specific content or exceptions permitted by Google's policy.

This website and your choices

This information website is hosted on GitHub Pages. Its own code has no advertising, analytics or collection forms; language selection uses links. GitHub may process technical visitor information for hosting: see GitHub's privacy statement. HUWiki's application uses browser storage for functionality. Google and optional providers may process information internationally; HUWiki does not promise EU-only storage for all services.

You can manage wiki sharing, delete content you control, export your wiki and revoke HUWiki's access through your Google account connections. Revocation stops future authorised access but does not erase existing data. Contact us about access, correction or deletion of information we administer; for a wiki managed by someone else, also contact its owner.

Changes

Changes will be dated on this page. New uses of Google user data require updated disclosures and consent before that new use. This policy does not mean Google has verified or approved HUWiki.