Nator provides a private card library at nator.aplomo.ai. Its accounts, sessions and database are isolated to this Nator service.
Information we store
When you sign in with Google, we store your Google account identifier, name, email and profile picture. The extension can save qualifying watched-video records, titles, channels, video durations, viewing dates and generated Narration Cards. Video records power your personal timeline; cards power your library. We do not request access to Gmail, Google Drive or other Google content.
AI processing
The extension asks you to agree to its AI data notice before processing. To translate captions and explain concepts, caption text, video title, channel and selected languages pass through Nator’s Cloudflare service and Pipixia AI (api.psydo.top) to the configured model provider. On-device translation stays on your device. Upstream handling and retention follow the provider’s terms. Application logs do not record caption or card text. Disable the extension to stop new AI requests.
AI safety checks
Our AI Acceptable Use Policy restricts pornographic and other prohibited AI uses. Local and server text checks examine AI input and output; the existing model is instructed to refuse restricted content. No additional moderation provider receives this text for these checks. Safety checks do not add raw captions or card text to application logs. Basic YouTube subtitles and video images are not reviewed by this text check. Detection is limited and may make mistakes; contact nator@aplomo.ai for review.
Sign-in and synchronization
The website uses a necessary sign-in cookie; the extension keeps its session in extension-only storage. In the same Chrome profile, signing in on either side can sign in the other side to the same Nator account. Short-lived, single-use authorization codes connect these sessions; the website does not receive the extension’s long-lived session token. If both sides already use different accounts, they are not silently switched. Signing out revokes the account’s active sessions on both sides. Signed-out users do not save personal video records or cards to the cloud. To provide a trial, the server stores a hash of a random installation identifier, random playback-session identifiers and cumulative AI-assisted playback time, without video titles or captions in those allowance reports. AI rate limits use hashed IP identifiers. Signed-in allowances belong to the account. Your selected translation language and interface language are shared between the extension and website. Pending records remain locally for retry when synchronization fails; signing out stops new cloud saves.
Subscriptions and payments
If you subscribe, Creem processes your checkout, payment details, invoices and billing portal as merchant of record. Nator sends the account email and an internal account identifier to associate your payment with your Nator account. Nator stores provider customer, checkout, subscription and transaction identifiers, payment status and paid periods; it does not receive or store your full card number. A server-side allowance ledger records cumulative AI-assisted playback time and allowance periods to enforce shared plan limits.
Storage and deletion
Account and library data is stored in this project’s Cloudflare database. Google handles authentication and YouTube provides video thumbnails. Nator does not use advertising tracking. You can delete your account from the avatar menu after resolving active subscriptions and pending payment checkouts. This removes cloud video records, cards, preferences and sessions. Minimal provider billing references, payment events and revocation records are retained separately for payment reconciliation, fraud prevention and legal obligations; their Nator user link is removed. Creem maintains its own payment records under its privacy policy.
Saving existing cards does not request additional AI generation. AI explanations and translations may contain errors.
For privacy, billing or deletion assistance, contact nator@aplomo.ai.