Private beta Join the beta

Privacy Policy

Last updated:

This Privacy Policy explains how FullSystems Inc. ("FullVision", "we", "us") collects, uses, and protects your information when you visit fullvision.io or use the FullVision web application (together, the "Service"). FullSystems Inc. is a Delaware corporation (EIN 37-2231020) and is the data controller responsible for your information.

What we collect

We collect only what we need to run the Service:

  • Account information: your name, email address, and password (or the identifier returned by Google / Microsoft if you sign in with them).
  • Billing information: handled by Stripe. We receive the last four digits of your card and billing metadata; we never see or store your full card number.
  • Usage data: the dashboards you view, the reports you run, and the integrations you connect, so we can deliver and bill the Service.
  • Technical data: IP address, browser type, device info, and pages visited. Collected automatically via standard server logs and cookies.
  • Communications: anything you send us by email or through the support chat.

How we use it

  • To provide, maintain, and improve the Service.
  • To process payments and send invoices.
  • To respond to support requests.
  • To send you product updates and occasional marketing emails (you can unsubscribe at any time).
  • To detect abuse, prevent fraud, and comply with legal obligations.

We do not sell your personal data, and we do not use it to train third-party AI models.

Who we share it with

We share your data only with service providers that help us run the Service, under contractual confidentiality obligations:

  • Cloudflare: website and application hosting, CDN, and DDoS protection.
  • Stripe: payment processing and billing.
  • Supabase: application database (account data, connection settings, and encrypted access tokens).
  • ClickHouse: analytics database (tracking events, revenue, and advertising performance data).
  • Railway: hosting for FullVision's backend services.
  • Vercel: hosting for the FullVision dashboard and its AI gateway.
  • Anthropic: AI model provider for the in-dashboard assistant, which processes a customer's data only when that customer asks it a question. This data is not used to train AI models.
  • Amazon Web Services: cloud infrastructure underlying the providers above.

We may also disclose information if required by law, to enforce our Terms, or to protect the rights, safety, or property of FullVision, our users, or others.

Requests from public authorities

FullSystems Inc. reviews every request from a public authority for personal data to confirm it is lawful, challenges requests it considers unlawful, discloses only the minimum data the request legally requires, and keeps a record of each request, its response, and the legal reasoning behind it.

Google Search Console data

FullVision offers an optional integration with Google Search Console (GSC). When you connect your Google account, FullVision accesses a subset of your GSC data via the Google Search Console API. This section describes how that data is collected, used, and protected.

What we access. When you grant consent, FullVision requests the following scope:

  • https://www.googleapis.com/auth/webmasters.readonly: read-only access to Search Analytics data for the GSC properties you own.

We do not request write access, and we cannot modify any settings, properties, sitemaps, or other resources in your Google account.

How we use it. GSC data is used solely to attribute paid customer acquisitions in your FullVision workspace to the organic Google search queries that drove them, so you can see per-keyword revenue inside the FullVision dashboard.

Limited Use. FullVision's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

  • We do not use GSC data to serve advertising of any kind, including retargeting, personalized, or interest-based advertising.
  • We do not sell GSC data, and we do not transfer it to third parties except as necessary to provide or improve the FullVision integration, comply with applicable law, or as part of a merger, acquisition, or sale of assets (with notice to you).
  • We do not allow humans to read GSC data unless (a) we have your affirmative agreement for specific identifiable data, (b) it is necessary for security purposes (e.g., investigating abuse), (c) it is necessary to comply with applicable law, or (d) the data is aggregated and used for internal operations.
  • We do not use GSC data to develop, improve, or train generalized or non-personalized AI/ML models.

Storage and retention. Access and refresh tokens are stored encrypted at rest in our database. GSC query data fetched on your behalf is stored in your workspace's data store and is accessible only to authenticated users of that workspace. You can disconnect the integration at any time from your FullVision dashboard or by revoking access in your Google account permissions; doing so immediately revokes our refresh token and we delete any cached GSC data within 30 days.

Security. Tokens and GSC data are encrypted in transit (TLS 1.2+) and at rest. Access is gated by workspace-level role-based access control.

Google Ads data

FullVision offers an optional integration with Google Ads. When you connect your Google account, FullVision accesses your Google Ads data via the Google Ads API and, if you enable conversion export, sends conversion data to your Google Ads account via the Google Data Manager API. This section describes how that data is collected, used, and protected.

What we access. When you grant consent, FullVision requests the following scopes:

  • https://www.googleapis.com/auth/adwords: access to the Google Ads accounts you manage. We use it to read campaign, ad group, ad, keyword and search-term performance (spend, clicks, impressions, conversions), click identifiers (gclid) for attribution, and to create conversion actions in your account when you enable conversion export. Google Ads offers a single scope for read and write; FullVision only modifies campaign settings (for example, adding a negative keyword or pausing a campaign) when you explicitly request or approve that change in the FullVision dashboard, and every change can be reverted.
  • https://www.googleapis.com/auth/datamanager and https://www.googleapis.com/auth/cloud-platform: requested only when you enable conversion export or audience match. They allow FullVision to upload offline conversions (for example, a payment recorded in your billing system) and customer-match lists to your own Google Ads account through the Google Data Manager API.

How we use it. Google Ads data is used solely to attribute revenue in your FullVision workspace to the campaigns, keywords and ads that drove it, to compute return on ad spend, and — when you enable it — to send your own conversion events back to your Google Ads account so that Google can optimise bidding on real revenue.

Limited Use. FullVision's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

  • We do not use Google Ads data to serve advertising of any kind on FullVision's behalf, including retargeting, personalized, or interest-based advertising. Conversion and audience data is only ever sent to your own Google Ads account, at your request.
  • We do not sell Google Ads data, and we do not transfer it to third parties except as necessary to provide or improve the FullVision integration, comply with applicable law, or as part of a merger, acquisition, or sale of assets (with notice to you).
  • We do not allow humans to read Google Ads data unless (a) we have your affirmative agreement for specific identifiable data, (b) it is necessary for security purposes (e.g., investigating abuse), (c) it is necessary to comply with applicable law, or (d) the data is aggregated and used for internal operations.
  • We do not use Google Ads data to develop, improve, or train generalized or non-personalized AI/ML models.

Storage and retention. Access and refresh tokens are stored encrypted at rest in our database. Google Ads performance data fetched on your behalf is stored in your workspace's data store and is accessible only to authenticated users of that workspace. You can disconnect the integration at any time from your FullVision dashboard or by revoking access in your Google account permissions; doing so immediately revokes our refresh token and we delete any cached Google Ads data within 30 days.

Security. Tokens and Google Ads data are encrypted in transit (TLS 1.2+) and at rest. Access is gated by workspace-level role-based access control.

Meta Ads data

FullVision offers an optional integration with Meta Ads (Facebook and Instagram advertising). When you connect through Facebook Login for Business, you choose which ad accounts, datasets and Pages FullVision may access, and FullVision uses the Meta Marketing API on your behalf. This section describes how that data is collected, used, and protected.

What we access. FullVision requests the following permissions:

  • ads_read: to read campaign, ad set and ad performance (spend, impressions, clicks, conversions) for the ad accounts you connect, so that spend can be tied to the signups and revenue it drove.
  • ads_management: to send your own conversion events to your dataset through the Conversions API, to build custom audiences in your own ad account when you enable audience match, and to create or change campaigns only when you explicitly request or approve that change in the FullVision dashboard. Every change FullVision makes can be reverted.
  • business_management: to read which business portfolio owns the ad accounts and datasets you selected, so the connection targets the right assets.
  • pages_show_list and pages_read_engagement: to list the Pages you manage and read the Page details needed to publish an ad from that Page, only when you ask FullVision to create an ad.

How we use it. Meta Ads data is used solely to attribute revenue in your FullVision workspace to the campaigns and ads that drove it, to compute return on ad spend, and, when you enable it, to send your own conversion and audience data back to your own Meta ad account. We do not use Meta data to advertise on FullVision's behalf, we do not sell it, we do not share it with other customers, and we do not use it to train generalized AI models. FullVision's use of Meta data complies with the Meta Platform Terms.

Storage and retention. The access token Meta issues is stored encrypted at rest and is used only by FullVision's servers. Meta Ads performance data is stored in your workspace's data store and is accessible only to authenticated users of that workspace. You can disconnect at any time from your FullVision dashboard, which deletes the stored token immediately, or remove FullVision from your Facebook Business Integrations. To have the Meta data FullVision imported deleted, follow the steps on our data deletion page.

Stripe integration

FullVision offers an optional integration with Stripe. When you connect your Stripe account, FullVision reads data from Stripe via read-only OAuth permissions. This section describes how that data is collected, used, and protected, and is separate from our use of Stripe to process FullVision subscription payments described in "Who we share it with" above.

What we access. When you authorize the integration, FullVision reads the following Stripe resources: customers, subscriptions, charges, invoices, payment intents, products, prices, coupons, promotion codes, checkout sessions, payment links, setup intents, balance transactions, disputes, and payouts.

We do not request write access and cannot create, modify, or refund any resources in your Stripe account.

How we use it. Stripe data is used solely to compute analytics in your FullVision workspace, including MRR, churn, customer growth, and related revenue metrics. We do not sell, share, or use Stripe data for any purpose outside of providing the analytics service to your workspace, and we do not use it to train AI/ML models.

Storage and retention. Stripe data and OAuth tokens are stored on FullVision's infrastructure (Supabase, ClickHouse, and Railway) encrypted at rest. Data is retained for the lifetime of your account or until you disconnect Stripe, whichever is sooner. Disconnecting Stripe immediately revokes our access and deletes the stored OAuth tokens. To request deletion of all imported Stripe data, email support@fullvision.io.

FullVision is a separate entity from Stripe, Inc. and is not endorsed by or affiliated with Stripe.

Data retention

We keep your account data for as long as your account is active, and for up to 2 years after closure to handle billing disputes and legal claims. Records we are legally required to retain (such as invoices) are kept for up to 7 years. After that, your data is deleted or anonymized.

International transfers

FullVision is operated from the United States, and our service providers may process data in the U.S. and the EU. Where required, we rely on Standard Contractual Clauses or equivalent safeguards to protect your data when it is transferred internationally.

Your rights

Depending on where you live (e.g. EU/UK under GDPR, California under CCPA), you may have the right to access, correct, delete, export, or restrict the processing of your personal data, and to withdraw consent or object to certain uses. To exercise any of these rights, email us at support@fullvision.io. We respond within 30 days.

Security

We use HTTPS/TLS in transit, encryption at rest, access controls, and regular reviews of our infrastructure. No system is perfectly secure, but we take reasonable steps to protect your information.

Cookies

We use a small number of cookies to keep you signed in, remember your preferences, and measure aggregate usage. You can clear or block cookies in your browser settings; some parts of the Service may not work without them.

Children

The Service is not directed to anyone under 16. We do not knowingly collect personal data from children. If you believe we have, contact us and we will delete it.

Changes

We may update this Policy from time to time. The "last updated" date at the top will reflect the latest version. Material changes will be announced in-app or by email.

Contact

FullSystems Inc.
2261 Market Street STE 92857, San Francisco, CA 94114
Phone: (415) 373-6080
EIN: 37-2231020 (Delaware, USA)
Email: support@fullvision.io