RepoPress Privacy Policy

1. Data Collection

RepoPress is local-first by default. It does not sell personal data or use data for advertising or tracking.

RepoPress does not include third-party advertising SDKs, does not track users across apps or websites, does not include developer-operated analytics or telemetry, and does not require a RepoPress account.

Data is processed or sent to services you configure only when you initiate workflows such as connecting a repository, importing remote content, syncing, publishing, backing up general materials, checking deployment status, using optional intelligent features, or selecting images.

2. Data Stored Locally

• Current-site content, general materials (including existing general drafts), Markdown content, front matter, slugs, tags, categories, authors, summaries, and publish status are stored in local app data.
• Site profiles, path rules, article presets, sync settings, repository purpose, publishing strategy, release records, version snapshots, and operation logs are stored in local app data.
• General-material backup configuration, including provider, repository target, branch, Markdown root, asset root, and last backup summary, is stored in local app data.
• Image attachments and covers are copied into local app data after you select them, so they can be previewed, optimized, backed up, published, and restored.
• App language preferences, local intelligent-assistance chat history, privacy lock preferences, and private content protection preferences may be stored in UserDefaults or local app data.
• GitHub/GitLab tokens, general-material backup tokens, and optional service API keys are stored in the iOS Keychain.

3. Network Access

RepoPress uses the network only for workflows that you configure and initiate:

• GitHub, GitLab, or self-hosted GitLab API requests for repository import, sync, permission checks, publishing, pull/merge requests, rollback, and deployment status.
• When you configure a backup repository for general materials and start a backup, RepoPress commits the selected Markdown and attachment files to the configured GitHub/GitLab repository.
• Requests to configured site URLs, deployment status endpoints, or GitHub Actions / Pages APIs for post-publish validation and deployment checks.
• Requests to a configured third-party or self-hosted intelligent service when you enable the optional feature and configure an endpoint, model, and API key.
• RepoPress does not provide a default RepoPress cloud sync service.

4. Optional Intelligent Features

Intelligent features are optional and are not required by default.

When you configure a service and initiate an intelligent action, RepoPress may send selected article text, front matter, site context, SEO reports, image metadata, publish package summaries, current chat context, or selected text to the third-party or self-hosted service you configured.

That service's privacy policy and terms govern how it retains and uses the data. If content must never leave your device, do not use intelligent features for that content.

5. Photos, Images, and Attachments

Photos access is used only when you select images as article attachments or covers. RepoPress does not automatically scan your photo library.

Images you select are copied into local app data and may be committed to the repository you configured when you publish articles or back up general materials.

RepoPress may inspect image size, paths, reference status, privacy metadata, or optimization opportunities locally for preflight checks and the image workbench.

6. Face ID / Device Authentication

Face ID or device authentication is used only for the app privacy lock and private content protection, to help protect local articles, private content, and publishing settings.

Authentication is handled by iOS. RepoPress does not receive, store, or upload biometric data.

7. App Store Privacy Labels

RepoPress declares no tracking and no tracking domains. The current App Store label lists Data Linked to You, used only for App Functionality and not for tracking:

• Other User Content: article Markdown, general materials, front matter, repository context, SEO reports, publish summaries, and optional intelligent-assistance prompts.
• Photos or Videos: images selected by the user as article attachments, covers, or general-material attachments.
• User ID: GitHub/GitLab account or repository identifiers configured by the user.

Repository tokens, backup tokens, and optional service API keys remain in the iOS Keychain and are used only to authenticate requests that you initiate. The RepoPress developer cannot access or retain the complete credentials, so they are not separately listed as an App Store collected-data type.

8. User Control

• You can remove GitHub/GitLab tokens, general-material backup tokens, and optional service API keys in app settings.
• You can delete current-site content, general materials, attachments, release records, operation logs, and site profiles.
• You can disable intelligent features, change repository purpose, or use RepoPress locally without connecting any repository.
• You can revoke Photos access in iOS Settings.
• Deleting the app removes local app data according to iOS behavior. Content already published or backed up to a repository must be managed in the corresponding Git service.

9. Children's Privacy

RepoPress is not directed to children and does not knowingly collect children's personal information.

10. Changes to This Policy

If app features, data handling practices, or App Store privacy declarations change materially, this page will be updated.

11. Contact

For privacy or support questions, contact: support@chengjinfang.com