← Back to homepage

Privacy Policy

Last updated: October 28, 2026

The Basics & Key Definitions

OverlayQA is a visual QA tool for web product teams. It ships as a Chrome extension and a companion web dashboard at overlayqa.com. When you use a feature (capturing a bug, running an accessibility audit, or comparing a live page to a Figma frame), OverlayQA turns that interaction into a structured issue report and stores it in your account.

"Service" means the OverlayQA Chrome extension, the dashboard at overlayqa.com, and the API at api.overlayqa.com. "We", "us", and "our" mean OverlayQA. "You" means the person using the Service.

This policy explains what information we collect, how we use it, who we share it with, and the rights you have over it. OverlayQA's use and transfer to any other app of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

What Information We Collect and How We Use It

1. Your Account Details

When you create an OverlayQA account, we collect your email address, password, and name (managed by our authentication provider, Clerk). Passwords are hashed by Clerk before storage and are never stored in plaintext or accessible to OverlayQA staff. If you sign in via Google, no password is collected. A signed session token (JWT, HMAC-SHA256, 30-day TTL) is stored locally in chrome.storage.local to keep you logged in. If you connect Figma, Jira, Linear, Notion, Asana, Trello, ClickUp, GitHub, Basecamp, monday.com, or Slack, we store the OAuth access tokens those services issue, encrypted at rest using AES-256-GCM.

We use this information to identify your account, associate your issues with you, keep you signed in across browser restarts, and send you product-related communications.

2. Data from the OverlayQA Chrome Extension

The Chrome extension collects data only when you explicitly trigger a feature such as capture, accessibility audit, Figma comparison, or AI analysis. Nothing in this section is collected passively or in the background.

When you initiate a feature, the extension captures:

• Screenshots: a visible screenshot of the current browser tab, produced via the Chrome tabs.captureVisibleTab API and uploaded to our server.
• Element selectors and metadata: the HTML tag name, CSS selector, class names, parent selector, ARIA role, alt text, and bounding rectangle of the element you pin or that an accessibility audit flags.
• Element text content: up to 200 characters of the visible innerText of elements you actively pin for bug capture. We do not capture text from form inputs, password fields, or content that is not visibly rendered.
• Element HTML snippets: up to 200 characters of outerHTML for elements associated with reported issues or accessibility violations.
• Computed CSS properties: for pinned elements we extract computed style values including color, background-color, font-family, font-size, font-weight, line-height, letter-spacing, padding, margin, gap, border-radius, border styles, display, flex properties, width, and height.
• Design system token extraction: when you initiate an AI design analysis, visual comparison, or Design Token Audit, the extension samples up to 200 visible elements from the current page and extracts their computed CSS properties (colors, typography, spacing, borders, shadows) to detect design system patterns. The Design Token Audit is an AI-powered feature: the extracted token inventory (unique CSS values, their frequencies, and CSS custom property declarations from :root stylesheets), client-detected inconsistency findings (near-duplicate colors, orphan font sizes, off-scale spacing) with element selectors and bounding rectangles, optional Figma design tokens (if a Figma file is connected), the page URL, and viewport dimensions are forwarded to OpenAI's GPT-4o API for enrichment analysis. Refinement includes non-ignored measured findings that already have a saved issue, so filing alone does not remove them from the page assessment. Saved issue discussions and assignee information are not included. No form inputs, passwords, or hidden content are captured during this sampling.
• axe-core accessibility results (AI-enriched): the accessibility audit is an AI-powered feature. axe-core scans your page's DOM locally in your browser and produces a list of WCAG rule violations. For each rule that produced violations, the extension sends our server the rule ID, impact level, WCAG criterion, description, help text, help URL, tags, and the count of affected nodes. Along with this, the extension sends a small DOM metadata bundle for flagged elements (computed color, background-color, font-size, font-weight, line-height, display, and bounding rectangles), the total element count on the page, a screenshot of the current browser tab, and, if you have linked a Figma frame, the Figma frame image. Our server forwards this bundle to OpenAI's GPT-4o API, which visually analyzes the page to identify WCAG violations that automated tools cannot detect (non-text contrast, touch target size, clickable-but-not-focusable elements, hover/focus dismissal issues, ARIA composite pattern gaps, color-only information conveyance). The full page DOM is never transmitted.
• Figma frame images: when you start a design comparison, the selected frame's PNG image is fetched from Figma's API, converted to base64, and sent to our server. The frame image is stored on Cloudflare R2 so the resulting issue can be viewed later.
• Comparison detail and measurement evidence: AI Visual Comparison may send enlarged regions of the same submitted reference image and page screenshot, matching labels, and generated finding text to OpenAI to inspect typography, spacing and the evidence for each finding. For numeric measurements, OverlayQA also processes captured element geometry, typography, padding and margin values, static visible text from up to 2,000 page elements, and the selected Figma frame's structure and version. This additional measurement bundle is processed by OverlayQA and is not forwarded to OpenAI. Editable field text and hidden content are excluded from that bundle. Local Auto Review findings also retain their captured typography, padding and margin when saved or shared; that separate styling bundle is not sent to OpenAI. Screenshots and measurement evidence may be retained with an analysis run, including findings saved for follow-up reviews. Saved comparison issues, shared reports and exports may include captured CSS values, measurements, source details and the full reference and live context images.
• Spacing measurements in visual comparisons: when you start AI Visual Comparison, we collect positions, padding, border widths, parent relationships, and static visible text from up to 2,000 page elements (up to 500 characters per text element), together with the selected Figma frame's structure and version. Editable field text and hidden content are excluded from this measurement data. Our server uses it to match spacing edges; this additional measurement bundle is not forwarded to OpenAI. Comparison images and measured gap evidence can be retained with the comparison and issues you create. Numeric measurements and their source details accompany an issue when you choose to export it.
• Browser and device context: when you create an issue, the extension captures the following from your browsing session (parsed from your browser's User-Agent Client Hints API or the navigator.userAgent string) and attaches it to the issue as reproducibility context for the developer fixing the bug:
  • Browser name (for example Chrome, Edge, Firefox, Safari)
  • Browser version
  • Operating system and version
  • Viewport width and height
  • Screen width and height
  • Device pixel ratio
  This information is visible to anyone you share the issue with. We do not use it for tracking, profiling, or fingerprinting.
• Page URL and title: recorded at the moment you actively use a feature such as creating an issue, running an accessibility scan, or starting a design comparison, and stored alongside the issue you create.
• Issue comments and @mentions: when you write a comment on an OverlayQA issue, the extension sends the comment text, the IDs of any team members you @mention, and a timestamp to our server. Comments are visible to all members of the team that owns the issue and can optionally be synced to the linked Figma comment thread when Figma is connected. You can edit or delete your own comments at any time. Posting a normal issue comment does not itself send it to an AI provider. A connected AI app can read comments you can access when you authorize it, as explained below.
• Fix Verification (AI-powered): when you mark an issue as resolved and re-capture it, the extension uploads a new screenshot of the page (or element) and our server sends the following to OpenAI's GPT-5.5 API so it can compare the before and after states: the original screenshot URL, the current screenshot URL (both stored on Cloudflare R2), the issue title, issue description, element selector, and severity. When you verify a fix from the dashboard on a publicly reachable page, or through a connected AI app (MCP), the extension is not involved: our server opens that page itself at the issue's original viewport size, takes the new screenshots there, and stores them on Cloudflare R2 the same way. For accessibility issue verifications, we also send the WCAG criterion, the axe-core rule ID, and the boolean results of re-running axe-core (whether the rule still flags the page and whether it still flags the original selector). If the element is no longer found on the page, or the viewport differs from the original capture, a single sentence describing that condition is appended to the prompt. GPT-5.5 returns a pass / fail / inconclusive verdict with a short natural-language explanation, which is stored alongside the issue.
• In-product help chat (AI-powered): the OverlayQA dashboard and browser extension include an AI help assistant that answers questions about OverlayQA. When you send a message, your typed chat messages and the assistant's prior replies in that conversation are forwarded to OpenAI's GPT-4o-mini API to generate the answer. No account data, screenshots, page content, or DOM data is included. The help-chat integration does not automatically attach your name, email, or account credentials to its requests. Conversation transcripts are stored on our servers (associated with your account so our team can review product questions and reported problems) and are automatically deleted after 90 days.
• Auto Review (AI-powered): Auto Review is a page scanner that runs when you start it or on a schedule you enable. A deterministic scan of the page's structure and computed styles runs locally in the extension, or on our servers when you start it from a team review link or a connected AI app, where our server loads the page under review in a headless browser, to detect UI-quality issues (design inconsistencies, missing interactive states, form problems, responsive gaps, dead UI elements, and leftover placeholder text). When you run it, our server sends OpenAI's GPT-6.1 Sol API a downscaled full-page screenshot and summaries of those findings (each finding's check type, category, title, severity, and element selector, up to 100), the page URL, viewport dimensions, and counts of interactive and form elements, and GPT-6.1 Sol reviews the screenshot to confirm and add findings. The request can also include a sampled inventory of up to 60 visible elements: selectors, tags, roles, states, visible text up to 120 characters per element, positions, sizes, and computed typography, spacing, corner, shadow and color values. This inventory excludes form values, hidden text and raw HTML.
• Client review comments (AI-classified): when a client or stakeholder leaves a comment on a review link you shared, that comment becomes an issue in your project. To set the issue's type (Bug, Mismatch, Improvement or General) and severity automatically, our server forwards the comment text, the screenshot of the element the reviewer pinned, that element's selector, tag, class names and alt text, and the page URL to OpenAI's GPT-4o API. Only the type and severity come back and are stored on the issue; your team can change either at any time, and an edit your team makes is never overwritten. The reviewer's name and email are never sent to OpenAI. This runs on the review page served by our API, not in the browser extension.
• Captured element type and severity (AI-classified): when you capture an element with the extension, our server forwards that element's screenshot, its selector, tag, class names and alt text, and the page URL to OpenAI's GPT-4o API to pre-fill the new issue's type (Bug, Mismatch, Improvement or General) and severity. Nothing you type is sent. Only the type and severity come back, and they are pre-filled only while you have not set either yourself; you can change both at any time.
• Screen recordings: when you or a client use the Record tool on a team review or client link, or you use it on the extension's capture toolbar while signed in (Chrome and Edge on a computer), the browser records the page you are reviewing only, after you choose Share in Chrome's dialog, with no sound, for up to 30 seconds. Nothing is recorded until you press Record. The recording is stored as a file on the issue or comment, like a screenshot, is visible to the same people, and travels with it to any tracker you export to. It is not sent to any AI model.

We use this information to generate the issue report, draft AI-powered title and severity suggestions, compare your Figma design against the live page for visual comparison, and run accessibility audits. Issue reports can be exported to Jira, Linear, Notion, Asana, Trello, ClickUp, GitHub Issues, Basecamp, or monday.com when you choose to do so.

The extension also maintains a local LRU index in IndexedDB of pages where you have used OverlayQA features (maximum 200 entries, 50 per hostname). Each entry contains the page URL, title, visit timestamp, and a compressed 200×200 JPEG thumbnail of the page captured at the time you used the feature. This index is stored only on your device and is never transmitted to our servers. It is removed when you uninstall the extension or clear browser data.

Passive browsing history. We do not track, record, or transmit a list of every page you visit. Page URLs and titles are only captured at the moment you actively use a feature such as creating an issue, running an accessibility scan, or starting a design comparison.

Passive page content. The extension does not read, log, store, or transmit the content of pages you visit unless you actively use a feature (creating an issue, running an audit, or starting a comparison). When you are signed in, an authenticated Server-Sent Events connection to api.overlayqa.com is maintained to deliver real-time notifications and Figma comment updates to your browser; this connection only carries notification payloads from our server to your browser and does not transmit page content, browsing history, or user activity from your browser back to us.

3. Usage Data (How You Use Our Service)

We collect basic usage data to understand how the Service is used and to improve it:

• Your IP address, transmitted as part of standard HTTPS requests to api.overlayqa.com. Your IP address is stored in our database solely for rate-limit tracking on the free design comparison feature (to prevent abuse of the unauthenticated endpoint). PostHog, our product analytics sub-processor, also receives your IP address and derives approximate geolocation (city, country, region, timezone) for each analytics event (see the PostHog entry under Sub-processors below). IP addresses may also appear in server access logs maintained by our hosting provider (Railway) for security and abuse prevention.
• Product analytics events such as sidebar opened, issue created, audit started, and screenshot captured, sent to PostHog. Event properties include feature usage metadata such as issue severity, issue type, and the page URL of the page you are inspecting when you initiate an accessibility scan or design comparison. These events do not contain page content or screenshots.
• MCP server (connected AI apps and coding tools): when you use an AI app or coding tool connected to OverlayQA, tool calls record product analytics in PostHog: your account, the tool called and its outcome, related project and issue IDs, counts and scores, and the URL a scan runs on. The local MCP client also supplies the name and version of the coding tool and a one-sentence purpose for the call. We cap that sentence and strip email addresses and credential-like strings before storing it. The hosted MCP endpoint records its transport name and version and does not request a purpose sentence. This analytics event never records your conversation with the coding tool, your code, or the tool's replies. Scans, issues and comments you create through MCP are stored like other work in your account.

4. Info from Third-Party Logins

You can create an OverlayQA account using Google. When you sign up or log in to your OverlayQA account using Google, we store your profile information (name, email address, and profile picture), as authorized by you.

How We Use Your Data

We use the information described above to:

• Operate the OverlayQA Service: create issue reports, run accessibility audits, and compare designs against live pages.
• Generate AI-powered issue suggestions, visual design comparisons, and accessibility remediation guidance by forwarding the relevant page data to OpenAI. These AI features are core functionality of the product, not optional.
• Authenticate you and keep you signed in across browser restarts.
• Sync issues to external trackers (Jira, Linear, Notion, Asana, Trello, ClickUp, GitHub Issues, Basecamp, or monday.com) when you connect them and choose to export.
• Send you account-related and service-related communications.
• Analyze and improve the Service through aggregate usage data.
• Detect and prevent abuse, fraud, and security incidents.

When We Share Your Information

We do not sell, rent, or trade your personal data. We share data with the sub-processors listed under "Third-Party Services We Use" below to operate the Service, and with external services and AI apps that you authorize, as described in this section.

When you create an issue, run an accessibility audit, start a Figma design comparison, run a Design Token Audit, verify a fix, or run Auto Review, the following data is forwarded to OpenAI's GPT models (GPT-4o; the Figma design comparison and Auto Review use GPT-6.1 Sol, and fix verification uses GPT-5.5): page screenshots, Figma frame images or uploaded reference images (when you compare against a design), element selectors and metadata, computed CSS for pinned elements, element text content (innerText, up to 200 characters), page URL, page title, viewport dimensions, axe-core accessibility violation results, design system token data sampled from up to 200 page elements, and (for Design Token Audits) the token inventory (extracted CSS values, frequencies, CSS custom property declarations), client-detected findings with element selectors and bounding rectangles, and optional Figma design tokens. For Fix Verification, we additionally forward the original screenshot URL, the current (re-captured) screenshot URL, the issue title, issue description, element selector, and severity; for accessibility-issue verifications, we also include the WCAG criterion, the axe-core rule ID, and the boolean results of re-running axe-core (whether the rule still flags the page and whether it still flags the original selector), plus an optional single-sentence note when the element is no longer present or the viewport differs from the original capture. For Auto Review, we forward a downscaled full-page screenshot, summaries of the locally-detected findings (each finding's check type, category, title, severity, and element selector, up to 100), the page URL, viewport dimensions, counts of interactive and form elements, and a sampled inventory of up to 60 visible page elements (each element's selector, tag, role, state, visible text up to 120 characters, position and size, and its computed font, spacing, corner, shadow and color values; never form values, input attributes, hidden text or raw HTML) to OpenAI's GPT-6.1 Sol model; Auto Review's rule-based scan runs in the extension for browser reviews and on our servers for team reviews, connected AI apps and scheduled reviews. When a client or stakeholder leaves a comment on a review link you shared, we forward the comment text, the pinned element's screenshot, its selector, tag, class names and alt text, and the page URL to OpenAI's GPT-4o API to set the resulting issue's type and severity; the reviewer's name and email are never included. When you capture an element with the extension, we forward that element's screenshot, its selector, tag, class names and alt text, and the page URL to OpenAI's GPT-4o API to pre-fill the new issue's type and severity; nothing you type is sent, and you can change both at any time. When you use OverlayQA's in-product help chat (in the dashboard or the browser extension), your typed chat messages and the assistant's prior replies in that conversation are forwarded to OpenAI's GPT-4o-mini API; transcripts are stored on our servers and automatically deleted after 90 days. The help-chat integration does not automatically attach your name, email, or account credentials to its requests. Per our agreement with OpenAI, data sent through their API is not used to train their models.

When you connect Figma, Jira, Linear, Notion, Asana, Trello, ClickUp, GitHub, Basecamp, monday.com, or Slack, the relevant issue or design data is sent to those services via their APIs using your OAuth credentials. For GitHub, issues are created only in repositories you have given the OverlayQA GitHub App access to. This only happens when you initiate the connection and choose to export.

Connected AI apps (MCP). When you connect an AI app such as ChatGPT, or an AI coding tool, you authorize it to request OverlayQA data and actions. Tool responses can include project and issue names, descriptions, status, tags, assignees, teammate names and email addresses, comments and their authors, attachment contents, screenshot links, captured page and element evidence, and scan findings. Only data available to your account through the requested tool is returned. A hosted connection is restricted to the workspace and permissions you approve; existing project access rules and account limits still apply. Write permission allows the app to change work and post comments on your behalf, including client-visible comments and notifications when requested. Permission to run scans lets the app start scans of public pages you name, using your account's scan allowance; our server loads each page in a headless browser. When such a scan uses AI (accessibility and contrast analysis, Auto Review, or AI Visual Comparison), the data described above is forwarded to OpenAI. A comparison's design reference can be a frame from your connected Figma account, a design saved to your project, or an image the app uploads.

The connected AI app receives these responses and processes them under its own terms, privacy policy and your account settings. For example, ChatGPT's handling of connector data is separate from our use of OpenAI's API for OverlayQA's built-in analysis features. Review the AI provider's terms before sharing workspace data. OverlayQA does not request your full chat history through this connection. You can revoke a hosted connection on the Connected AI apps page. Disconnecting stops future access; it does not remove data already received by the AI app or undo issues and comments it created.

Email previews. When you request an email preview of a captured issue, we send the issue (including the screenshot, page URL, element CSS values, browser metadata, and your typed description) to the email address you specify, via Resend (our transactional email provider). We do not retain the recipient's plaintext email address; we store only a one-way SHA-256 hash of it in a rate-limit ledger so we can enforce per-IP and per-user send limits (the ledger is queried over a 24-hour rolling window). We do not create an OverlayQA account for the recipient of a preview email, and anonymous senders do not get an account created either. Screenshots captured in the anonymous flow are stored on api.overlayqa.com at unguessable URLs; because these URLs are not authenticated, anyone who has the URL can view the screenshot. These captures are not tied to an account, and you can request deletion of an anonymous-flow screenshot at any time by contacting hello@overlayqa.com with the URL.

We also use Resend to send a small number of lifecycle and product emails to signed-in users (for example, a welcome email after sign-up and a short follow-up after install). Resend receives the recipient email address, the email content, and delivery metadata.

How Long We Keep Your Data & How We Protect It

• Account data and issues are retained for as long as your account is active. You can request deletion of your account and all associated data at any time by contacting hello@overlayqa.com.
• Screenshots and Figma frame images are retained for as long as the associated issue exists.
• OAuth tokens for every integration you connect (Figma, Slack and each issue tracker above) are encrypted at rest using AES-256-GCM.
• Hosted MCP connections store the app's registered name and callback URLs, your selected workspace and permissions, timestamps, and one-way hashes of authorization codes and access and refresh credentials. Access credentials expire after one hour; refresh credentials rotate on use, and a connection expires after 30 days unless you connect again. Disconnection revokes access immediately. Expired connection records are removed by cleanup when a client registers; account or workspace deletion also removes its connections. App registration metadata is retained so an app can reconnect. The connected AI provider controls retention of data it has already received.
• Extension session tokens are signed using HMAC-SHA256 and expire automatically after 30 days.
• All data in transit is encrypted via HTTPS/TLS.
• API endpoints are protected by authentication middleware and rate limiting.
• Local browser data is removed when you uninstall the extension or clear browser data.

No method of transmission over the internet is completely secure, and we cannot guarantee absolute security.

Your Rights and How to Exercise Them

You have the right to request access, correction, or deletion of your personal data; to delete your account; to disconnect integrations (which revokes our access to those services); to unsubscribe from communications; and to uninstall the extension at any time (which removes all locally stored data). To exercise any of these rights, contact hello@overlayqa.com.

Your Rights Under GDPR (For Users in the EU/EEA and the UK)

If you are in the EEA or the UK, we process your personal data under the following legal bases: contract performance (to provide the Service you signed up for), consent (for optional integrations and marketing communications), and legitimate interests (product analytics to improve the Service, including the IP address and derived geolocation data that PostHog captures on every analytics event; see the PostHog entry under Sub-processors). You have the right to access, rectify, erase, restrict, object to, and port your personal data.

Your California Privacy Rights (CCPA/CPRA)

If you are a California resident, you have the right to know what personal information we have collected about you, to request deletion, to opt out of the sale of personal information (we do not sell personal information and have no plans to do so), and to non-discrimination for exercising these rights.

Third-Party Services We Use (Our Sub-processors)

We use the following third-party services that collect or process data on our behalf:

• OpenAI: AI analysis of screenshots, element metadata, computed CSS, element text content, page URLs, accessibility audit results, fix-verification comparisons (before-and-after screenshots plus issue context), and client-review comment classification (comment text, pinned-element screenshot and metadata, page URL) via their GPT-4o, GPT-5.5 and GPT-6.1 Sol APIs, plus OverlayQA's in-product help chat (in the dashboard and browser extension; your typed chat messages and the assistant's replies in that conversation) via their GPT-4o-mini API. Core feature of the Chrome extension. Per our agreement with OpenAI, data sent through their API is not used to train their models.
• Clerk: Authentication (including Google sign-in) and user management for the web dashboard.
• Neon: PostgreSQL database hosting in the United States.
• Railway: API server hosting and hosting for our self-managed Rybbit website analytics, including its databases, in the United States.
• Cloudflare: Hosting for uploaded screenshots and Figma frame images (R2) and CDN services.
• Stripe: Payment processing for paid plans. When a team owner subscribes, we send Stripe the owner's email address and an internal team ID. Card and other payment details are entered on Stripe's hosted checkout page and are not stored by OverlayQA. Deleting your account cancels the team's Stripe subscriptions.
• PostHog: Product analytics and session replay. Analytics covers the Chrome extension, the marketing website, the dashboard at app.overlayqa.com, and team and client review pages. Session replay records clicks, scrolling, page content and navigation on our web pages, including the dashboard and team and client review pages; the Chrome extension does not record sessions. For signed-in users, receives user ID and email to link analytics events to your account. PostHog also receives the IP address of analytics events and derives approximate geolocation (city, country, region, timezone) from it, which is stored alongside each event in PostHog's US infrastructure. For AI comparison diagnostics, PostHog receives the initiating account ID, project ID when available, comparison entry point, model, token counts, timing, and success or failure. These diagnostic events do not include comparison screenshots, prompts, completions, or page content.
• Netlify: Marketing website hosting.
• Resend: Transactional email delivery for lifecycle messages (for example, welcome emails after sign-up, install follow-ups) and for the email-preview feature in the extension. Resend receives the recipient email address, the email content (including any captured issue data attached to a preview send), and standard delivery metadata such as bounces and opens.

Each of these services operates under their own privacy policies. We encourage you to review them.

Rybbit website analytics. We run Rybbit on our own Railway deployment to understand visits to the marketing website at overlayqa.com. It collects page visits, referrers, browser and device information, and approximate location derived from the request IP address. Rybbit uses a random visitor identifier in browser local storage. This integration does not enable Rybbit session replay, form-content capture, or account identification.

Other Important Details

Children. OverlayQA is not intended for use by children under the age of 13. We do not knowingly collect personal data from children. If we learn that we have collected data from a child under 13, we will delete it promptly.

Do Not Track. The extension does not alter its data collection in response to DNT signals, but performs no passive background tracking regardless of DNT settings: data is only collected when you actively use a feature.

International transfers. Data may be processed in the United States and other countries where our sub-processors operate. By using OverlayQA, you consent to this transfer. We ensure that all third-party processors maintain appropriate data protection standards.

Cookies and local storage. Our services use cookies and similar technologies (localStorage, chrome.storage) to maintain your session, remember preferences, and collect product analytics (PostHog, which also receives your IP address and derived geolocation; see Sub-processors). You can control cookie behavior through your browser settings. The Chrome extension's local storage can be cleared by removing the extension.

Changes to this policy. We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated revision date. Your continued use of the Service after changes are posted constitutes your acceptance of the revised policy.

Contact Us

If you have questions about this Privacy Policy or wish to exercise your rights, please contact us at hello@overlayqa.com.