Summary
Midjourney to Notion is a Chrome extension that reads supported Midjourney or Discord page content at your request and creates pages in a Notion database you select. Extension settings are stored using Chrome extension storage. Several operations use external services, including Notion authorization and APIs, Midjourney requests, analytics and event logging, subscription verification, checkout, and an image-hosting fallback.
The extension does not sell your Midjourney content for advertising. It does, however, transmit data needed for requested saves and may transmit usage, account, subscription, or event metadata to the services described below.
Data the extension may handle
- Midjourney prompts, image URLs, job URLs, parameters, versions, and available video URLs
- Content extracted from supported Discord Midjourney messages when you select Save to Notion
- Notion workspace, database, data-source, page, and authorization information needed to perform requested saves
- A generated extension client identifier
- Detected Midjourney user ID used for history requests
- Subscriber email, Notion account email, activation status, save count, language, timestamps, and product source identifiers when used by subscription or event services
- Usage-event names and, for some save events in the current implementation, serialized prompt-related payload data
Chrome extension storage
The extension uses Chrome local and sync storage for configuration such as the selected database, generated client identifier, subscription information, and locally tracked sync history. Chrome may synchronize values stored in its sync area according to your browser account settings.
The current Midjourney account identifier used by batch export is stored under the canonical local key midjourneyUserId.
Notion authorization and saving
When you connect Notion, you are redirected through Notion’s OAuth flow. The extension exchanges the authorization code through a service operated for the integration, then uses the Notion API to search authorized data sources, inspect and update supported database properties, upload files, and create or update pages.
You control which Notion pages or workspace access the integration receives through Notion’s authorization screen. You can revoke that access from Notion.
Image download, Notion upload, and R2 fallback
For a requested save, the extension may download an image from Midjourney or Discord. It first attempts to send the image through Notion’s native file-upload API.
If native upload fails, the extension may send the image data, file type, generated filename, and extension client identifier to an upload endpoint operated at nodeapi.chatgpt2notion.com. The endpoint stores the image in a configured Cloudflare R2 bucket and returns a public image URL used by the Notion page. This fallback means image data may be processed and retained outside Notion.
Analytics and event logging
The current extension code can send usage events to Google Analytics Measurement Protocol and application-operated logging endpoints. Data may include a generated client identifier, action name, product name, language, subscription state, save count, email when available, timestamp, page context, and optional event data.
The redesigned product website itself does not currently load Google Analytics or PostHog scripts. If website analytics are added later, this policy should be updated before deployment.
Subscription and payment checks
Checkout is provided at tools.aluo.app. Payment information is handled by the checkout and payment provider rather than by this static website.
The extension may send an email address and product identifier to activation and active-order services at supabase139.chatgpt2notion.com and payv2.chatgpt2notion.com. Cached activation may be used when a verification service is temporarily unavailable.
Third-party and operated services
- Google Chrome: extension installation, permissions, and storage
- Midjourney: supported page content and history requests
- Discord: supported message content selected for saving
- Notion: OAuth, database inspection, property updates, file uploads, and page creation
- Google Analytics: extension usage-event measurement
- Cloudflare R2 / operated upload endpoint: fallback image hosting
- Operated activation and logging services: subscription verification and product-event logging
- Payment provider: checkout, order, and billing processing
Each provider may process information under its own terms and privacy policy.
Retention and security
Data stored in Chrome remains until it is cleared, replaced, or the extension is removed, subject to Chrome sync behavior. Notion pages remain until you delete them. R2-hosted fallback images and operated-service logs may be retained for service operation, troubleshooting, abuse prevention, and subscription support. Specific retention periods are not currently guaranteed on this page.
No internet transmission or storage system can be guaranteed completely secure. Do not submit passwords, payment details, private authentication headers, or unrelated confidential material in support requests.
Your choices
- Do not activate a save on content you do not want transmitted to Notion or the fallback services.
- Choose which Notion pages and databases the integration can access.
- Revoke Notion access from your Notion account.
- Clear extension storage or uninstall the extension to remove local settings.
- Delete created pages from Notion and contact support regarding operated-service data associated with an identifiable email or client ID.
Contact
For privacy questions or deletion requests, email [email protected]. Include enough information to identify the relevant account or purchase, but do not send passwords, access tokens, or payment card data.