You should know where project information is stored, when it reaches your AI, and how to make a data request. This notice describes the current version’s actual features.
Who is responsible
Mapfable is operated personally by Michael Choong, who is responsible for personal data processing in this service. Send privacy, access, correction, or deletion requests to the email below. The service includes local development and restricted hosted testing. Before general availability, this notice will identify hosting providers, processing regions, and retention arrangements.
Google sign-in information
When you sign in with Google, we receive your account identifier, email and its verification status, name, and avatar URL. We use these to create or identify your Mapfable account, display your profile, maintain your session, and establish project ownership. Google sign-in cannot be completed without the required identity information.
Sign-in requests only basic identity, email, and profile access, not Gmail messages, Google Drive files, or contacts. We do not receive your Google password. The current implementation does not persist Google access or refresh tokens. Google’s own policies apply to its sign-in service; loading an avatar also sends a request to Google.
Projects, sources, and activity
We store projects and dungeons, tasks, decisions, ideas, skill records, drafts, review answers, and completion evidence submitted by you or connected tools, together with the versions, timestamps, and activity records needed to maintain them. This supports displaying routes, resuming work, reviewing changes, and recovering incomplete operations.
After you select a folder, only the Markdown content and related information such as relative paths that you select and confirm for import are saved as snapshots. Folder selection does not grant ongoing access to your entire computer or make Mapfable watch changes on disk. Project content is optional; without it, the corresponding source-reading or map-generation features cannot be used.
What your own AI can access
Mapfable exposes project tools to your own AI client through a connection you configure. Tool calls may provide maps, source snapshots, drafts, or decisions to that client and its model service, and save submitted changes in Mapfable. The current local connection covers the local workspace of its bound account; selecting a dungeon in the browser does not restrict this access.
Mapfable currently has no built-in model inference and does not use this information to train its own AI models. Your chosen AI service’s handling of content, logs, and model training depends on its policies and your account settings, not this policy. Disconnecting or deleting data in Mapfable does not automatically delete copies already obtained by a third party.
Cookies and browser storage
Necessary sign-in cookies identify your session, currently for up to 14 days. An OAuth flow cookie protects sign-in for up to 10 minutes. Signing out revokes the current session, not sessions on other devices. Cookie expiry does not mean all server records have been deleted.
The language cookie lasts up to one year. Browser local storage keeps language, theme, and project selection. Session storage may also contain account-specific unconfirmed import content, source updates, and other operation-recovery information. Signing out does not automatically clear this recovery content. You can clear this site’s browser storage, but that may remove local recovery information or require another sign-in; it does not delete server-side projects. The current version has no integrated advertising trackers or third-party behavioral analytics.
Storage, providers, and security
Local data is held on the computer running Mapfable; hosted data is held in a database on the operator’s server. Project maps, history, and skills also have Markdown copies, and manual database backups may contain this information. Access controls restrict account access, and the server stores session-token hashes. This is not a claim of end-to-end encryption.
Google provides sign-in and avatars. If you contact us by email, X, or Telegram, that platform also processes your message, potentially outside your region. We use correspondence to answer questions, verify identity, and handle requests. Legally required disclosures are handled under applicable law.
When subscriptions are enabled, we provide Stripe with your account email, internal account identifier, plan, and transaction information. Card details go directly to Stripe on its hosted checkout page; Mapfable does not store full card numbers. We retain Stripe customer and subscription identifiers, trial dates, paid-access expiry, cancellation status, and deduplicated webhook records to verify access and resolve billing issues. The sandbox is for testing only; Mailgun product emails are not enabled.
Retention, history, and backups
The current preview does not automatically purge accounts, projects, version history, or backups on a schedule. Editing, archiving, or removing content from the current source list does not ensure that copies in history, Markdown, or backups are also removed. Signing out does not erase this data.
Email us to request removal. We will verify your identity and the request’s scope, and explain the outcome and any records that need to be retained and why. A delete or archive action in the interface should not be understood as immediate removal of every copy. Specific retention and backup cleanup arrangements will be established and published before the hosted service opens.
Access, correction, export, and deletion
You can view and edit projects you have access to and download map Markdown. The map download is not a full account-data export. Email us for broader access, a copy, correction, deletion, or other applicable data-rights requests. Identity verification may be required; do not send passwords or connection secrets.
You can remove the Mapfable connection in your AI client or revoke Mapfable’s sign-in authorization in your Google account. Revoking Google authorization does not automatically end an existing Mapfable session or delete your account; also sign out of Mapfable and request deletion separately if needed. This notice does not limit rights provided by applicable law.
Changes to this notice
When hosting, payments, email, or other features change how data is processed, we will update this page’s date and explain important changes in the relevant product flow. We will seek consent before uses that require it. Contact Michael directly with questions about data handling.