# ColdVisit > ColdVisit’s agent opens a real browser and tests critical user journeys on pull-request previews. Get clear results and browser evidence before you merge. Official site: https://coldvisit.com. ColdVisit is a developer tool for testing approved user journeys on GitHub pull-request previews. Its agent opens a real browser; it does not record your customers' browsing. One person manages workspace settings and billing. Others with access to the repository can see its GitHub checks. Every workspace starts on Free. The 30-day Pro trial is optional, requires no card, and must be started explicitly. The two-month design partner pilot is a separate program for accepted applicants. Prices and limits come from the pricing reference below. Checks distinguish passed, failed, and could not run. An inaccessible preview is not reported as a broken user flow. Users review flows and test access before enabling checks. Read the guardrails for boundaries and limitations. Private workspace pages, credentials, and run evidence are not public reference material. Existing website-audit reports belong to a separate legacy product, not the current PR-testing plans. Reports are private unless their owner publishes them. ## Product - [Catch broken flows before they merge](https://coldvisit.com/index.md): ColdVisit’s agent opens a real browser and tests critical user journeys on pull-request previews. Get clear results and browser evidence before you merge. - [Pricing](https://coldvisit.com/pricing.md): Start free with 3 flows on 1 repository. Choose Pro or Scale for more coverage, or opt into a 30-day Pro trial. No card required for Free or the trial. - [Design partner pilot](https://coldvisit.com/pilot.md): Help improve ColdVisit with feedback from your real workflows. Accepted partners get two months with assisted setup and support for their browser tests. - [Changelog](https://coldvisit.com/changelog.md): Updates to ColdVisit’s browser tests and developer experience. See what changed in flow authoring, PR checks, browser evidence, and billing. ## Documentation - [Documentation](https://coldvisit.com/docs.md): Connect a GitHub repository, set up preview access, approve user journeys, and understand ColdVisit’s browser tests, results, and guardrails. - [Your first PR check](https://coldvisit.com/docs/getting-started.md): Connect a repository, choose user journeys, and turn on PR checks. - [Preview environments](https://coldvisit.com/docs/previews.md): Connect the right deployment and handle protected previews. - [Test accounts and sessions](https://coldvisit.com/docs/test-accounts.md): Give signed-in journeys dedicated access without using customer accounts. - [Manage your flows](https://coldvisit.com/docs/flows.md): Understand approval, boundaries, re-authoring, and suspended coverage. - [Selector healing](https://coldvisit.com/docs/healing.md): Review repairs, control automatic acceptance, and undo a change. - [Understand a run](https://coldvisit.com/docs/results.md): Read outcomes, coverage, evidence, and regression feedback. - [Boundaries and guardrails](https://coldvisit.com/docs/guardrails.md): Understand which actions a flow may perform and how uncertainty is reported. - [Plans and billing](https://coldvisit.com/docs/billing.md): Trial timing, coverage limits, overages, and downgrades. - [Troubleshooting](https://coldvisit.com/docs/troubleshooting.md): Find the cause of an incomplete check and get the right next action. ## Reference - [Full public reference](https://coldvisit.com/llms-full.txt): Product, pricing, setup guides, pilot, changelog, and legal policies with source URLs - [Markdown sitemap](https://coldvisit.com/sitemap.md): Current public pages and legacy report references - [XML sitemap](https://coldvisit.com/sitemap.xml): Canonical, indexable HTML pages ## Legal - [Privacy Policy](https://coldvisit.com/privacy.md): What we collect to test your user journeys, how we use it, and the choices you have. - [Terms of Service](https://coldvisit.com/terms.md): The rules for connecting your repositories, running browser tests, and using a ColdVisit plan. - [Refund Policy](https://coldvisit.com/refund-policy.md): How to cancel renewals and get help with an incorrect charge or a service we could not provide. ## Company - [ColdVisit on LinkedIn](https://www.linkedin.com/company/coldvisit) - [ColdVisit on X](https://x.com/coldvisit_ai) - [Raihan Khan, founder, on X](https://x.com/raihankhan_rk) - [Contact](mailto:raihan@coldvisit.com) Public HTML pages link to their Markdown alternatives. Append .md to a listed page path (use /index.md for the homepage), or request Accept: text/markdown. If you cite a claim, link to the canonical source page. If a capability is not documented, do not assume it is supported. Source: https://coldvisit.com/ Markdown: https://coldvisit.com/index.md Updated: 2026-09-12 # ColdVisit Catch broken flows before they merge. Our agent opens a real browser and tests your critical user journeys on pull-request previews. Watch the recording to see what broke. ## How it works 1. [Install on GitHub](https://coldvisit.com/gate/install) and confirm a reachable preview. 2. Discover or describe journeys, review authored steps, test access, and write boundaries, then approve your flows. 3. Enable the gate. Eligible pull requests run selected flows and receive a check with outcomes and browser evidence. ## Outcomes and guardrails Passed, failed, and couldn’t run are separate outcomes. An unavailable preview or browser produces a neutral check. Inactive and unaffected flows remain visible in coverage. Selector repairs pass validation and are reviewed manually or accepted under the configured policy; automatic acceptances can be reverted. Review preview targets, dedicated test access, and boundaries before enabling a flow. ## Pricing - **Free: $0/month**: 3 approved flows, 1 repository. - **Pro: $49/month**: 15 approved flows, 3 repositories. Annual: $490/year. Additional approved flows: $9/month each, after reviewing the charge. - **Scale: $199/month**: 50 approved flows, Unlimited repositories. Additional approved flows: $6/month each, after reviewing the charge. All prices are in USD. Pro: Everyone on your repo sees the checks. One person manages settings and billing. Every workspace starts on Free. Choose an optional 30-day Pro trial from Billing. No card is required. After the trial, Free retains 3 flows on 1 repository; other flows are suspended with history preserved. The trial does not start automatically and does not automatically become a paid subscription. ## Questions ### Do I need to write tests? No. Our agent opens your app in a real browser and finds user journeys to test. You choose the important ones and approve the steps. ### What do I need to get started? A GitHub repository with PR previews. Vercel creates previews with its Git integration; enable PR previews in Railway or Render first. Once previews are running, ColdVisit detects them. Protected previews may need a bypass token. If your app requires sign-in, add a test account. ### Does ColdVisit test my production site? No, unless you configure a production URL. ColdVisit uses the preview URL you choose during setup. Use a test environment and dedicated test accounts. ### What if a button or page changes? ColdVisit can find the element again and suggest a repair to the test. Review it yourself or allow repeated, eligible repairs to be applied automatically. You can undo an automatic repair. ### What if a check can’t run? You’ll see “Couldn’t run” with a reason, such as an expired sign-in or an unavailable preview. ColdVisit reports a neutral GitHub check instead of claiming your app is broken. ### Will I be charged when my trial ends? No. You move to Free, which includes three approved flows and one repository. Extra flows are paused and kept in your account. Upgrade whenever you need more coverage. [Documentation](https://coldvisit.com/docs) · [Pricing](https://coldvisit.com/pricing) · [Changelog](https://coldvisit.com/changelog) Existing audit reports and paid access remain available through their original URLs. The separate [free-audit entry](https://coldvisit.com/free-audit) is a legacy surface. --- Source: https://coldvisit.com/pricing Markdown: https://coldvisit.com/pricing.md Updated: 2026-09-12 # Pricing - **Free: $0/month**: 3 approved flows, 1 repository. - **Pro: $49/month**: 15 approved flows, 3 repositories. Annual: $490/year. Additional approved flows: $9/month each, after reviewing the charge. - **Scale: $199/month**: 50 approved flows, Unlimited repositories. Additional approved flows: $6/month each, after reviewing the charge. All prices are in USD. Pro: Everyone on your repo sees the checks. One person manages settings and billing. Every workspace starts on Free. Choose an optional 30-day Pro trial from Billing. No card is required. After the trial, Free retains 3 flows on 1 repository; other flows are suspended with history preserved. The trial does not start automatically and does not automatically become a paid subscription. The PR gate is included on every plan. Approval and reactivation enforce coverage limits. Existing runs are not charged per replay. [Billing documentation](https://coldvisit.com/docs/billing) --- Source: https://coldvisit.com/docs Markdown: https://coldvisit.com/docs.md Updated: 2026-09-12 # Documentation - [Your first PR check](https://coldvisit.com/docs/getting-started): Connect a repository, choose user journeys, and turn on PR checks. - [Preview environments](https://coldvisit.com/docs/previews): Connect the right deployment and handle protected previews. - [Test accounts and sessions](https://coldvisit.com/docs/test-accounts): Give signed-in journeys dedicated access without using customer accounts. - [Manage your flows](https://coldvisit.com/docs/flows): Understand approval, boundaries, re-authoring, and suspended coverage. - [Selector healing](https://coldvisit.com/docs/healing): Review repairs, control automatic acceptance, and undo a change. - [Understand a run](https://coldvisit.com/docs/results): Read outcomes, coverage, evidence, and regression feedback. - [Boundaries and guardrails](https://coldvisit.com/docs/guardrails): Understand which actions a flow may perform and how uncertainty is reported. - [Plans and billing](https://coldvisit.com/docs/billing): Trial timing, coverage limits, overages, and downgrades. - [Troubleshooting](https://coldvisit.com/docs/troubleshooting): Find the cause of an incomplete check and get the right next action. --- Source: https://coldvisit.com/docs/getting-started Markdown: https://coldvisit.com/docs/getting-started.md Updated: 2026-09-12 # Your first PR check Connect a repository, choose user journeys, and turn on PR checks. ## Before you start You need a GitHub repository that deploys pull requests to a preview URL. Have a dedicated test account ready if your critical journeys require sign-in. Installing the GitHub App does not enable checks. ColdVisit starts checking pull requests only after you turn on PR checks. ## Connect, explore, approve 1. Select Install on GitHub and sign in to ColdVisit. Grant the GitHub App access to the repository you want to protect. 2. Review the detected preview environment. If it is protected, provide and verify the bypass access requested during setup. 3. Explore the app. Proposed journeys appear while exploration is still running; you can begin selecting them immediately. 4. Select the journeys that matter. ColdVisit prepares their test steps in the background. Complete any request for test access or missing data. 5. Review the test steps, the account it will use, and where it stops before submitting data. Then approve the flow. Watch the initial run and inspect its result. 6. Turn on PR checks. You stay on Free with one repository and three approved flows. Start the optional 30-day Pro trial from Billing when you need more. ## After setup Open Home for things that need attention and recent runs. Flows is where you manage coverage. Your run pages separate regressions from checks that could not run, and show the available browser evidence. --- Source: https://coldvisit.com/docs/previews Markdown: https://coldvisit.com/docs/previews.md Updated: 2026-09-12 # Preview environments Connect the right deployment and handle protected previews. ## Choose the environment you intend to test ColdVisit looks for preview deployments on recent pull requests. Review the detected URL and host before exploring. If no preview is found, setup provides a host-specific guide and lets you check again. Production deployment success is not a substitute for a pull-request preview. ColdVisit needs a working preview of the code in the pull request. ## Protected previews A deployment password or hosting-provider access wall is different from your application’s sign-in screen. Supply the requested preview bypass token or header, then let ColdVisit verify access. Keep bypass values scoped to test environments. You can update environment access in repository settings when the token changes. ## When a preview is unavailable An unreachable or expired preview is reported as couldn’t run. Check deployment health, access credentials, and the target URL before retrying. It is not counted as a confirmed application regression. --- Source: https://coldvisit.com/docs/test-accounts Markdown: https://coldvisit.com/docs/test-accounts.md Updated: 2026-09-12 # Test accounts and sessions Give signed-in journeys dedicated access without using customer accounts. ## Use a dedicated test identity When ColdVisit encounters a sign-in wall, setup can request credentials or a browser storage-state import. Use an account intended for automated testing, with only the data and permissions the selected flow needs. Credentials, session values, and bypass tokens should never be entered into a flow description or public feedback. ## Import or refresh a session A browser storage-state import lets ColdVisit reuse a signed-in test session. Sessions can expire or be revoked. If a run requests refreshed access, update the session in Test accounts and verify that the account can reach the required pages. A session is not permanently valid merely because an earlier run succeeded. Home surfaces access problems separately from product failures. ## Data and parallel runs Review the flow’s fixture strategy: no setup, fresh account, existing test account, or a configured reset strategy. ColdVisit coordinates access where a test account must be exclusive. Additional dedicated accounts can support concurrent journeys. Never reuse a real customer’s account to increase test capacity. --- Source: https://coldvisit.com/docs/flows Markdown: https://coldvisit.com/docs/flows.md Updated: 2026-09-12 # Manage your flows Understand approval, boundaries, re-authoring, and suspended coverage. ## A flow is an approved user journey A flow describes a sequence of browser actions and checks. Review the plain-English steps first; technical selectors and matching details are available when you need them. Drafts do not run as approved coverage. A proposal that needs input stays distinct from an active flow until its missing requirements are completed and it is approved. ## Update coverage Use Add a flow to discover additional journeys on an existing repository or describe a journey. Use re-authoring when a substantial UI change calls for fresh steps; review the proposed replacement before approving it. Run now checks a flow against the selected preview without creating a pull-request check. The resulting run remains available for inspection. ## Suspend and reactivate Suspended flows retain their definitions and history but do not run as active coverage. Reactivation follows the same plan and overage constraints as approval. Pin the flows you want to keep when your plan decreases. --- Source: https://coldvisit.com/docs/healing Markdown: https://coldvisit.com/docs/healing.md Updated: 2026-09-12 # Selector healing Review repairs, control automatic acceptance, and undo a change. ## A small repair with evidence When a step cannot locate its target, ColdVisit can look for the same element and propose a guarded selector repair. A fallback selector may also resolve the target without a healing model call. Healing is not permission to change what the flow does. Identity checks, pinned data, and the commit boundary constrain the proposed repair. ## Accept or reject a change Review what the step targeted before and what it will target afterward. Accept applies a valid change to the approved script. Reject retains the existing selector. A stale proposal must not overwrite a newer script. ## Automatic acceptance and reversal Your automatic-acceptance policy can accept a repeated, identical eligible repair after its configured streak. Settings shows the threshold and recorded acceptances. Reverting an automatic acceptance restores the prior selector when it is still safe to do so and makes that step manual-only. A conflicting later change may require a new review instead of a direct reversal. --- Source: https://coldvisit.com/docs/results Markdown: https://coldvisit.com/docs/results.md Updated: 2026-09-12 # Understand a run Read outcomes, coverage, evidence, and regression feedback. ## Three outcomes Passed means the executed checks succeeded. Failed means a checked flow found a regression. Couldn’t run means access, environment, fixture, or execution conditions prevented a conclusive result. A healed annotation explains that a repair was used; it does not replace the pass/fail outcome. An infrastructure block produces a neutral GitHub conclusion. ## Four coverage labels Checked: a flow was executed. Not affected: selection did not identify it as affected by this change. Inactive: the flow was not active coverage. Couldn’t run: the flow could not produce a conclusive check. Not affected is not the same as passed. Review the selection explanation in technical details when you need to understand why coverage was selected. ## Help qualify failures Inspect the failure explanation, screenshot, and video when available. Mark Yes, real bug or Not a real bug on the failing flow-run. Your verdict is recorded and can be corrected. Feedback qualifies the product’s regression and false-positive reporting. It does not immediately rewrite the pull request or guarantee a model-training change. --- Source: https://coldvisit.com/docs/guardrails Markdown: https://coldvisit.com/docs/guardrails.md Updated: 2026-09-12 # Boundaries and guardrails Understand which actions a flow may perform and how uncertainty is reported. ## Approve the behavior, not just the name Review each authored flow before approval. Its commit boundary specifies where execution stops before a consequential action. Opening that boundary requires an explicit choice and does not bypass the other enforced restrictions. Some journeys need controlled account creation, test mail, or other test data. Review their disclosures and use dedicated testing resources. ## Healing stays within the flow A proposed repair must preserve the target’s identity and respect data and boundary constraints. Automatic acceptance is limited to eligible changes; uncertain or forbidden repairs are not silently applied. ## Uncertainty is visible A preview that cannot be reached or a session that has expired is reported as couldn’t run, with available context. ColdVisit does not label that condition as a proven application failure. The gate is evidence about the selected flows on the tested preview. It is not a guarantee that every possible journey or environment is covered. --- Source: https://coldvisit.com/docs/billing Markdown: https://coldvisit.com/docs/billing.md Updated: 2026-09-12 # Plans and billing Trial timing, coverage limits, overages, and downgrades. ## Free first. Try Pro when you need more. Every new workspace starts on Free with one repository and three approved flows. Start your one-time 30-day Pro trial explicitly from Billing. No card is required. At expiry, Free limits apply and extra coverage is paused without deleting history. ## Coverage determines your plan Every plan includes the blocking PR gate. Plans differ in approved-flow and repository limits. The pricing page and billing page use the same plan definitions. Pro and Scale support additional approved flows at their stated rates. Approval or reactivation that adds billable overage must follow the quotation and confirmation shown in the app. ## Downgrading preserves your work Flows over the new limit are suspended, not deleted. Pin important flows to influence which coverage remains active. Billing shows your plan, usage, notices, and access to the customer portal. --- Source: https://coldvisit.com/docs/troubleshooting Markdown: https://coldvisit.com/docs/troubleshooting.md Updated: 2026-09-12 # Troubleshooting Find the cause of an incomplete check and get the right next action. ## Start with the run Open the run from Home. Failed means the journey produced a failing result; couldn’t run means ColdVisit did not establish a conclusive result. Inspect the coverage list to see which flows ran, were not affected, or were inactive. ## Preview or sign-in problems In Settings, open the affected repository’s setup. Confirm the detected preview URL and reverify any protected-preview bypass token. Refresh expired credentials or a saved session under Test accounts; the account becomes ready only after browser verification. After fixing access, open the flow and use Run now against the confirmed preview. A manual run has its own identity and does not update a PR check. ## A changed interface If a selector proposal is available, compare its current and proposed locators with the recorded browser evidence. Accepting checks that the approved script has not changed and that the repair still passes guardrails. For a journey that changed intentionally, create a candidate revision. The active flow stays intact while the candidate is authored. Review both sets of steps before replacement; the new revision starts with a closed write boundary. ## Missing coverage or evidence Confirm that both the flow and its repository gate are enabled. A plan change can suspend excess flows while retaining their history. Pin flows in advance to express which coverage should survive a downgrade. Video and screenshots are available only when recorded and uploaded successfully. Sign in with access to the owning installation to open evidence links, including links from GitHub. A missing recording is not evidence that the application passed. --- Source: https://coldvisit.com/changelog Markdown: https://coldvisit.com/changelog.md Updated: 2026-09-12 # Development changelog ## 2026-09-11: Tests that adapt when the interface changes ColdVisit remembers more than one verified way to find a button or field. If the first stops working, it tries the alternatives before asking for a repair. - Tests keep verified alternatives for finding the same element. - Clearer text checks and better access checks for protected previews. ## 2026-09-11: Test the journeys behind sign-in Let ColdVisit create a test email account or connect an empty test wallet. It signs in before testing journeys that need an account. - Choose whether to reuse an account across pull requests. - Improved setup for previews and signed-in testing. --- Source: https://coldvisit.com/pilot Markdown: https://coldvisit.com/pilot.md Updated: 2026-09-12 # Design partner pilot Help us improve ColdVisit and test our ideas against real workflows. Your feedback helps us build what your team actually needs. ## Two months. On us. Accepted partners get two months with setup and support included. This application-based program is separate from the optional 30-day Pro trial. ## What your pilot includes - **As we onboard you:** We help configure ColdVisit on your repository, connect your preview, and choose the flows to test. - **A direct line to the founder:** Get help, ask questions, and share feedback throughout your pilot. - **A say in what ships next:** Use ColdVisit on real pull requests and help shape the product around your team. ## A good fit if you - Your team ships code faster than it can review. - Your users rely on your product, and broken flows cost you their trust. - You can share feedback during the two-month pilot. ## Apply 1. [Share your workflow](https://coldvisit.com/pilot) and the journeys you need to protect. 2. We review your application and agree on pilot scope and setup. 3. Your two free months start after acceptance and assisted setup. We discuss options before they end. [Request a demo](https://cal.com/raihankhan/30min) or contact [raihan@coldvisit.com](mailto:raihan@coldvisit.com). --- Source: https://coldvisit.com/sitemap Markdown: https://coldvisit.com/sitemap.md Updated: 2026-09-12 # ColdVisit site map - [Catch broken flows before they merge](https://coldvisit.com/): ColdVisit’s agent opens a real browser and tests critical user journeys on pull-request previews. Get clear results and browser evidence before you merge. Markdown: https://coldvisit.com/index.md - [Pricing](https://coldvisit.com/pricing): Start free with 3 flows on 1 repository. Choose Pro or Scale for more coverage, or opt into a 30-day Pro trial. No card required for Free or the trial. Markdown: https://coldvisit.com/pricing.md - [Documentation](https://coldvisit.com/docs): Connect a GitHub repository, set up preview access, approve user journeys, and understand ColdVisit’s browser tests, results, and guardrails. Markdown: https://coldvisit.com/docs.md - [Your first PR check](https://coldvisit.com/docs/getting-started): Connect a repository, choose user journeys, and turn on PR checks. Markdown: https://coldvisit.com/docs/getting-started.md - [Preview environments](https://coldvisit.com/docs/previews): Connect the right deployment and handle protected previews. Markdown: https://coldvisit.com/docs/previews.md - [Test accounts and sessions](https://coldvisit.com/docs/test-accounts): Give signed-in journeys dedicated access without using customer accounts. Markdown: https://coldvisit.com/docs/test-accounts.md - [Manage your flows](https://coldvisit.com/docs/flows): Understand approval, boundaries, re-authoring, and suspended coverage. Markdown: https://coldvisit.com/docs/flows.md - [Selector healing](https://coldvisit.com/docs/healing): Review repairs, control automatic acceptance, and undo a change. Markdown: https://coldvisit.com/docs/healing.md - [Understand a run](https://coldvisit.com/docs/results): Read outcomes, coverage, evidence, and regression feedback. Markdown: https://coldvisit.com/docs/results.md - [Boundaries and guardrails](https://coldvisit.com/docs/guardrails): Understand which actions a flow may perform and how uncertainty is reported. Markdown: https://coldvisit.com/docs/guardrails.md - [Plans and billing](https://coldvisit.com/docs/billing): Trial timing, coverage limits, overages, and downgrades. Markdown: https://coldvisit.com/docs/billing.md - [Troubleshooting](https://coldvisit.com/docs/troubleshooting): Find the cause of an incomplete check and get the right next action. Markdown: https://coldvisit.com/docs/troubleshooting.md - [Changelog](https://coldvisit.com/changelog): Updates to ColdVisit’s browser tests and developer experience. See what changed in flow authoring, PR checks, browser evidence, and billing. Markdown: https://coldvisit.com/changelog.md - [Design partner pilot](https://coldvisit.com/pilot): Help improve ColdVisit with feedback from your real workflows. Accepted partners get two months with assisted setup and support for their browser tests. Markdown: https://coldvisit.com/pilot.md - [Privacy Policy](https://coldvisit.com/privacy): What we collect to test your user journeys, how we use it, and the choices you have. Markdown: https://coldvisit.com/privacy.md - [Terms of Service](https://coldvisit.com/terms): The rules for connecting your repositories, running browser tests, and using a ColdVisit plan. Markdown: https://coldvisit.com/terms.md - [Refund Policy](https://coldvisit.com/refund-policy): How to cancel renewals and get help with an incorrect charge or a service we could not provide. Markdown: https://coldvisit.com/refund-policy.md ## AI references - [LLM index](https://coldvisit.com/llms.txt) - [Full public reference](https://coldvisit.com/llms-full.txt) - [XML sitemap](https://coldvisit.com/sitemap.xml) ## Legacy audit product - [Free audit](https://coldvisit.com/free-audit) - [Sample report](https://coldvisit.com/audit/demo) - [Owner-published audit library](https://coldvisit.com/audits) Private reports are not listed. --- Source: https://coldvisit.com/privacy Markdown: https://coldvisit.com/privacy.md Updated: 2026-09-12 # Privacy Policy > What we collect to test your user journeys, how we use it, and the choices you have. Effective September 12, 2026 ## 1. Who we are ColdVisit provides automated browser testing for web applications. Our agent explores preview environments, helps you create tests, and checks approved user journeys on pull requests. For privacy questions or requests, email raihan@coldvisit.com. ## 2. Information we collect - Account and workspace details, including your name, email, account identifier, workspace name, and optional workspace image. - GitHub connection details, repository and pull-request information, commits, and configuration needed to select and run checks. - Test instructions, approved flow steps, preview URLs, test data, and the credentials or browser sessions you provide. Managed test accounts may include a generated email address or test-wallet address and the access material needed to sign in. - Content our browser encounters during testing, including page text, screenshots, recordings, execution logs, and results. This may include information visible to the test account. - Pilot applications, support conversations, feedback, and billing records such as plan, subscription status, and payment identifiers. Our payment provider processes card details; ColdVisit does not store full card numbers. - Technical and usage information, such as device and browser details, pages visited, errors, and interactions, subject to your analytics choices. ## 3. Why we use this information We use this information to authenticate you, connect repositories, run and maintain browser tests, show evidence, manage subscriptions, deliver requested messages, provide support, and improve service reliability. Pilot form responses are emailed to our founder for review. Where a legal basis is required, we rely on providing the service you request, our legitimate interests in operating and securing it, legal obligations, or your consent where applicable. We do not sell your personal information. ## 4. Services that help us operate We share the information needed for each task with our service providers. These include Clerk for authentication, GitHub for repository integrations, Browserbase for browser sessions, configured AI providers such as Anthropic or OpenAI for test authoring and repair, Cloudflare R2 for stored artifacts, Dodo Payments for billing, Resend for email, and our hosting and database providers. Sentry helps us diagnose errors. PostHog and other configured analytics services help us understand product use according to your analytics preferences. AI and browser providers may process page content, instructions, and test evidence needed to perform the requested work. Providers may process information outside your country. Where required, appropriate contractual safeguards apply. We may also disclose information when legally required, to address abuse or security incidents, or as part of a business transfer subject to applicable protections. ## 5. Test accounts and browser evidence Use dedicated test accounts and test data. Only give ColdVisit access to environments you are authorized to test. Avoid providing production customer credentials or unnecessary sensitive information. Stored test credentials and session material are encrypted. Access to workspace results and private artifacts is checked against account permissions. Browser evidence can contain information visible during a run, so treat screenshots and recordings as potentially sensitive. No security measure can guarantee absolute protection. Generated test wallets are for connecting and signing supported login messages. They are not intended to hold funds or perform financial transactions. ## 6. How long we keep information We retain account configuration, reusable test access, and run history as needed to provide the service and support your workspace. Removing an account or requesting deletion may remove access material and related records, subject to technical backup cycles and information we must keep for billing, security, or legal obligations. You can ask us about retention or request deletion at raihan@coldvisit.com. We do not promise that every recording, backup, or provider log is deleted immediately after a run. ## 7. Cookies and your choices Essential cookies and browser storage support sign-in, security, theme preferences, and requested features. Use Analytics settings in the website footer to review and change optional analytics preferences. Disabling optional analytics does not disable essential authentication or security functions. Depending on applicable law, you may have rights to access, correct, delete, export, restrict, or object to the use of your personal information, withdraw consent, or complain to a privacy regulator. Contact raihan@coldvisit.com; we may verify your identity before acting on a request. ## 8. Updates We may update this policy as the product changes. The effective date identifies this version. We will communicate material changes where required. --- Source: https://coldvisit.com/terms Markdown: https://coldvisit.com/terms.md Updated: 2026-09-12 # Terms of Service > The rules for connecting your repositories, running browser tests, and using a ColdVisit plan. Effective September 12, 2026 ## 1. Using ColdVisit By creating an account or using ColdVisit, you agree to these terms. If you act for an organization, you confirm that you have authority to accept them on its behalf. Contact raihan@coldvisit.com with questions. ColdVisit opens real browsers to explore configured environments and test approved user journeys. It can report results on GitHub, collect run evidence, and suggest or apply eligible test repairs according to your settings. ## 2. Your account and authorization Keep your account secure and provide accurate billing and contact information. You are responsible for activity through your account and for ensuring that you have permission to connect each repository, test each environment, and provide any data or credentials. Use dedicated test accounts and environments. Review the preview URL, approved steps, test data, and actions a flow is allowed to perform. Do not use ColdVisit for unauthorized access, abuse, unlawful activity, or testing systems you do not control or have permission to test. ## 3. Tests, repairs, and results You choose which flows to approve and when to enable PR checks. Automated repairs update test instructions, not your application code. Review your repair settings and any proposed changes; automatic repairs can be reviewed and undone where the product provides that option. A passing check covers the flows and conditions actually tested. It is not a guarantee that your application has no bugs, security issues, or accessibility problems. Unavailable previews, expired sessions, and service failures can prevent a check from running. Results may be incomplete or incorrect and require your judgment. Guardrails reduce unintended actions but do not replace your responsibility to review test permissions and use test data. ColdVisit is not a security audit or a guarantee of release quality. ## 4. Plans, trials, and pilots Current plan limits and prices are shown on the pricing and billing pages. Paid subscriptions renew at the selected monthly or annual interval unless canceled. Applicable taxes and the amount due are shown at checkout. Dodo Payments processes payments and provides billing services. New workspaces start on Free. You may explicitly start a one-time 30-day Pro trial with no card required. Signup, repository connection and enabling PR checks do not start the trial. When it ends without a paid subscription, the workspace moves to Free. Coverage above the Free limits may be paused while its records remain available. A design partner pilot is separate: accepted teams receive the agreed two-month pilot and setup support. Applying does not start a paid subscription. You can manage or cancel a subscription through Billing. Cancellation stops future renewals according to the subscription details shown there. Refunds are governed by our Refund Policy and applicable law. ## 5. Your content and our service You retain ownership of the content, repositories, and test data you provide. You give ColdVisit permission to process that material and use service providers as needed to deliver the requested testing, evidence, support, and related features. ColdVisit retains ownership of its software, branding, and service. You may use results for your own work, subject to any rights in the underlying content. Do not misrepresent a result or remove context in a way that falsely claims untested behavior was verified. ## 6. Privacy and service providers Our Privacy Policy explains how we handle account details, test access, browser evidence, analytics, and billing information. Third-party services used for authentication, hosting, browsers, AI processing, integrations, and payments may also have terms applicable to your use of their services. ## 7. Availability and limits of liability We work to keep ColdVisit useful and reliable, but we do not promise uninterrupted service, a particular testing outcome, or detection of every defect. To the extent permitted by law, the service is provided as available without additional warranties. To the extent permitted by law, ColdVisit is not liable for indirect or consequential loss, lost profits, or lost data arising from use of the service. Our total liability for a claim is limited to the amount you paid ColdVisit during the six months before the event giving rise to it. These limits do not exclude rights or liabilities that cannot legally be excluded. ## 8. Suspension, changes, and prior purchases We may suspend access for abuse, security risks, nonpayment, or material breaches of these terms. You may stop using the service and request account deletion. Legal and billing records may need to be retained. We may change features and these terms as the service develops. Material subscription changes will be communicated where required. Existing purchases of earlier audit products remain subject to the purchase terms and rights that applied to them; this update does not remove previously purchased credits or mandatory consumer rights. --- Source: https://coldvisit.com/refund-policy Markdown: https://coldvisit.com/refund-policy.md Updated: 2026-09-12 # Refund Policy > How to cancel renewals and get help with an incorrect charge or a service we could not provide. Effective September 12, 2026 ## 1. Subscriptions and cancellation You can cancel future renewals from Billing using the subscription portal. Check the effective cancellation date there. Cancellation does not automatically refund the current monthly or annual period, and unused flows or checks do not by themselves create a refund entitlement. ## 2. When to request a refund We investigate the issue and may first offer a correction. Eligible refunds cover the incorrect charge or the affected service. A test finding no bugs, a disagreement with a result, or a preview that cannot be accessed because of its configuration is not by itself a service failure. - You were charged twice for the same subscription or purchase. - You were charged an incorrect amount or after an effective cancellation. - A confirmed ColdVisit service failure prevented us from providing the paid service and we could not reasonably resolve it. ## 3. Trials and design partner pilots The standard trial and an accepted two-month design partner pilot do not require a paid subscription. Submitting a pilot application does not charge you. If you choose a paid plan, the checkout price and billing interval apply. ## 4. How to contact us Email raihan@coldvisit.com, preferably within seven days of the charge. Include your account email, payment or subscription reference, and a short description of what went wrong. Do not send card details or test-account passwords. We aim to review requests within three business days. Approved refunds go back to the original payment method through Dodo Payments. Bank processing times vary, and the credit may take several business days to appear. ## 5. Earlier audit purchases If you bought a one-time audit or an Agency Bundle before the subscription product, the refund and credit terms shown for that purchase still apply. Contact us with the purchase reference so we can resolve it under those terms. ## 6. Your legal rights This policy does not limit cancellation, refund, dispute, or consumer rights that cannot legally be waived. The seven-day contact preference is not a limit on those rights. Contacting us first often helps resolve a billing problem faster, but you retain your rights with your payment provider.