Privacy & Google data

Kojent Map · Updated 8 November 2026

Your maps stay in your browser unless you choose to save them to Google Sheets or export them. Google Sheets sharing permissions control access to a shared map.

Data the app uses

Kojent Map uses the topics, connections, notes, dates, tasks, comments and display names you enter to display and edit your maps. Your browser stores local maps, local edit history, view preferences, your local collaborator name, a snapshot of your last Google Sheets map and unsent changes to shared maps. These remain on that browser until removed or its site data is cleared.

Connecting Google Sheets

When you connect, Google requests permission for only the specific Drive files and folders you select or create with Kojent Map (the drive.file scope). The app does not request access to all your spreadsheets or all your Drive files. This permission allows the app to read and edit selected map spreadsheets and create new ones; the app does not offer a spreadsheet-deletion operation.

Google’s own file browser displays the available files. Kojent Map receives the selected file or folder’s ID, name and type; it does not download a listing of your whole Drive. A pasted or shared link identifies a spreadsheet but does not grant the app access. If needed, you select that spreadsheet in Google’s browser before it can be opened. The app reads that file and writes map changes to its “Kojent Map” worksheet.

For a selected save folder, the app checks whether you can add files and places only the newly created map spreadsheet there. Choosing a folder does not grant the app access to every existing file inside it. The folder’s existing sharing rules may apply to the new file.

Older versions requested access to all Google Sheets spreadsheets. New connections request only selected-file access and do not include that earlier permission in their new access tokens. To remove a historical grant from your Google Account, remove Kojent Map in Google Account connections, then reconnect and select the maps you want to use.

The app does not request Google profile or email OAuth scopes. When you open Share, it reads the selected file’s sharing capabilities and access list, including names and email addresses returned by Google. These access details are displayed in the current page and are not stored in the map. The app reads your account’s display name and email address from Google Drive using the same selected-file permission, so you can distinguish accounts when opening or saving maps. The email address is displayed in page memory and is not added to maps, local storage or usage statistics. For shared maps, the app uses your display name for your activity and new comments. Local maps can use a name you enter. Display names are labels, not access controls. Google access tokens used by the editor are held in page memory and are not saved in browser local storage. The public OAuth client ID identifies this app; it is not an access token.

Staying signed in

When persistent sign-in is enabled, Google sends a one-time authorization code to the app. A Kojent Map connection service on Google Firebase exchanges it for access and refresh credentials. The refresh credential lets the service renew your connection without another popup. Your selected-file permission remains unchanged.

The service stores encrypted Google credentials, your Google Drive account identifier and display name in a dedicated Firebase database in Europe. The encryption key and OAuth client secret are held in Google Secret Manager. Your browser receives a secure, HttpOnly session cookie and a short-lived access token. The cookie is necessary for automatic reconnection and is not used for advertising or analytics. In the editor, map contents travel directly between your browser and Google Sheets. If you enable an AI connection, the separate handling described below also applies.

Sessions expire after 90 days without use, or sooner if Google ends the grant. Using the app renews that period. Choose Sign out on this device in Collaboration or Save status to delete that browser session’s server credentials and cookie. This stops automatic reconnection on that browser and website address; other devices remain signed in. Clearing site data also removes the cookie, but the inaccessible server record remains until expiry. Expired records are denied immediately and removed asynchronously by Firebase.

Storage and sharing

When you submit the Share form, the email address and Viewer or Editor role you choose are sent directly to Google to grant access to that spreadsheet. If you select the invitation option, Google is asked to send that person an email containing the direct Kojent Map link. Copying a map link does not itself change permissions. The app checks whether your Google account can share the selected file.

Your browser connects directly to Google’s services to read and write shared maps. Shared worksheets contain an edit history with map content, session identifiers, timestamps, comments and collaborator activity. People with access to the spreadsheet can read the data and history it contains. People with edit access can change it. Sharing the website link alone does not grant access to a private spreadsheet.

The editor does not send map contents to a Kojent Map server. An optional AI connection does, as described below. The app does not use advertising trackers. Website hosting and Google services may process standard connection information under their own policies. Exported files and copies made by collaborators are controlled by the people who hold those copies.

Recent Maps remembers the IDs, names, layouts and save/sync times of Google Sheets maps you open or create in this browser. After sign-in, the app can restore older entries from its saved references to previously opened Sheets. This history stays in your browser and does not grant access to any file. A snapshot of the last Sheet’s map content is also kept here so it can reopen immediately. It is labelled as a saved snapshot until reconnection completes; Google rechecks file access before syncing or editing. The snapshot may remain on the device after Google access is revoked, like a previously downloaded copy.

Optional AI connections (MCP)

When you connect ChatGPT, Claude or another MCP client, you choose a Google account, an explicit list of Google Sheets maps and either read-only access or permission to prepare reviewed edits. Creating new maps requires a separate choice. Local maps are not exposed. Google file permissions and your connection’s map list are checked by the server.

For enabled maps, the Kojent Map service reads requested map content and returns it to the AI service you connected. This can include node text, notes, dates, assignees and relationships. Only connect maps you intend that AI service to process; its privacy and retention policies apply to the data it receives. AI-proposed edits are held as encrypted previews. You must open the review link and approve before a map is created or changed.

The private European Firebase database stores an encrypted copy of the selected Google account’s credentials for each AI connection, a hashed account reference, display name, enabled map IDs and titles, and the connection’s permissions. Google credentials are never sent to the AI client. The client receives separate, limited Kojent Map credentials; only their hashes are stored. These records are separate from anonymous usage counters.

Pending previews expire after 30 minutes. Applied or conflicted previews are retained for up to seven days to confirm results and handle retries. A connection expires within 90 days, or earlier when Google access ends. Expired records become unusable immediately and are removed asynchronously. Use AI connections to revoke access. Revocation stops future requests, but does not undo a save already in progress or erase map content already sent to an AI conversation. Signing out of the editor does not revoke an AI connection; manage these separately.

Anonymous usage totals

We collect daily totals for visits and use of features such as creating and importing maps, opening and creating Google Sheets maps, switching layouts, opening sharing, exporting files and encountering a sync interruption. These are activity counts, not unique-user counts. Repeat visits count again; blocked or interrupted requests can be missed.

Usage requests contain only fixed event names and integer counts. They omit cookies, account credentials and the page’s referrer. We do not collect visitor identifiers, map contents or titles, Sheet IDs or links, names or email addresses in these statistics. We do not use analytics cookies, browser fingerprinting or cross-site tracking. The collector stores only daily aggregate counters in the app’s private Firebase database, separate from sign-in records; it does not retain individual event histories or join counts to accounts.

Hosting and network services still receive standard connection information, which may include IP addresses and browser information in operational logs. This information is not used to identify visitors in the usage totals. Necessary sign-in data is handled separately as described above.

Retention and deletion

Local maps can be removed from Local Maps. Clearing this website’s browser data removes its stored local maps, recent-map history, the last Sheet snapshot, preferences and pending changes; export anything you want to keep first. Closing the page clears its in-memory Google token. With persistent sign-in enabled, the session cookie allows the app to restore access on your next visit. Signing out keeps your browser’s maps, snapshots and pending edits; clear site data separately if you also want to remove those local copies.

Deleting a topic or comment is an edit, not erasure of its earlier history. Shared map history remains in the spreadsheet until the file owner removes it using Google Drive or Sheets. To retain only the current map state, export and import the current map and save it to a new Sheet, then manage the old file and its sharing separately.

You can remove Kojent Map’s authorization in your Google Account connections. You can also change or revoke a collaborator’s access through the spreadsheet’s Share controls. Revoking access stops future authorized access; it does not erase copies or exports already held by another person.

Use of Google data

Google data is used to provide the map editing, storage and collaboration features you choose. It is not sold, used for advertising or used to train AI models by this app. Kojent Map’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Contact and updates

For questions about Kojent Map’s handling of data, contact tim.b.kroemer@googlemail.com. Changes to this notice will be published here with an updated date. New uses of Google data require updated disclosure and consent where required.