Legal · Trust · Privacy
Privacy Policy
ScopeDue helps freelancers create clear business records for client changes, approvals, payment status, handoff events, and Proof Packs. This policy explains what information may be collected, how it is used, who can see it, and how to manage privacy questions before or after using ScopeDue.
Last reviewed: May 26, 2026 · Applies to ScopeDue public pages, workspaces, approval links, support requests, and product-related communications.
Policy summary
What this privacy policy covers
ScopeDue is built around records that freelancers and small service providers intentionally create: projects, original scope records, priced change requests, client approval links, payment status history, uploaded proof, handoff status, and Proof Pack exports. The goal is to help you keep client changes professional without turning ScopeDue into a marketplace, CRM, accounting system, or legal contract platform.
Information you enter
Workspace, account, client, project, approval, payment status, file upload, and support information that you or invited clients provide.
How it is used
To operate approval links, maintain payment status history, confirm freelancer-controlled records, export Proof Packs, provide support, and keep the service reliable.
How to manage it
Contact ScopeDue for privacy questions, account-data requests, access issues, or help with client-facing approval records.
Quick navigation
Privacy topics on this page
Information collected
Information ScopeDue may collect
ScopeDue collects information that is needed to run a freelancer approval and payment proof workspace. The exact information depends on whether you browse the public website, create an account, send an approval link, interact as a client, upload payment proof, or contact support.
- Account and workspace information
- Name, email address, workspace name, profile settings, default currency, timezone, sign-in events, and basic product preferences.
- Client and project information
- Client names, client emails, company names, project titles, original scope notes, deliverables, revision limits, handoff terms, and payment-related notes that you choose to enter.
- Approval and change request information
- Priced change request details, timeline impact, approval status, decline or question responses, approval events, and related messages.
- Payment ledger information
- Payment item title, amount due, due date, status history, client marked paid events, proof uploaded events, freelancer confirmed received events, partial payment notes, overdue status, waived status, and disputed status.
- Files and proof uploads
- Receipt images, payment evidence, project attachments, file names, file metadata, file size, and related record references when uploads are enabled.
- Technical and usage information
- Device, browser, IP-derived approximate location, pages viewed, link activity, error logs, audit logs, and security events needed to operate, troubleshoot, and protect the service.
- Support and communication information
- Messages you send to ScopeDue, support category, attachments you choose to include, and replies needed to handle the request.
Use of information
How ScopeDue uses information
ScopeDue uses information to provide the specific approval, payment status, handoff, and proof workflows requested by freelancers and their clients. The product is focused on creating clear business records, not on selling freelancer-client records as advertising data.
- Operate the service: create accounts, workspaces, clients, projects, change requests, approval links, payment items, and Proof Packs.
- Show the right records to the right people: display approval request details to the client who receives the link, and display workspace records to the freelancer or authorized workspace users.
- Track approval and payment events: save client approval, client marked paid, proof uploaded, freelancer confirmed received, overdue, waived, disputed, and handoff history.
- Support handoff rules: show when work or final handoff is waiting on a required condition, such as freelancer-confirmed payment.
- Provide support: answer questions, troubleshoot account access, investigate delivery or upload issues, and respond to privacy requests.
- Improve reliability and safety: monitor errors, prevent abuse, maintain audit trails, protect private routes, and diagnose product performance.
- Send service communications: send account, approval, payment status, security, and support messages related to the service.
Approval links
Client approval links and private records
A ScopeDue approval link is meant to help a client review a specific request: what changed, what it costs, how it affects the timeline, whether payment is required, and what happens next. Public SEO pages may link to static samples such as a sample approval link, but private client-specific project pages and generated user records should not be treated as public marketing pages.
| Record area | Who may see it | Privacy note |
|---|---|---|
| Public website pages | Anyone who visits the public website | Includes pages such as features, pricing, legal, help, and static samples. |
| Client approval link | The freelancer, authorized workspace users, and the client or recipient with access to the link | Used to review, approve, decline, ask questions, or mark a related payment as sent. |
| Workspace dashboard | The freelancer and authorized workspace users | Used to manage projects, approved-but-unpaid changes, payment pending confirmation, overdue items, and handoff locks. |
| Proof Pack export | The person who exports it and anyone they choose to share it with | May include approval timeline, payment status history, uploaded proof references, handoff status, and export timestamp. |
Keep client-specific links, exported Proof Packs, and uploaded proof in private channels. Do not publish them publicly unless you have the right to share the underlying information.
Payment and proof
Payment status, proof uploads, and freelancer confirmation
ScopeDue’s payment ledger is designed to record payment status events, not to act as a full accounting system or guarantee payment. A client may mark payment as sent or upload proof, but the freelancer controls final confirmation that payment was received.
Client-side payment actions
- View the requested payment item.
- Mark payment as sent.
- Upload a receipt or payment proof when allowed.
- Ask a question or flag a problem.
Freelancer-side payment actions
- Request payment for a change, milestone, source file fee, or final handoff.
- Confirm payment received.
- Confirm partial payment when supported.
- Mark a payment overdue, waived, refunded, or disputed where appropriate.
Retention and exports
Retention, Proof Packs, and deletion requests
ScopeDue keeps records for as long as needed to provide the service, maintain account history, preserve event-backed proof records, comply with legal obligations, resolve disputes, prevent abuse, and support backups. Because ScopeDue is built around approval and payment history, deleting or editing historical events can affect the usefulness of a record.
- During active use: project, approval, payment, handoff, and Proof Pack information remains available in the workspace according to account settings and product rules.
- After export: a Proof Pack downloaded or shared by a user may exist outside ScopeDue. The person who exports it is responsible for where they store or share it.
- After account closure: ScopeDue may delete, anonymize, or retain certain records when needed for security, legal, backup, audit, support, or legitimate business purposes.
- After a privacy request: ScopeDue will review the request and respond based on the account, workspace role, record type, identity verification, and applicable requirements.
Your choices
Your privacy choices and request options
You can manage some information directly through your account or workspace settings when those controls are available. For other requests, use the contact path and include enough detail for ScopeDue to find the relevant workspace, approval link, payment item, or Proof Pack record.
- Access: ask what account or workspace information is associated with you.
- Correction: ask to update inaccurate account, client, or workspace information.
- Deletion: ask whether specific account, support, client, or project information can be deleted.
- Export: use Proof Pack export for project records where available; ask support if you need help accessing your data.
- Communication preferences: unsubscribe from optional product marketing when available; service emails may still be sent for account, approval, payment, or security reasons.
- Client link concerns: if you received a client approval link and have a privacy concern, include the link or project context when contacting ScopeDue.
Security
Security and responsible limitations
ScopeDue is designed to handle sensitive business workflow information such as client approvals, payment status history, receipt uploads, and handoff records. Reasonable safeguards should be used to protect accounts, client links, file uploads, audit logs, and private workspace routes. No online service can promise perfect security, so users should avoid putting unnecessary sensitive information into project notes, messages, or file uploads.
What you can do
- Use strong account credentials.
- Only send approval links to the intended client or contact.
- Do not upload unnecessary sensitive documents.
- Revoke or update links when a project relationship changes.
What ScopeDue should support
- Private routes for workspace and client-specific records.
- Access controls for approval links and app pages.
- Audit events for approvals, payments, uploads, and handoff records.
- Clear support paths for suspicious access or upload issues.
For a plain-language product security overview, visit the ScopeDue security approach.
Children
Children’s privacy
ScopeDue is intended for freelancers, solo studios, small service providers, and their business clients. It is not intended for children. If you believe a child provided personal information to ScopeDue, use the contact path so the issue can be reviewed.
Updates
Changes to this policy
ScopeDue may update this Privacy Policy when the product changes, new workflows are added, service providers change, legal requirements evolve, or privacy controls are improved. The last reviewed date at the top of the page should be updated when material changes are made.
Manage privacy / contact
Privacy request checklist
To make a privacy request easier to handle, include the information that best identifies the record without sending unnecessary sensitive details.
| Request type | Helpful details to include | Avoid sending |
|---|---|---|
| Account or workspace privacy | Your account email, workspace name, and a short description of the request. | Passwords, payment account credentials, full bank details, or unrelated client documents. |
| Client approval link concern | The approval link, project name, client email used for the link, and what needs review. | Extra personal documents that are not part of the approval record. |
| Payment proof or receipt issue | Project name, payment item, approximate date, and whether you are the freelancer or client. | Unmasked bank login information or full payment account screenshots when a redacted proof is enough. |
| Proof Pack or export question | Workspace, project, export date if known, and the section you are asking about. | Public posting of private Proof Pack links or client-specific records. |
Need to manage a privacy question?
Use the contact page to ask about account data, client approval links, payment proof records, Proof Pack exports, or privacy controls. Include enough context to identify the record, but avoid sending sensitive information that is not needed.