Privacy Policy
This policy explains how Scope-to-Go handles information when facility professionals use the service to scope projects, solicit proposals, compare contractor responses, and prepare approval records.
Information we collect
We collect pilot-request information such as name, work email, organization, facilities role, facility-count range, and the project challenge submitted; founder application notes; pilot feedback; account identity information; organization and membership information; project scopes, facility details, contractor contacts, proposals, uploaded documents, clarification records, recommendations, onboarding progress, product usage, audit events, and billing status. Payment-card information is entered directly into Stripe-hosted services and is not stored by Scope-to-Go.
Contractor submissions
When a contractor uses a secure proposal link, Scope-to-Go processes the contractor identity supplied by the requesting organization, the proposal PDF, optional submission notes, submission and replacement timestamps, and an audit record of the accepted submission terms. Expiring one-way identifiers derived from the secure link and network request may be used to limit abusive upload attempts; raw network addresses are not stored in the submission-limit record.
Public-site analytics
Scope-to-Go records privacy-conscious, aggregated counts for public page views, product-tour plays, pilot-form starts, and submitted pilot requests. These counts help evaluate whether the public page is useful. Raw IP addresses and full referring-page URLs are not stored as analytics data.
With your optional permission, we also use a first-party, randomly generated session cookie lasting up to 30 minutes to understand public-page landing points, source categories (such as Google, LinkedIn, Facebook, or direct), pages visited next, and progress through pricing, workspace signup, checkout, verified payment, and first-project creation. Analytics receives fixed page and source labels, not URL query strings, names, email addresses, project contents, or payment-card details. It is not used for advertising or cross-site profiling. Temporary, one-way hourly network-request identifiers help rate-limit abuse and are removed after 48 hours when analytics cleanup next runs. A one-way organization identifier associates verified service milestones with the consenting session for up to seven days. Reports cover the most recent 30 days of session and page-journey records; older records are deleted when analytics collection or reporting next runs. These counts are not a record of every visitor or a count of unique people; tabs may share the session cookie. Tracking begins only after permission, so earlier pages are not recovered.
You can decline without affecting the service or change your choice using the analytics control below. Turning analytics off removes the current linked journey. When signed in, it also removes retained journey attribution for workspaces you own, including after the session cookie expires. To withdraw earlier workspace attribution after signing out or on another browser, sign in and turn analytics off. The choice is remembered in this browser tab for up to 30 minutes. We honor Do Not Track and Global Privacy Control for this optional tracking. Known testing and founder activity are excluded; blocked tracking, declined permission, expired sessions, and visits on other browsers or devices limit attribution. No missing historical journeys are reconstructed.
How information is used
Information is used to review pilot applications, provision invitation-only workspaces, follow onboarding and first-project milestones, respond to pilot feedback, provide and secure the service, isolate customer workspaces, generate requested AI assistance, process subscriptions, communicate service information, troubleshoot problems, enforce plan limits, preserve audit history, and comply with legal obligations.
AI processing
When an authorized user requests AI assistance, relevant project text or contractor documents may be sent to OpenAI’s API to produce the requested output. Users must avoid submitting information they are not authorized to process. AI output must be reviewed by a qualified person before procurement, contracting, safety, legal, or financial decisions are made. OpenAI states that API business data is not used to train its models by default.
Service providers
Scope-to-Go uses infrastructure and service providers to operate the application, including OpenAI for AI processing, Stripe for subscription billing, and hosting and storage providers for application delivery and customer files. These providers process information under their own agreements and privacy practices.
Customer control and retention
Organization administrators can select document-retention settings, manually delete uploaded proposal PDFs, and export organization records. Deleting a PDF removes the stored file while retaining the proposal’s normalized comparison data and audit record. Some information may be retained when required for security, fraud prevention, legal compliance, backup integrity, or dispute resolution.
Security
Scope-to-Go uses authenticated access, organization-level authorization, protected storage paths, non-cacheable customer responses, signed billing webhooks, and activity records. No internet service can guarantee absolute security, and customers remain responsible for managing authorized users and the sensitivity of submitted information.
Sharing and disclosure
Scope-to-Go does not sell customer project data. Information may be shared with authorized organization users, service providers needed to deliver the service, or authorities when legally required. Data may be processed in the United States or other locations where service providers operate.
Your choices and account deletion
Organization administrators may correct account information, manage members, export records, and change document-retention settings. Any account user may request deletion of their individual account from Organization Settings or through the public account-deletion page. Organization owners may use the same process to request closure of the organization workspace and deletion of its associated projects, files, contractors, proposals, and member access.
Deletion requests are identity-verified before processing. Individual deletion removes the requesting person’s profile and access but does not delete project records owned by an organization with other authorized users. Some records may be retained only when required for billing, tax, security, fraud prevention, dispute resolution, backup integrity, or another legal obligation. Retained information is restricted from ordinary product use and deleted when the applicable obligation ends.
Other privacy requests may be sent to thesimpletim@gmail.com.
Changes
This policy may be updated as Scope-to-Go develops. Material changes will be communicated through the service or another reasonable channel, and the effective date will be revised.