Privacy Policy

Chipper Inc. (hereinafter "the Company") establishes the following provisions regarding the handling of personal information and linked account information in the marketing support tool "Creative Drive CRO" (hereinafter "the Service") provided by the Company.This policy is ourCorporate Privacy Policyand supplements the handling specific to this service (use of data obtained through external service integrations and Google user data).

Business Information

• Business operator: Chipper Inc. (Representative: Yuki Toki)
• Location: 15F, Cerulean Tower, 26-1 Sakuraoka-cho, Shibuya Ward, Tokyo 150-0031
• Contact:info@chipper.co.jp / 03-4405-0860 (Weekdays 10:00–19:00)

2. Information to Acquire

• Account Information: Email address, name/organization name, authentication information (passwords are stored in hashed form).
• Data created and measured in this service: Content of created LPs, first-party measurement data such as impressions, clicks, and scrolls on published LPs.
• Visitor Identifier (cl_uid): Randomly generated and assigned to public LPs, measurement tag placement pages, and intermediate pagesFirst-party anonymous identifierIt is.Used for A/B test distribution, page variation based on number of visits, and measurement of impressions, clicks, and conversions.Personal information such as name, contact details, and age is not included, and the identifier alone does not identify a specific individual.Please note that the input information and cl_uid may be associated on behalf of the user (customer) only when an LP visitor enters personal information via the form feature described later.
• Form (Prospect) Information: The user (customer) uses this serviceForm FunctionIf installed, personal information such as the name, email address, phone number, and inquiry details entered by visitors to the landing page will be collected and stored on behalf of the user.For this informationUser is the administrator of personal informationand,We are a processor that handles data processing based on the instructions of the data controller.As a [role], we manage it safely within the scope of the outsourcing agreement.Obtaining consent, notifying users of the purpose of use, and ensuring legal compliance are the responsibility of the user.
• Data acquired through integration (read-only): Based on the authorization of the contracted user, report metrics from Google Analytics (GA4) and campaign performance metrics from advertising accounts (Google Ads / Meta Ads) will be retrieved.Any/AllAggregated report values onlyPersonal information that can identify individuals is not collected.
• Visitor behavior log: Records views, clicks, scroll depth, time spent, and page view sequences on pages where the measurement tag is installed.Used to improve pages and deliver personalized content tailored to each visitor.
• Estimated region: Estimates and stores the country, region (prefecture or state), and city/municipality based on the source IP address.The IP address itself is used for this determination and fraud prevention, and will not be retained in reports.This is an estimate and may differ from the actual location.
• Session Replay (only when enabled by the user): Not retrieved by default.Only when enabled by the user (customer), the screen interactions of LP visitors (mouse movements, clicks, scrolls, and screen changes) will be recorded and made available for later playback.The following handling will apply when recording.
  • All characters typed in the input field will be masked and recorded.The same applies to passwords, email addresses, and phone numbers.The actual entered values will not be recorded.
  • Instead of recording all visits, record visits that show signs of conversions, rage clicks, unresponsive clicks, errors, and dead ends.
  • Records are compressed and stored,Automatically deleted after 60 daysWill do.
  • User is on the page cl-noreplay or cl-mask Areas marked with this designation will be excluded from recording or will be masked.Please specify the areas you do not want to display on the user side.
• Questions for visitors and their answers (only when enabled by the user): Not retrieved by default.Only when configured by the user, questions are displayed on-screen to LP visitors, and their answers are stored linked to the visitor identifier.Answers are used for branching output and reports.The legality of the question content and the act of seeking answers is the responsibility of the user to determine.
• Referral site: Records which site the visitor came from.It will also be used to determine whether a visit was made via comparison or competitor sites registered by the user.We do not collect individual browsing histories; we only handle the referrer passed to pages where our tag is active.
• Estimation of the connecting organization (only when enabled by the user): Not retrieved by default.Only when enabled by the user, the system estimates whether the connection originates from a corporate network based on the source IP address, and determines company attributes such as company name, industry, and size.Estimation of corporate attributes, not personal identificationIt is.This is an estimate and may differ from actual results.
• Customer chat conversation: When a user installs the customer service chat, the content entered by LP visitors and our responses will be stored.To generate a response, the conversation content and materials registered by the user areSend to external AI service (Anthropic)Will do.The content you send will not be used for training the AI in question.If a visitor enters personal information, the user will be the controller and our company will be the processor of that information.
• Location information (only when enabled by the user): Not retrieved by default.Only when the user (customer) has enabled this feature, the browser of LP visitorsWith the visitor's consentUsing the acquired location information, the distance from pre-registered stores/locations isIn the visitor's deviceDetermine.Latitude and longitude data itself is not transmitted to or stored on our servers.We only receive the result of whether the user is "within the range of any of the registered locations."This feature will not work if visitors do not allow location access in their browser.

3. Usage Purpose

The information obtained will be used for the following purposes.If the purpose of use is changed, it will be done within a reasonably recognized scope of relevance, and the individual will be notified or publicly announced.

• Service Provision: LP creation/delivery/A/B testing, performance report generation, improvement suggestion display, customer chat responses, support handling, fraud prevention, and billing management.
• Improvement of this service and development of new features: Analyzes which features are being used and how, identifies where users get stuck, and applies the findings to improvements.
• Statistical analysis and publication of its results: We may compile insights such as industry-specific trends, the effectiveness of improvement measures, and average figures, and publish them externally as seminars, proposal materials, articles, or reports.

4. Use of Google User Data (Limited Use)

The use and transfer to other applications of information received from Google API through this service isGoogle API Services User Data Policy(including requirements for limited use).Specifically, the data obtained from Google Analytics is

• Used only to provide easy-to-understand features (reporting and analysis features of this service) to users.
• Not used for ad delivery purposes.
• We do not sell to third parties.
• Human review will not be conducted except with the explicit consent of the user, for security, fraud prevention, or legal compliance purposes, or when data is aggregated and anonymized for internal operations.

5. Slack Integration

By connecting this service's customer chat to Slack, you can receive inquiries from LP visitors in Slack and reply directly from Slack.The information that our company handles in this integration is as follows.

• Workspace Information: A list of the workspace ID and name, and the channels selected as posting destinations (ID and name).
• Channel messages: You will receive messages from Slack from channels where this service has been added.Of theseOnly replies to threads created by this service, processes and stores them, and discards the rest immediately.Direct messages and files will not be accepted.
• Access token: It is stored encrypted and will never be displayed again on screen or via API.

The thread replies read will only be used to deliver messages to visitors.If the visitor's language differs from that of the Slack agent, the reply content will be sent to an external AI service for translation and displayed in the visitor's language.The content you send will not be used for training that AI.If the language is the same, it will not be sent externally.We do not use this for ad delivery.We do not sell to third parties.We do not use this for training machine learning models.

The Slack integration can be disconnected at any time from the settings screen of this service, and the token and workspace information will be deleted upon disconnection.If the app is uninstalled on the Slack side, it will also be deleted.

6. Access Permissions and Authentication Token

Authentication information such as access tokens obtained during integration isMinimum required permissions for this featurewill be retrieved with.Analytics and advertising integrations are read-only.The Slack integration only acquires the minimum permissions necessary to post inquiries and read replies.Authentication credentials are encrypted and stored in an access-restricted area.You can disconnect the integration at any time from the settings screen of this service, and the corresponding credentials will be deleted upon disconnection.

7. Security Management Measures

We implement organizational, human, physical, and technical security management measures.Communications are encrypted via HTTPS, and credentials and sensitive data are managed in an access-controlled environment.Please note that some data may be stored with cloud service providers in the United States and may be routed through countries such as Australia and India.

The following information isStore after one-way hashingWill do.No one, including us, can restore the original values.Even if data leaks from the storage location, the original information cannot be retrieved from it.

• Login password: We do not store this in plain text, as it is used only for verification.
• API Key: Displayed only once at the time of issuance and cannot be accessed by us thereafter.
• Index used for matching the same person: Indexes used to identify the same person across different devices or domains (such as email addresses and member IDs provided by users) are only used for matching purposes, so they are hashed before being stored.Use a different hash for each user,They will not be matched as the same person across different users.
• Session replay input values: Since the information is masked at the point of recording, the characters you enter will not reach us.

Items stored with their original values intact: The name, email address, and phone number of leads obtained through forms are stored as-is in their original values, as they are used by the user (customer) for contact purposes.This information is managed in an access-controlled environment, with the user acting as the controller and our company acting as the processor.

8. Retention Period / Deletion

The acquired and generated information is retained for the following periods by type.All of them will be automatically deleted after the period has elapsed.

• Visitor Identifier (cl_uid): Up to 2 years in first-party cookies on the browser.
• Status per visitor(Number of visits, sequence of pages viewed, content distribution assignment, etc.): Up to 90 days.
• Session Replay Recording: 60 days.
• Aggregated value(Non-personally identifiable numbers such as daily impressions and conversion counts): Up to 3 years.
• Lead information captured via form: Up to 2 years.Because this is business data belonging to users (customers), it is retained longer than per-visitor state data.
• Customer chat conversation: The period necessary for providing this service.

When the integration is disconnected, the token will be deleted. When your account is deleted or your contract is terminated, related data will be deleted unless retention is required by law.Requests for disclosure, correction, suspension of use, or deletion will be accepted at the contact information above after verifying your identity.

9. Third-Party Disclosure

We will never sell or provide the information we obtain to third parties.However, this does not apply in cases required by law, business outsourcing, or business succession.When providing information to third parties overseas, we will provide the necessary information in accordance with laws and regulations.Please note that if the user (customer) exports or integrates lead information obtained through forms to an external service (CRM/marketing tools, etc.) at their own discretion, such transmission isHandling under user control based on user instructionsand the handling of data within those external services is subject to each service's own policy.

10. Feature for operating this service from external AI (MCP integration)

Users (customers) can enable a feature that allows external AI (Claude, ChatGPT, etc.) to operate this service.Disabled by default.

• When enabled, the AI service will be able to read data from this service (including reports, settings, customer chat conversations, and prospect information) or modify settings.
• The read data will be sent to the provider of the applicable AI service.The handling at the destination follows the policies of the respective service.
• A key issued by the user is required for the connection.For each key, you can specify the scope of permissions, such as read-only or including configuration changes.
• The key is fixed to one contract unit,You cannot access data from other contracts.
• A record will be kept of when, which key, and which operation was performed.You can revoke the key at any time from the settings screen.

Whether to enable this feature and what scope of permissions to grant are determined at the user's own discretion and responsibility.

11. If you are using our services through an agency

This service may be provided through agencies authorized by our company.In this case, the following handling will occur.

• Agency View: Agencies may view and operate your account and data within the scope you have configured.The scope is set and reviewed by you (the customer).
• Verification by us: Our company uses your information to the extent necessary for service provision, support responses, incident investigation, fraud prevention, and billing verification.We may review accounts managed by agencies and the data contained therein。Confirmations are performed to the minimum necessary extent,Records who accessed what data and when。
• We will never use an agency's data for sales activities directed at clients other than that agency.

12. Cookies, Visitor Identifiers & Access Analytics

This service uses first-party cookies and similar technologies for the following purposes: maintaining login sessions, A/B test assignment, page variation based on visit count, and first-party measurement of impressions, clicks, and conversions (visitor identifier cl_uid).To continue tracking across multiple domains operated by the same contract holder, cl_uid may be passed as a parameter in the destination URL.These are all first-party measurements and will not be used for behavioral tracking by third parties or for advertising delivery purposes.In addition, our site may use Google Analytics.Visitor identifiers and cookies can be disabled at any time through your browser's cookie deletion or blocking settings.

13. Revision

This policy may be revised as necessary.Important changes will be announced on this service.

14. Contact Us

For inquiries regarding this policy and the handling of data,info@chipper.co.jpPlease contact Chipper Inc.