Who we are
Proofsource is a product of Grovio Labs, Inc., a Delaware corporation in the United States ("Proofsource", "we", "us"). This policy explains what personal data we collect when you visit proofsource.co, use the Proofsource app at app.proofsource.co, our apps for iPhone, Android and Shopify or our Chrome extension, or contact us, and what we do with it.
Proofsource is a business tool. It measures how AI answer engines mention and cite your brand, and helps you act on what it finds. It is meant for companies and the people who work for them, not for personal use.
The short version
- We collect what we need to run your account and your workspace, and little else.
- We don't sell personal data. We share a little with Meta to measure our own ads, and you can turn that off.
- We don't use your data to train AI models.
- You can ask us for a copy of your data, or to delete it, at any time.
What we collect
- Account details: your name, email address, and a profile picture if you upload one. Your role in your workspace and the workspaces you belong to. If you sign up through an AI assistant, which assistant it was and whether your email address is a work or personal one.
- Workspace content: the brands, domains, competitors, markets and prompts you track, your settings, reports, notes, content drafts, files you upload, and the questions you ask our assistant.
- Measurement data: the answers AI engines give to your tracked prompts, the sources they cite, and copies of cited public web pages.
- Data from services you connect: for example Google Search Console, Google Analytics, Bing Webmaster Tools, CDN analytics, server logs and your website. Logs we receive can include IP addresses and user agents of AI crawlers.
- Credentials for services you connect, such as access tokens and keys. We store these encrypted.
- Billing details: your billing name, email, address, country and tax details. Payment card and bank details are collected by our merchant of record, Stripe or Dodo Payments, not by us.
- Messages: emails, contact form submissions and support conversations.
- Security and usage data: IP address, browser and device type, sign-in times, and actions taken in your workspace.
- Website analytics: see Cookies and analytics below.
Please don't put personal data about other people into your tracked prompts. Prompts are sent to AI engines as written, and the service doesn't need personal data to work.
How we use it
- To provide the service: run your prompts on AI engines, analyze the answers, build your reports, send your alerts, and run the features you turn on.
- To create and secure your account, sign you in, and prevent fraud and abuse.
- To bill you and keep the records the law requires.
- To talk to you: sign-in codes, results, alerts, service and billing notices, and replies to your questions.
- To understand how our website is used and improve the product.
- To meet legal obligations and enforce our Terms of Service.
Data we receive from Google is used only as described under Google user data below.
Legal bases
Where the GDPR or UK GDPR applies, we rely on these legal bases: performance of our contract with you or your company, to provide the service; our legitimate interests in securing, supporting and improving the service; your consent, where we ask for it, which you can withdraw at any time; and legal obligation. Where another country's data protection law applies, we process your personal data for the purposes described here with your consent, or on another basis that law allows.
AI models and your data
- We don't use your data to train AI models.
- To measure your visibility, we send your tracked prompts to AI engines, the same way a buyer would ask them.
- Some features send workspace content to an AI model to do their job. We share with AI providers only what a task needs.
- AI answers we capture are third-party content. We show them to you as evidence of what the engines said.
Connected services
You can connect Proofsource to services you already use. Every connection is optional, started by you on the Integrations page, limited to the brand you pick, and asks only for what its features need. Each subsection below says what we read, what we write and why. These rules apply to all of them:
- Your approval comes first. Proofsource never posts, publishes or changes anything in a connected service on its own. Each post, page, reply or change is shown to you first and goes out only after you approve it. We never delete or change anything else.
- Storage: tokens, keys and passwords for a service are sealed with AES-256-GCM, bound to your organization and connection, and opened only by the Proofsource service that calls that provider. Data we read is stored encrypted at rest on AWS, kept apart for each organization by database row-level security, and visible only to members of your workspace. All traffic uses TLS.
- Use and sharing: we use data from a connected service only to run the features described here for your workspace. We don't sell it, use it for advertising, or use it to train generalized AI models. We share it only with the service providers listed at proofsource.co/subprocessors as needed to run those features, or when the law requires it.
- Disconnecting: you can disconnect any service at any time on the Integrations page. We delete our stored token or key at once and stop all reads and writes. Where the provider lets us, we also revoke our access there. You can also remove Proofsource in the provider's own settings.
- Retention: data we read stays in your workspace until you delete it or your account. Anything you delete in the app can be restored for 90 days, then it is removed. Asking us to delete your account erases it within 30 days. Deleted data leaves our database backups within 35 days.
When you connect a service such as Slack, a webhook or your website, we send data to it because you asked us to. Those services handle the data under their own terms. You can disconnect any of them at any time on the Integrations page.
Google user data
Proofsource asks Google only for what each feature needs, and only when you start that feature.
- Sign in with Google (scopes userinfo.email and userinfo.profile): Google shares your name, email address and profile picture. We keep your name and email address and use them only to create your account and sign you in. We don't keep a Google token for sign-in.
- Search Console (scope webmasters.readonly): we read the list of Search Console sites you can access, so you can pick the one for your brand, and that site's search performance: queries, pages, clicks, impressions, click-through rate, position and index status. If you also allow sitemap updates (scope webmasters), we resubmit your sitemap after a fix you approved goes live, and nothing else. When your site is not yet in Search Console, we can add it and verify your ownership with the token you placed (scope siteverification.verify_only).
- Google Analytics (scope analytics.readonly, read-only): we read the list of Google Analytics properties you can access, so you can pick the one for your brand, and that property's reports: sessions, traffic source and channel, landing pages, key events, transactions and revenue.
- Google Analytics setup (scope analytics.edit): when you press Set up, we create one property for your brand's site with one web data stream if you have none, or add one web data stream to the property you picked if it has none, and show you the Google tag for your site. Undo deletes only the property or stream Proofsource created. We never change or delete anything else in your Google Analytics account.
- Google Business Profile (scope business.manage): we list the locations you manage, so you can pick your brand's, and read its rating and review count. When you approve a reply to a review or a change to your profile, we post that exact reply or change.
- YouTube (scope youtube.force-ssl): after you upload a video to your own channel and approve the text we drafted, we read that video's details and update its title, description and tags. We never upload, delete or change anything else.
- Google Drive and Google Docs (scope drive.file): we can open only the files you pick and the files Proofsource creates for you. We read the Docs, Sheets, PDFs and Word files you pick into a knowledge base, and when you ask, we create a Google Doc with a drafted fix. We can't see the other files in your Drive.
- Google Calendar (agency workspaces; scopes calendar.events.owned and calendar.events.freebusy): when you connect your calendar, we read your free and busy times on your primary calendar and create, on that calendar, only the meetings you send from Proofsource, and Google sends the invitations. We never read, change or delete any other event.
How we use it: only to show it back to you and your workspace in Proofsource and to run the features above. That means the Organic search, AI referrals and Reviews pages, reports you create, agent steps you add, knowledge bases, and ranking which of your tracked prompts matter most. We write to your Google accounts only as described above, and only after you approve each change.
Storage and security: all traffic between your browser, Proofsource and Google travels over TLS. Your Google refresh token is sealed with AES-256-GCM and bound to your organization, and only the Proofsource services that sync your data can unseal it, at the moment they call Google. Imported data is stored encrypted at rest in our database on AWS, isolated per organization by database row-level security, and visible only to members of your workspace. We keep only the tokens and the data listed above, never your Google password.
Sharing: we don't sell Google user data, use it for advertising, or use it to develop, improve or train generalized AI or machine-learning models. We transfer it only as needed to run the features above: to our hosting provider, and, when a feature you use needs it, such as drafting a fix from a file you picked, an agent step that reads Google Analytics, or a reply that offers your free times, to one of three AI services that don't use it to train models: Anthropic's API, OpenAI's API (with storage turned off), or Anthropic's Claude models on Amazon Bedrock. We never send Google user data, or anything derived from it, to any other AI model, such as DeepSeek, Grok, Llama, Gemini or Perplexity. Beyond that we share it only to comply with the law, or as part of a merger or acquisition with notice to you. Proofsource staff don't read your Google data unless you ask us to for support, it's needed for security, or the law requires it.
Disconnecting and deletion: you can disconnect any Google service at any time on the Integrations page. When you disconnect, we delete our stored copy of the token and stop syncing. If no other connection of yours uses that Google account, we also ask Google to revoke Proofsource's access. Your other connections keep working. You can also remove Proofsource's access at myaccount.google.com/permissions. Data already imported stays in your workspace until you delete it or your account, or ask support@proofsource.co to delete it. We then delete your Google tokens and imported data.
Proofsource's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Microsoft
- Bing Webmaster Tools (scope webmaster.manage): we read the list of sites you have added, so you can pick the one for your brand, and that site's Bing search traffic: clicks, impressions, average position, the queries and pages behind them, and each page's status. After a fix you approved goes live, we tell Bing which page was added or changed and resubmit your sitemap.
- Microsoft Copilot citations: Bing reports these only in its AI Performance report, which has no API yet. When you upload that report's files, we store the citation counts, cited pages and grounding queries they contain.
- SharePoint (scope Sites.Read.All, read-only): we read the pages and documents of the SharePoint sites you pick into a knowledge base, so drafted fixes use your real facts.
Microsoft offers no way for us to revoke access, so disconnecting deletes our token. To remove Proofsource's access in your Microsoft account too, use account.live.com/consent/Manage or, for a work account, myapps.microsoft.com.
Cloudflare
We read your zones, so you can pick your brand's, the zone's traffic analytics to count AI crawler visits, and its DNS records and Pages deployments, to see where your site is served from and when a fix is live. After you approve a fix, we can serve the fix page from Cloudflare's edge with a Worker and its route, add a rule that lets verified AI crawlers in, clear the cache for the fix page's address, and set up a log job that records crawler visits to that page. Undo removes only what we added.
GitHub
With a token or our GitHub app limited to the repositories you choose, we read the site's files, build checks and deployments. After you approve a fix, we commit it on its own branch and open a pull request. We merge it only after your OK, and your developers can review, change or close it first.
Slack
We list your channels so you can pick one, then post your digest, alerts, and the answers and reports your team asks for. We read only messages that mention our app, the /proofsource command, direct messages to our app, and a thread or channel someone asks us to read or import into a knowledge base. We read members' names and email addresses only to match a Slack person to a member of your workspace. To remove our app in Slack too, use your workspace's Manage apps page.
Linear
We list your teams so you can pick one. When you send a fix to Linear, we create one issue for it, comment the fix's proof on that issue, and move that issue when the fix is live. We don't change your other issues.
Atlassian Confluence
Read-only. We list your spaces and read the pages of the spaces you pick into a knowledge base, so drafted fixes use your real facts. To remove our access in Atlassian too, use your Atlassian account's Connected apps page.
Website builders and content systems
WordPress, Webflow, Wix, HubSpot, Shopify, Notion-built sites, Framer, Ghost, Contentful, Sanity, Drupal, Strapi, Storyblok, GitBook and Hashnode. You connect with a key, an app password or the provider's own consent screen. After you approve a fix, we publish it as a page, post or entry on your site, check that it is live, and can undo it. We change and remove only what we created.
- WordPress: we connect with an application password you create. Our optional crawler log plugin sends us only AI crawler visits to your site (time, IP address, user agent, page and host), and nothing until you save a key in it.
- Webflow: we also read your sites, collections, pages, images, products, form sign-ups and site activity, to count visits from AI and prove when a fix page went live. For a page we published, we set its SEO title, description and structured data and add it to your sitemap.
- HubSpot: we also read which forms visitors to a fix page fill in, how many contacts those forms bring, and the page's views and traffic sources. We don't copy your contact records.
- Shopify: we also read your products. After you approve a fix, we can update the product copy fields the fix names, add a menu link to a fix page, and create FAQ and comparison entries. We never ask for your customers or orders.
- Wix: we publish each fix as a post on your Wix blog.
Zendesk, Intercom
After you approve a fix, we publish it as an article in your help center, check that it is live, and can undo it. We don't read your tickets, conversations or customers.
Meta (Facebook, Instagram)
We list the Facebook Pages you manage, so you can pick your brand's, and read that Page's name, rating and review count and the Instagram business account linked to it. After you approve a post and turn on its auto-publish, we publish it to your Page or your Instagram account. We never edit or delete your other posts, and we don't read your followers or messages. To remove our access in Meta too, use Business Integrations in your Facebook settings.
You can connect your own LinkedIn profile and the LinkedIn pages you administer. We read your name, photo and member ID, the pages you administer, and, for posts we published for you, their statistics (such as impressions, reactions, comments and link clicks) and the comments on them. After you approve, or on their own if you turn on automatic posting for your profile or a page, we publish posts, reply to comments and react from that profile or page, create page events, and can delete what we published. We never edit or delete your other posts, and we never read your connections or messages.
If you connect a LinkedIn ad account, we can boost posts you approve and read their results, bring leads from your own LinkedIn lead forms into your account, and send LinkedIn the conversion events you choose so it can measure your campaigns. If you live in the European Economic Area and agree on LinkedIn's consent screen, we can read your past LinkedIn posts to match your writing style. We use LinkedIn data only to run these features for you, never for sales prospecting, advertising audiences or recruiting, and we don't sell it, export it or combine it with other data about people. We keep the IDs of what we published, your name and photo, and encrypted access tokens; other members' comments and activity are deleted within 48 hours. To remove our access in LinkedIn too, use Permitted services under Data privacy in your LinkedIn settings.
X
We read your account's name and ID, so you can see which account is connected. After you approve a post or thread and turn on its auto-publish, we publish it from that account. We don't read timelines or messages, and we don't follow, like or repost.
From your brand's own Reddit account, we read the thread and the subreddit's rules, then post the one reply you approved, word for word. Every reply says who you work for. We then read the reply's score, replies and status.
Amazon, eBay, Shopee, Lazada
Read-only. From your own seller account, we read only your seller rating and number of ratings: Amazon's seller feedback report, eBay's feedback score, Shopee's product ratings and Lazada's seller rating. We store only the rating and the count. We don't read orders, buyers, listings or prices. To remove our access there too, use Manage your apps in Amazon Seller Central, or the authorized apps page in eBay, Shopee or Lazada.
Amazon S3: if you grant us a role on a bucket you name, we read the access logs in it to count AI crawler visits. Delete the role in your AWS account to remove our access.
Trustpilot, G2, App Store Connect, Google Play
With a key you create, we read your rating, review count and reviews, and for apps, your app's reviews. Only Trustpilot can also write: when you approve a review invitation, we send Trustpilot the name and email address of each customer you chose, and Trustpilot sends its own invitation; when you approve a reply to a Trustpilot review, we post that exact reply.
Getty Images, Gamma, v0
With your own key, we search images you can license, or create the deck or page layout you ask for in your own account. We send each one only the fix content that task needs.
Who we share it with
We don't sell personal data, and we don't share it with data brokers. We share it only with service providers that help us run Proofsource, each limited to what its job needs:
- Hosting and network: Amazon Web Services and Cloudflare.
- AI engines and models: OpenAI, Anthropic, Perplexity, Google Gemini, xAI and TypeSafe.
- Search and web data: Google Maps Platform, YouTube, DataForSEO, Firecrawl, TinyFish and Xpoz.
- Email, notifications and messages: Fast Mail Tracker, Resend, Knock, Slack and Pagerless.
- Payments: Stripe and Dodo Payments.
- Analytics: PostHog and Meta.
- Services you connect, such as Google, and ChatGPT or Claude when you connect them (see AI assistants you connect below).
Our merchant of record, Stripe (purchases show as "Sold through Link") or Dodo Payments, bills you and handles sales tax, VAT or GST. What each provider does, the data it receives and where it processes it are listed at proofsource.co/subprocessors. Questions go to privacy@proofsource.co.
We may also disclose personal data when the law or a valid legal process requires it, to protect the rights, property or safety of our users, the public or us, or as part of a merger, acquisition or sale of assets.
Place names and locations in the location search come from GeoNames (geonames.org), used under the Creative Commons Attribution 4.0 license. We keep our own copy, so what you type is never sent to GeoNames.
AI assistants you connect
You can connect Proofsource to an AI assistant, such as ChatGPT by OpenAI or Claude by Anthropic, so the assistant can call Proofsource tools for you. When you do:
- Proofsource receives each tool call the assistant makes: the tool's name and its arguments, such as a brand, a domain or a question, with a token that identifies your account and workspace. We do not receive your chat history or the rest of your conversation beyond those tool call arguments.
- The results of the tools you request, such as visibility figures, competitor names, cited pages and answer excerpts from your workspace, are sent to OpenAI or Anthropic so the assistant can show them to you. From then on they are handled under that provider's own terms and privacy policy, not this one.
- The assistant can read only the workspace you chose when you connected it, and act only with your role in that workspace.
- You can disconnect at any time in the app under Settings, then AI agents, then Connected apps. We then revoke the assistant's access, and its next tool call is refused. Removing Proofsource in the assistant's own settings stops it on the assistant's side.
Our iPhone, Android and Shopify apps
Everything in this policy applies to our apps too. This section adds what is specific to each app.
- iPhone and Android: you sign in with a code we email you. The apps use the same account and workspace as app.proofsource.co, so they collect the same account details and workspace content described above.
- Alerts on your phone: if you turn on notifications, your phone gives us a push token. We store it with your account and use it only to send the alerts you chose. Apple (Apple Push Notification service) or Google (Firebase Cloud Messaging) delivers each alert. You can turn notifications off in the app or in your phone's settings at any time.
- The phone apps contain no advertising code. They don't track you across other companies' apps or websites, and they don't read your contacts, photos or location.
- Usage data in the phone apps is off until you turn it on. If you choose Share, the app sends PostHog the screens you open, a few named actions (such as running a scan or sharing a report) and crash reports, linked to your Proofsource user ID, never your email. There is no session recording. You can turn it off any time in Account, which stops sending immediately.
- Shopify: when you install the app, Shopify tells us your store's domain and name and the email of the staff member who installed it, which we use to create your Proofsource account (you can sign in at app.proofsource.co with a code sent to it). The app also reads your product catalog, such as product titles, descriptions and links. We use it to build buyer questions about your products and show which ones AI engines name. The app changes your store only after you approve a fix: it can publish a blog article, update the product copy the fix names, add a menu link and create FAQ and comparison entries, and undo removes only what it added.
- We don't ask Shopify for access to your customers or orders, so we receive no data about your shoppers.
- If you choose a paid plan in the Shopify app, Shopify bills you. We receive your plan status from Shopify, never your payment details.
- When you uninstall the Shopify app, we stop reading your store. Shopify then asks us to delete your store's data, and we delete it within 30 days.
Our Chrome extension
Everything in this policy applies to the Proofsource extension for Chrome too. This section adds what is specific to it.
- Sign-in: you sign in on Proofsource's own page with an email code or Google. The extension keeps its sign-in on your computer and never asks for a password.
- The page you are on: the extension sends us a page's address only when you open it on that page or choose Track this page. It takes a screenshot of the visible tab only when you press Save screenshot, and keeps it in your workspace as evidence for your brand.
- Sites you allow: the extension adds its buttons only on the sites you turn on, one at a time. It reads those pages in your browser to place its buttons, and fills a form only when you click. It never posts or submits anything for you.
- The dot: if you turn it on, the extension checks whether a page matters to your brand by sending a short hash prefix of its address, never the address itself.
- Once a day the extension tells us its version, whether the dot is on and which sites you allowed. It never sends your browsing history.
- We use data from the extension only to run its features. We don't sell it, use it for advertising, or use it to train AI models. Removing the extension stops all of this. What you already saved stays in your workspace until you delete it.
Deleting your account
- In the Proofsource app for iPhone or Android: open Account, tap Delete account and confirm. This deletes your account and the data tied to it, and cancels any paid plan.
- Anywhere else: email privacy@proofsource.co from your account's email address and ask us to delete your account. We confirm by email when it is done.
- Shopify stores: uninstall the app from your Shopify admin. We delete your store's data within 30 days.
- Deleted data leaves our database backups within 35 days, as each backup expires.
International transfers
We store and process data in the United States, on Amazon Web Services. Our team and some providers access or process data from outside the United States: Amazon Bedrock may run an AI request in another AWS region, Cloudflare handles traffic at the location nearest the visitor, Google Gemini, Google Maps Platform and YouTube run in Google data centers worldwide, DataForSEO works from Estonia and Ukraine, Xpoz does not publish where it works and its terms follow Israeli law, Pagerless runs on Cloudflare's worldwide network, and Dodo Payments works from the United States and other countries. Each provider's location is listed at proofsource.co/subprocessors. Where the GDPR or UK GDPR applies, we protect transfers with Standard Contractual Clauses or another lawful mechanism, and every transfer follows the data protection law of the country it leaves.
How long we keep it
We keep data only as long as needed to provide the service, meet legal obligations and resolve disputes:
- Captured AI answers and your workspace content: until you ask us to delete them.
- Assistant chats: until you delete them; then removed 90 days later.
- Email delivery logs: 6 months.
- Screenshots of AI answers and cited pages: 15 days.
- Booking link visits (that an agency's booking link was opened, from which kind of link, the rough city and the device type): 90 days. We never store the visitor's IP address.
- Service and security logs: up to 12 months.
- Account data: kept until you ask us to delete it, even after a free trial or a paid plan ends. A workspace owner can delete it in the app under Settings, then Data and privacy, or email privacy@proofsource.co.
- Backups: deleted data leaves our database backups within 35 days, as each backup expires.
Asking us to delete your account erases it within 30 days.
You can ask us to delete your data at any time by emailing privacy@proofsource.co.
Security
We protect data with encryption in transit and at rest, access controls, and isolation between customers. No system is perfectly secure. If a breach affects your personal data, we will tell you and the relevant authorities as the law requires. To report a vulnerability, email support@proofsource.co.
Cookies and analytics
- The app (app.proofsource.co) uses cookies it needs to work, such as keeping you signed in and remembering your active workspace. It also runs the Meta Pixel described below, on the same terms as our website.
- Our website (proofsource.co) uses PostHog for analytics: page views, a few named events (opening or sending the demo form) and session replays. Until it may set cookies, it sends page views and named events only, without storing identifiers in your browser.
- Each event reaches PostHog through our own domain with your IP address and browser type, which PostHog uses for approximate location and to count visits without cookies.
- PostHog sets a cookie to recognize a returning browser and records session replays of your visit. If you are in the EU, the EEA, the UK or Switzerland, it does this only after you click Accept. Elsewhere it does this unless you click No thanks or your browser sends Global Privacy Control or Do Not Track. Anything typed into a form field is masked in replays, and the contact form is not recorded. We do not use heatmaps or autocapture. The demo form event carries the team size you pick, never your name, email or message.
- If you are in the EU, the EEA, the UK or Switzerland, the Meta Pixel loads only after you click Accept. Elsewhere it loads unless you click No thanks or your browser sends Global Privacy Control or Do Not Track. It sets the _fbp and _fbc cookies, kept for 90 days, so we can measure which of our Meta ads lead to sign-ups.
- Booking links (meet.proofsource.site and an agency's own booking address) set a ps_bv cookie for 1 year to count one visit per browser for the agency that shared the link. It holds only a random id.
- A ps_consent cookie on proofsource.co and its subdomains remembers your choice for 1 year, so the app follows it too.
- When you sign up, start a trial or make your first payment, our server also reports it to Meta with your hashed email address, user ID, country, IP address, browser type and Meta cookie IDs (and, for a payment, its amount and currency), so ad results are still counted when a browser blocks the Pixel. Meta is listed at proofsource.co/subprocessors.
- These server reports follow the same rules as the Meta Pixel, and choosing No in Cookie settings stops both.
- Our emails measure delivery, opens and link clicks through our email provider, Resend. We record those, and what you do next in the app, in PostHog against your account, with your name, email and plan on your PostHog profile, so we can tell which emails help and send fewer that don't. Deleting your account deletes that profile.
- You can turn off tips and alerts on the email preferences page linked at the bottom of every email. Sign-in codes, billing and security emails always send.
- If your browser sends Do Not Track or Global Privacy Control, we treat it as no.
- You can change your choice any time through Cookie settings at the bottom of every page.
- Apart from Meta, as described above, we don't use advertising cookies or let third parties track you across other sites through our website or app.
Your rights
Wherever you are, you can ask us to access, correct, update, export or delete your personal data, and you can withdraw consent you have given. Some laws give you more specific rights:
- European Union, EEA and United Kingdom: the rights of access, rectification, erasure, restriction, data portability and objection, and the right to complain to your local data protection authority.
- Other countries: wherever your local law gives you further rights, such as grievance redressal or naming someone to act for you, you can use them by writing to us, and you can complain to your local data protection authority if we do not resolve your request.
- California: the right to know what personal information we collect, use and disclose, and to delete and correct it. We don't sell personal information. Sending Meta the ad measurement data described under Cookies and analytics may count as sharing for cross-context behavioral advertising; choosing No in Cookie settings or sending Global Privacy Control opts you out. We won't treat you differently for using your rights.
To use any of these rights, email privacy@proofsource.co. We may need to confirm your identity first. We reply within the time required by applicable law. If your request concerns a workspace your company controls, we may refer it to your workspace owner.
When your company is in charge
For data that customers put into Proofsource, the customer decides what goes in and we process it on their behalf as a processor. Our Terms of Service and any data processing agreement with the customer govern it. To request a data processing agreement, email privacy@proofsource.co.
Children
Proofsource is for businesses. It is not meant for anyone under 18, and we don't knowingly collect personal data from children. If you believe a child has given us personal data, email us and we will delete it.
Changes to this policy
We will post any change on this page and update the effective date. If a change is material, we will tell you by email or in the app.
Contact and grievance officer
- Privacy questions and requests: privacy@proofsource.co
- Grievance Officer, Grovio Labs, Inc.: grievance@proofsource.co. We acknowledge and resolve grievances within the time the law requires.
- Everything else: support@proofsource.co
Proofsource is a product of Grovio Labs, Inc., a Delaware corporation.
Registered office: 131 Continental Dr, Suite 305, Newark, DE 19713, United States