How ScopeWorth handles website information, account data and customer delivery evidence.
Gustavo de Souza Coelho, trading as ScopeWorth, is based in Den Haag, the Netherlands, KvK 42167762. For website inquiries, accounts, billing, fraud prevention and service security, ScopeWorth acts as a controller. For delivery evidence a customer connects or uploads, the customer gives the instructions and ScopeWorth acts as its processor, or subprocessor where the customer acts for a client.
Product processing is governed by the applicable customer agreement and Data Processing Agreement. Website marketing is separate from Customer Content.
When you request a report or contact us, we collect the fields you submit, such as your name, work email, company, website, tools and message. Cloudflare D1 stores the submission, its timestamp, user agent, country derived from the request and campaign attribution such as UTM parameters or a LinkedIn click id. We use it to answer your request, deliver the requested material and manage the conversation. Do not include sensitive personal data in free-text fields.
The product processes the sources the customer authorizes: work-item and code-change metadata, connected calendar or communication data, uploaded evidence, time and cost inputs, mappings, report facts and optional AI feature inputs. When enabled and consented, labelled text-based AI-assistance estimates and Project Forensics narratives use minimized titles, shortened descriptions, commit subjects, work-item and objective text, and validated metric slots; code diffs are not sent for these features. Availability and scope depend on the integration and feature the customer enables. Connected source vendors are selected by the customer; they are separate from ScopeWorth’s service providers.
When a customer connects Google Calendar, ScopeWorth requests read-only access to the calendar list and event metadata to calculate meeting time for delivery reports. ScopeWorth’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Account and billing information support authentication, subscriptions and service administration. We do not use delivery evidence for website advertising.
Where configured, PostHog EU records website page views, interactions, campaign attribution, clicks through to sign up or sign in, and form-conversion events. Before an analytics choice, the browser client can use memory-only identifiers; accepting analytics enables persistent first-party storage, and rejecting analytics stops browser capture. On an accepted sample-report contact request, a profile can include the submitted email, name and company. Server-side lead analytics may use a hashed email-derived identifier and submission metadata. An analytics cookie choice does not erase the inquiry you asked us to handle.
When you are signed in to the ScopeWorth app, PostHog EU can record pseudonymous product-usage events: route-level page views, features used, onboarding steps, and report and plan milestones. They are linked to an internal account identifier and your account’s email domain, never your name, email address, client names, file contents or financial figures. The app runs on the same scopeworth.app address, so its browser analytics follow the same cookie choice as the website: cookieless before a choice and none after a decline. With analytics accepted, website visits before sign-up can be joined to that pseudonymous account journey.
Account-milestone events recorded by ScopeWorth’s servers, such as sign-up, onboarding completion, report generation and subscription changes, are processed under our legitimate interest in operating and improving the service, regardless of the cookie choice. They use the same internal identifier and email domain, not workspace content. With analytics consent, app sessions may be recorded as session replays with all on-screen text and form inputs masked; replays are kept for 30 days. Analytics runs on the production site only: staging, preview and local copies send no analytics.
Cloudflare provides hosting, spam protection and website traffic measurement. Necessary request processing can include IP addresses and browser information.
With marketing consent, the LinkedIn Insight Tag, the Google Ads tag and Google Tag Manager can collect page URLs, referrers, IP addresses, browser and device characteristics, timestamps, cookies and advertising identifiers, including LinkedIn and Google ad-click identifiers. For attributed lead submissions, the configured LinkedIn Conversions API can receive a SHA-256 hash of your work email, a LinkedIn click identifier, company, country, conversion time and a submission-derived event id.
When a paid plan is purchased in the ScopeWorth app, Google Ads receives the purchase amount, its currency and the Stripe checkout reference; it does not receive the app page address. For a visitor who arrived from a LinkedIn campaign, ScopeWorth's servers send the LinkedIn Conversions API a SHA-256 hash of the account email, the LinkedIn click identifier, the purchase amount and currency, the conversion time and a checkout-derived event id. Hashing an email does not make it anonymous.
These paths measure campaigns and can support audience matching or retargeting. They are disabled on staging and controlled internal test traffic. Browser and server paths respect a marketing opt-out and GPC.
We treat LinkedIn and Google advertising measurement and audience matching as potential sale or sharing for applicable US privacy rights. You can opt out for this browser at any time. Global Privacy Control (GPC) overrides a saved marketing opt-in. This website has no signed-in marketing account; the choice applies to the browser that sends it.
You may also contact privacy@scopeworth.app for a privacy request. Using essential forms and requesting a report does not require advertising consent.
The plan’s data window controls how far back syncs and reports read: 90 days for Free and 365 days for Starter, Growth and Scale. Stored raw connector responses also expire 90 days after fetch on Free or 365 days after fetch on paid plans. A fresh fetch starts a new clock. Normalized delivery facts and published reports follow the workspace lifecycle; these raw-response limits do not erase provider copies, backups, audit, billing, Support or AI history.
Workspace deletion has a 30-day cancellation and export grace period, followed by automated purge. Backups can retain a recoverable copy for up to 14 days; deleted blobs can remain within the provider’s 7-day soft-delete window. Restoring a database requires replaying deletion records before serving it. An export link is single-use and expires after 24 hours; raw provider payloads and secrets are excluded from customer exports.
Minimal DPA acceptance evidence is kept for seven calendar years after organization deletion or agreement termination, whichever is later, under the customer agreement’s evidence policy. A justified legal hold can extend that evidence retention. It does not preserve deleted Customer Content. Website inquiries are retained for the response and follow-up purpose; contact privacy@scopeworth.app to request removal or an explanation of the applicable retention.
See the subprocessor list for purposes, locations and activation limits. Delivery evidence, financial inputs, connector credentials, reports, PDF snapshots and export artifacts stay in the assigned production data plane: Central US or North Europe (Ireland), including regional database backups, blobs, queues and telemetry. Shared accounts, authentication sessions, memberships, workspace directory and billing metadata remain in the US control plane. Manual Ask uses Microsoft Foundry: a US Data Zone deployment for US workspaces and an EU Data Zone deployment for EU workspaces. Inference may run elsewhere within the selected data zone. The regional application sends questions and selected evidence to its selected data zone and stores answers in the assigned workspace data plane. Bounded credit and operation metadata goes to the shared US control plane. Global edge traffic, mail, billing and analytics have separate provider locations. A regional storage pin does not mean every provider processes data in that region.
Provider processing agreements and transfer safeguards have been reviewed for Azure, Cloudflare, Resend, PostHog and OpenAI; service activation and data locations are described separately. Customer Content is not used to train general-purpose models. OpenAI sharing is disabled in the reviewed account, with standard provider retention; the report callers disable stored Responses. Manual Ask uses Azure-hosted models, separately from the optional OpenAI report configuration. Standard Microsoft abuse monitoring applies; no zero-retention or modified-monitoring claim is made. ScopeWorth requests store: false for Responses calls. Anthropic remains conditional and unconfigured.
Depending on the law that applies, you may request access, correction, deletion, restriction, portability or objection, and withdraw consent where processing relies on it. For Customer Content, ask the customer organization that controls the source data; we assist it with valid requests. You may contact the Dutch Data Protection Authority or another competent supervisory authority.
Contact privacy@scopeworth.app for privacy questions and security@scopeworth.app for security reports. We may verify a request before disclosing or changing personal information.