SalesBreaker SalesBreaker

SalesBreaker English Workspace

English Privacy Policy

This English Privacy Policy explains how SalesBreaker handles account, service, billing, tracking, workspace, API, and Japan GTM data for English-language users. The Japanese Privacy Policy remains the authoritative legal document in case of conflict, inconsistency, or interpretation.

Important language note

SalesBreaker is operated by SalesBreaker Inc. in Japan. The Japanese Privacy Policy governs the legal interpretation of privacy handling. This English page is provided so English-language users can understand what information may be collected, how it may be used, when it may be shared with service providers, and what responsibilities users have when they use tracking, outreach, APIs, and AI-assisted workflows.

Last updated: June 25, 2026.

This Privacy Policy applies to SalesBreaker websites, English workspace pages, logged-in SaaS functions, Agent Workspace materials, API key pages, tracking scripts, landing pages, forms, support interactions, subscription and billing workflows, and related services. It also explains certain responsibilities of customers who use SalesBreaker on their own websites, domains, landing pages, CRM workflows, or outreach operations.

1. Personal Information

In this policy, personal information means information that can identify a living individual, information that can be combined with other information to identify an individual, and other information treated as personal information under applicable Japanese privacy law. Some information handled by SalesBreaker is business information, company information, technical information, or inferred organization information. Depending on context, that information may still relate to an identifiable person or account user.

2. Information We May Collect

  1. Account and registration information, such as name, email address, company name, department, role, phone number, address, login identifiers, authentication status, and account settings.
  2. Contract, billing, and payment references, such as selected plan, Stripe customer ID, subscription ID, invoice ID, price ID, payment status, cancellation status, trial status, and billing-related support records. Full payment card numbers are handled by Stripe or other payment processors and do not need to be stored by SalesBreaker.
  3. Company profile, sender, domain, and DNS setup information, including sender names, sender email domains, DKIM records, tracking domains, landing page domains, custom domain settings, and related configuration status.
  4. Customer-created or customer-uploaded data, including house lists, target companies, contacts, CRM records, tags, statuses, notes, suppression settings, message templates, landing pages, forms, scenarios, documents, click logs, send history, reply handling notes, and API integration settings.
  5. SalesBreaker-owned or SalesBreaker-managed company data, including Japanese company names, addresses, industries, public website information, source records, tags, classifications, organization identifiers, IP-based organization estimates, and related public or operational source data.
  6. Outreach and operator workflow data, including execution logs, review states, quality checks, form-analysis results, delivery or submission results, error logs, click/open/unsubscribe events, customer ledger activity, CRM activity, and operational audit records.
  7. Website, analytics, and advertising measurement data, including IP address, cookies, device information, browser type, operating system, referrer, UTM parameters, landing page path, click events, conversion events, fbp/fbc identifiers, hashed contact identifiers where applicable, and similar technical or measurement signals.
  8. API, Agent Workspace, and AI-assisted workflow data, including API key metadata, scopes, workspace-version information, prompt/documentation access, operator-assist activity, request logs, and actions taken through tools such as Codex, ChatGPT, Claude Code, Cursor, Gemini, or other AI/developer environments when used with SalesBreaker.
  9. Support, inquiry, cancellation, complaint, abuse-report, security, and privacy-request information, including messages, attachments, investigation details, and response history.

3. How Information Is Collected

  1. Information may be collected when you register, log in, verify email, select a plan, open Stripe Checkout, use the SaaS, configure domains, create lists, upload data, create templates, send outreach, create forms, build landing pages, use APIs, download workspace materials, or contact support.
  2. Information may be collected automatically through service logs, browser sessions, cookies, tracking links, pixels, open tracking, click tracking, unsubscribe links, API logs, error logs, analytics tools, advertising measurement tools, and security systems.
  3. Information may be received from service providers and integrations, including Stripe, cloud infrastructure, email delivery services, analytics tools, advertising platforms, customer-configured domains, CRM tools, and AI or developer tools you choose to use.
  4. Japanese company data may be collected, organized, corrected, or inferred from public sources, company websites, technical analysis, source records, and other lawful operational sources.

4. Purposes of Use

  1. To provide, operate, authenticate, secure, maintain, and improve SalesBreaker.
  2. To create and manage accounts, subscriptions, trials, invoices, payments, cancellations, plan changes, and billing support.
  3. To support Japan GTM workflows, company research, target filtering, suppression, message creation, form analysis, outreach execution, click/open measurement, reply handling, CRM operations, customer ledger workflows, marketing automation, and related SaaS functions.
  4. To operate domain settings, sender settings, tracking domains, landing pages, forms, one-line tags, scripts, custom domains, DNS verification, and customer-configured tracking.
  5. To provide API keys, Agent Workspace materials, operator-assist functions, documentation, AI-assisted workflows, and related support.
  6. To respond to inquiries, support requests, billing questions, cancellation requests, privacy requests, security reports, complaints, abuse reports, and legal requests.
  7. To detect, prevent, investigate, and respond to fraud, trial abuse, spam, unlawful use, security incidents, service errors, system overload, data misuse, recipient complaints, and violations of SalesBreaker terms.
  8. To perform analytics, advertising measurement, conversion measurement, product improvement, quality control, load management, service reliability analysis, and feature-usage analysis.
  9. To create aggregated or de-identified information that does not identify a specific person or customer for service quality, product development, capacity planning, debugging, and operational learning.
  10. To comply with law, enforce contracts, protect rights, and preserve records reasonably needed for legal, accounting, security, operational, or dispute-resolution purposes.

5. Cookies, Tracking, Advertising, and CAPI

  1. SalesBreaker may use cookies, local storage, server logs, tracking links, pixels, and similar technologies for login, security, service operation, analytics, product improvement, advertising measurement, and conversion measurement.
  2. SalesBreaker may use Meta Pixel, Meta Conversions API, Microsoft Clarity, and similar tools for SalesBreaker-owned advertising and website analytics. These tools may receive event information, browser identifiers, hashed contact identifiers where applicable, click identifiers, page paths, referrers, UTM parameters, and conversion data.
  3. When a customer configures customer-provided pixels, CAPI settings, tags, scripts, forms, or tracking domains, information may be sent to that customer's selected providers according to the customer's configuration and those providers' terms.
  4. Browser settings, cookie restrictions, ad blockers, privacy tools, and translation tools may affect tracking, login behavior, attribution, measurement, or functionality.
  5. Customers who install SalesBreaker tags, scripts, tracking links, forms, pixels, or similar tools on their own sites are responsible for providing any required privacy notices, cookie notices, consent mechanisms, and opt-out mechanisms to their own site visitors and end users.

6. Customer Data, House Lists, and Company Data Separation

  1. Customer-specific data is handled separately for each customer account or client environment.
  2. SalesBreaker does not make a customer's uploaded house lists, customer CRM records, notes, suppression settings, send history, or customer-specific operational data available to other customers as SalesBreaker-owned company database records.
  3. SalesBreaker-owned company data and customer-specific data may appear together inside a customer's workspace so the customer can perform Japan GTM work, but they are treated as distinct data categories.
  4. SalesBreaker may use customer-specific data as necessary to provide the service, support the customer, investigate problems, prevent misuse, maintain quality, comply with law, and improve reliability.
  5. SalesBreaker may use aggregated or de-identified information for quality and operational improvement, provided it does not identify a specific individual or customer.

7. Sharing, Service Providers, and External Transmission

  1. SalesBreaker may share information with service providers and processors as necessary for hosting, database operation, storage, backup, security, authentication, email delivery, billing, payment processing, analytics, advertising measurement, support, logging, error monitoring, AI assistance, and service operation.
  2. Service providers may include cloud infrastructure providers, payment processors such as Stripe, email and notification providers, analytics tools, advertising platforms, domain/CDN/DNS-related providers, customer support tools, and AI/developer tool providers where enabled or used.
  3. SalesBreaker may disclose information when required by law, regulation, court order, government request, payment processor requirement, security investigation, abuse prevention, contractual enforcement, rights protection, or dispute handling.
  4. SalesBreaker may share information with a customer's own configured providers or integrations when the customer enables that integration or instructs SalesBreaker to send information to that destination.
  5. SalesBreaker does not sell customer-specific house lists or customer-specific operational data as standalone datasets to other customers.

8. International Processing

  1. SalesBreaker is operated from Japan, but information may be stored, processed, transmitted, or accessed in Japan and other countries where SalesBreaker, its service providers, payment processors, infrastructure providers, analytics providers, advertising providers, or AI/developer tool providers operate.
  2. When information is processed outside the user's country, privacy and data protection rules may differ from those in the user's location.
  3. SalesBreaker uses service providers and operational controls that it considers appropriate for the service, taking into account the type of information, purpose of processing, and operational needs.

9. AI Tools and Agent Workspace

  1. SalesBreaker may provide documentation, prompts, API key pages, Agent Workspace ZIP files, markdown files, and operator-assist materials to help customers use SalesBreaker with AI or developer tools.
  2. If you choose to paste, upload, export, or expose SalesBreaker data to third-party AI tools or developer environments, that provider may process the information under its own terms and privacy practices. You are responsible for your organization's use of those tools.
  3. Do not provide sensitive personal information, confidential customer data, API keys, credentials, payment information, or private records to external AI tools unless your organization has approved that use and the tool is appropriate for that information.
  4. SalesBreaker may use AI-assisted or automated tools internally or through service providers for support, debugging, drafting, quality review, classification, and operational assistance where appropriate. Human review may be used for sensitive or operationally important decisions.

10. Google Workspace Data and AI/ML Use

  1. When a user connects Google Calendar or another Google API integration, SalesBreaker may access Google account information and Google Calendar information only within the OAuth scopes approved by that user.
  2. SalesBreaker uses Google Workspace user data only to provide the requested Google Calendar and scheduling functions, including calendar connection, availability checks, booking creation, rescheduling, cancellation, connection management, troubleshooting, security, and abuse prevention.
  3. The use and transfer of raw or derived user data received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
  4. SalesBreaker does not send Google Workspace user data obtained through Google APIs to any third-party AI or large language model provider. SalesBreaker currently has no AI/LLM subprocessors that process Google Workspace user data.
  5. SalesBreaker does not use Google Workspace user data obtained through Google APIs to develop, improve, or train generalized AI or machine learning models.
  6. If SalesBreaker later offers a feature that sends Google Workspace user data to a third-party AI or LLM provider, SalesBreaker will first update this policy or provide another appropriate disclosure and obtain any required consent or authorization.

11. Data Accuracy and Source Limitations

  1. SalesBreaker company data, organization identification, IP-based estimates, form-analysis results, source records, tags, classifications, and related information may be based on public information, technical analysis, source data, inference, or correction processes.
  2. SalesBreaker does not guarantee that such information is always accurate, complete, current, lawful for every customer use, or suitable for every business decision.
  3. Customers should review information before using it for outreach, CRM, advertising, account planning, or other business activity.

12. Retention

  1. SalesBreaker retains information for as long as reasonably necessary to provide the service, maintain accounts, process billing, support customers, comply with law, resolve disputes, enforce contracts, prevent misuse, maintain security, debug systems, and preserve operational records.
  2. Some logs, billing records, security records, support records, and legal/accounting records may be retained after account cancellation when reasonably necessary.
  3. Customers may request deletion or correction as described in this policy, but some information may remain where retention is required or reasonably necessary for legal, security, billing, dispute, backup, or operational reasons.

13. Security

  1. SalesBreaker uses reasonable technical, organizational, and operational measures to protect information, taking into account the nature of the information and service.
  2. No internet service, cloud system, email system, browser workflow, AI tool, or third-party integration can be guaranteed to be completely secure.
  3. Customers are responsible for protecting their own accounts, passwords, API keys, workspace files, custom domains, email accounts, CRM systems, browser sessions, and connected tools.
  4. See the English Security Summary for additional information about security practices, certification status, and operational controls.

14. Access, Correction, Suspension of Use, and Deletion Requests

  1. Where required by applicable law, SalesBreaker will respond to requests for disclosure, correction, addition, deletion, suspension of use, erasure, or suspension of third-party provision after confirming the identity and authority of the requester.
  2. A disclosure request may be subject to a fee, currently 1,000 JPY per request, where permitted by law and described in the Japanese Privacy Policy.
  3. Requests may be limited or denied when permitted by law, when identity cannot be verified, when the requester lacks authority, when disclosure would harm rights or legitimate interests, or when retention is required for legal, security, billing, dispute, or operational reasons.
  4. For privacy requests, use Help & Support inside the English workspace or the inquiry channel described in the Japanese Privacy Policy.

15. Customer Responsibilities

  1. Customers are responsible for ensuring that their own use of SalesBreaker complies with applicable privacy, advertising, email, outreach, cookie, tracking, AI, CRM, and data-protection requirements.
  2. Customers must provide accurate notices and obtain any required consent from their own employees, users, leads, site visitors, customers, recipients, and end users when using SalesBreaker tags, forms, tracking links, pixels, custom domains, CAPI integrations, CRM integrations, AI tools, or outreach workflows.
  3. Customers must not upload, process, or transmit information through SalesBreaker unless they have the right to do so.
  4. Customers must promptly handle opt-out, deletion, correction, complaint, and non-contact requests they receive in connection with their own outreach or website activity.

16. Changes to This Policy

  1. SalesBreaker may update this English Privacy Policy and the authoritative Japanese Privacy Policy due to legal changes, service changes, operational changes, security needs, new integrations, or changes in data handling.
  2. Updated policies become effective when posted on the website or at another time stated by SalesBreaker, unless applicable law requires a different process.
  3. Important changes may be announced through website posting, in-app notice, email, or another reasonable method.

17. Authoritative Japanese Policy and Contact

  1. The Japanese Privacy Policy is the authoritative legal document for privacy handling by SalesBreaker. This English policy is provided to help English-language users understand SalesBreaker's practices.
  2. If there is any conflict, inconsistency, or question of legal interpretation between this English policy and the Japanese Privacy Policy, the Japanese Privacy Policy controls unless applicable law requires otherwise.
  3. For privacy inquiries, account questions, billing questions, or cancellation questions, use Help & Support inside the English workspace or the inquiry channel described in the Japanese legal pages.