Privacy Policy

Fountain+ Exporter

Google Workspace add-on

Google data we access

The Fountain+ Exporter requests these Google OAuth scopes:

• documents.currentonly: read-only access to the currently open Google Doc (document body text and title)
• script.container.ui: permission to display menus and dialog windows within Google Docs (no data access)

The Exporter accesses the document body text and document title of the currently open Google Doc. That is all. It does not access Drive file listings, email, contacts, or any other Google services.

How we use it

• Document text is read to parse screenplay formatting (Fountain and Mangaplay syntax)
• Parsed text is converted to export formats (PDF, Final Draft, FadeIn, plain text, Fountain)
• All processing occurs locally in your browser. No server-side processing.
• Document title is used only to name the exported file
• We do not use Google user data for advertising, profiling, or any purpose other than the export you initiate

Storage and retention

The Exporter does not store your document content. Processing is ephemeral: data exists in browser memory only during the active export and is gone once the export completes or the dialog closes. No server-side storage, databases, caches, or logs contain your document content. Retention period is zero. No Google user data is stored, so there is nothing to delete.

Fountain+ Studio

Chrome Extension

Permissions

Fountain+ Studio uses the Chrome Extension permission model. Here is every permission and why it is needed:

Chrome permissions:

• sidePanel: opens the Side Panel UI alongside Google Docs. Does not access any user data.
• tabs: detects when a Google Docs tab is active so the Side Panel can sync. Does not read browsing history or other tab content.
• storage: saves user preferences (theme, font size, Side Panel state) via chrome.storage. Does not store document content or personal information.
• identity: authenticates with Google to read the active document via the Google Docs API. Does not access email, contacts, or Google Drive™ file listings.
• offscreen: renders PDF exports in a hidden page (Chrome requires this for off-screen rendering). Does not run background processes or access data beyond the active export.
• downloads: triggers file download when you export (PDF, FDX, etc.). Does not upload files or access your download history.

Host permissions (network access):

• docs.googleapis.com: reads the currently active Google Doc content for live preview and export. Does not write to, modify, or delete any document.
• www.googleapis.com/oauth2: fetches your Google account display name and profile picture to show in the Side Panel. Does not access email content, contacts, or calendar.
• oauth2.googleapis.com: handles OAuth token exchange for secure Google sign-in. Does not store tokens on our servers.
• *.googleusercontent.com: loads your Google profile picture. Does not access any other Google-hosted content.
• api.absolutelyskint.com: our first-party analytics endpoint. See Data Sharing for full details.

Content script

Fountain+ Studio injects a small script into Google Docs pages to bridge the page and the Side Panel. This content script detects when a document is open and relays page-level events (such as tab focus and document URL) to the Side Panel via Chrome messaging. The content script does NOT read, modify, or extract document text from the page. Document content is fetched separately through the Google Docs API.

External messaging

The fountain.plus website and api.absolutelyskint.com can send messages to the extension (for example, to detect whether Fountain+ Studio is installed). No user data flows inbound through this channel.

How we use it

• Document content is read via the Google Docs API for live preview rendering, screenplay analysis, and export. It does NOT modify, write to, or delete any document.
• User preferences (theme, font size) are stored locally via chrome.storage. No document content is stored.
• Your Google account display name and profile picture are displayed in the Side Panel
• Anonymous feature-usage counts are sent to our first-party analytics endpoint (see Data Sharing)
• We do not use Google user data for advertising, profiling, or any purpose other than the features you use

Storage and retention

Fountain+ Studio does not store your document content. Document data is held in memory during the active session and discarded when you close the tab or Side Panel. No server-side storage, databases, caches, or logs contain your document content or personal data. Document data retention is zero.

User preferences (theme, font size, Side Panel state) are stored locally in your browser via chrome.storage.local. No document content is included. These can be cleared by removing the extension or clearing extension data in your Chrome settings (chrome://extensions).

Fountain+ API and Fountain Man

Web service and Discord bot

What we process

Script text submitted to the API is processed entirely in memory and is never stored, logged, or retained after the response is returned. Your API key name is logged for rate-limiting purposes; the key value itself is never written to any log. We do not store, share, or use your script content for AI, LLM, or generative model training of any kind.

What we store

API keys are held in a server-side configuration file. Treat your API key as a secret: do not expose it in client-side code or public repositories. No script content is ever stored. The API's own rate-limit counters are held in memory and reset when the service restarts; they are not persisted to disk.

If you use the Fountain Man Discord bot, we store monthly export counts: your Discord user ID, the calendar month, and the number of exports you have run in it. This is held in a database on our server and persists across restarts. It exists to enforce the monthly export limits published on our pricing page. We do not store your Discord server names, channel names, or message content.

Whether a server has Fountain Man Pro is read directly from Discord each time you run a command. We do not keep our own record of subscription status.

Deletion and your API key

Monthly export counts are tied to your Discord user ID rather than to any one server, so removing the bot from a server does not delete them. They are not deleted automatically.

To request deletion of your API key, your export counts, or any other bot data, contact discard-trap-7v@nope.invalid[click to reveal email].