Privacy Policy

2.1 Account information

When you sign in, we receive basic account information from your sign-in provider (for example, your GitHub username, profile name, email address if available, and a provider identifier). We use this to create and manage your account and to provide the Service.

2.2 Configuration and operational data

We store the information needed to run backups and show history in the app, such as:

• Selected backup roots (page/database IDs and optional friendly names)
• Selected destination repository (repo ID, owner/name, default branch)
• Schedule settings (manual/daily/weekly), path prefix, enabled/paused state
• Backup runs, timestamps, statuses, error codes/messages, and logs
• Job queue state (attempts, retry timing, lock state)

2.3 Support communications

If you contact support, we may receive the information you provide (such as your email address and message contents). We use this to respond and resolve issues.

NotionGitBackup is designed to minimize what we store. In particular:

Note: The Service may temporarily process Notion content in memory to convert it to snapshot files that are written to your GitHub repository. This transient processing is necessary to provide the Service.

We use information to:

• Provide, maintain, and improve the Service (including job scheduling and retries)
• Authenticate users and prevent abuse
• Send service-related emails (for example, failure alerts)
• Provide customer support
• Comply with legal obligations and enforce our Terms

The Service integrates with Notion and GitHub. Your use of those services is governed by their respective terms and policies.

5.1 Notion

After you authorize NotionGitBackup via OAuth, the Service can access Notion content that you explicitly share/authorize with the integration (for example, the pages and databases you select as backup roots, and their child content where permitted).

5.2 GitHub

After you install the GitHub App and select a repository, the Service can read and write files in that repository as permitted by the GitHub App’s granted permissions. Snapshot files are committed into that repository path that you configure.

Notion and GitHub are trademarks of their respective owners. NotionGitBackup is not affiliated with, endorsed by, or sponsored by Notion or GitHub.

We take reasonable measures designed to protect your information and the Service:

• Connection tokens are stored encrypted at rest where feasible
• We avoid logging secrets and sensitive tokens
• We use access controls to restrict internal access to operational data
• We use HTTPS for Service communications

No method of transmission or storage is 100% secure. You are responsible for securing your Notion and GitHub accounts, including enabling multi-factor authentication.

We retain account and operational metadata for as long as needed to provide the Service, comply with legal obligations, resolve disputes, and enforce agreements.

Backup snapshot files are stored in your GitHub repository. You control how long those files and commit history are retained by managing your repository.

Depending on your location, you may have rights to access, correct, delete, or export personal information. You can also:

• Disconnect integrations (if available in-app) or revoke access in Notion/GitHub
• Control repository visibility (public/private) and collaborator access on GitHub
• Update your backup roots and schedules

To request assistance with data rights, contact support using the contact method provided in the Service.

Your information may be processed in countries other than where you live. Where required, we take steps designed to ensure appropriate safeguards for international transfers.

The Service may use essential cookies and similar technologies to maintain sessions and provide core functionality (for example, authentication). If we use analytics, we aim to keep it lightweight and privacy-conscious.

If you add additional analytics or marketing tools, you should update this section to reflect those tools and provide any required consent mechanisms.

The Service is not directed to children and is not intended for use by anyone under the age of 13 (or the age required by local law). We do not knowingly collect personal information from children.