Privacy & Google data

Kojent Map · Updated 17 October 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 chosen collaborator name and unsent changes to shared maps. These remain on that browser until removed or its site data is cleared.

Connecting Google Sheets

When you choose to connect, Google asks for permission to see, edit, create and delete your Google Sheets spreadsheets. This permission supports creating map files and opening shared map files by their spreadsheet link. The app reads the spreadsheet you open and writes map changes to its “Kojent Map” worksheet. It does not browse your other spreadsheets, and it does not offer a spreadsheet-deletion operation.

The app does not request your Google profile or email address. Collaborator display names are entered by users and are not verified Google identities. Google access tokens are held in the current page’s memory, not saved in browser storage or sent to a Kojent Map application server. The public OAuth client ID identifies this app; it is not an access token.

Storage and sharing

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 app’s code does not send map contents to a Kojent Map server or use advertising or analytics 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.

Retention and deletion

Local maps can be removed from My maps. Clearing this website’s browser data removes its stored local maps, preferences and pending changes; export anything you want to keep first. Closing the page clears its in-memory Google token.

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.