Use locally
Core Scope records can be used without sign-in. Local data stays on the device unless you export, share, or back it up.
Scope is local-first because client work deserves control.
This page summarizes the Scope-specific privacy posture. The general Polenest privacy policy remains available at /privacy.
Data categories
| Local project records | Project names, client names, currency, budget notes, estimated hours, SOW text, pricing policy, scope items, and approval records are stored in the app workspace. |
|---|---|
| SOW templates | Reusable SOW titles, SOW text, and pricing policy text are stored so you can attach them to projects. |
| Client request notes | Requests you type or paste into the app are used to help you classify the work as in scope or out of scope. |
| Backup files | Export creates a JSON backup file. You choose where that file goes, such as Files, iCloud Drive, Google Drive, or another provider. |
| Diagnostics | Crash logs, app version, OS version, device model, and error details may be used to fix defects and maintain reliability. |
| Purchases | App Store or Google Play handles payment when purchase features are available. Polenest does not store your card number. |
| Support data | Emails and details you send to [email protected] are used to answer your request and diagnose the issue you report. |
Controls
Export backup
Export creates a JSON file named as a Polenest Scope backup. The storage provider you choose handles any upload or sync.
Import backup
Import reads a Polenest Scope JSON backup and replaces the local workspace on that device after confirmation.
Delete content
Projects, SOW templates, scope items, and records can be edited, archived, or deleted from the relevant app screens where available.
What Scope is not
Scope records are practical project records. They are not tax invoices, legal advice, accounting advice, or a guarantee that a client will accept a charge. Review important records before using them outside the app.