Privacy policy

In providing AIOPulse (the “Service”), Marketing Cloud Lab (“we” or “us”) sets out this privacy policy for the handling of users’ personal information, as follows.

We collect the following information.

2.1 Account information

• Email address
• Name (optional)
• Authentication information (managed through Clerk)

2.2 Payment information

• Credit card information (processed directly by Stripe; we do not keep card numbers)
• Billing information

2.3 Service usage data

• Registered keywords
• Names of tracked brands
• Result data of LLM queries

2.4 Access logs

• IP address
• Browser type
• Date and time of access

2.5 Information obtained through the Google Search Console connection (only if the connection is set up)

We obtain the following information through Google’s API only if a user connects Google Search Console on the settings screen.

• The email address and identifier of the Google account used for the connection
• The list of Search Console properties (sites) that the Google account can view, and the type of permission for each
• Search performance data for the one property the user selects (search terms, and impressions, clicks and position by date)
• Authorization information for continuing to obtain the data

Access is read-only, and we do not change Search Console settings or the content of the site.

2.6 Information obtained through the Google Analytics connection (only if the connection is set up)

We read the following information from a user’s own Google Analytics (GA4) property through Google’s API only if the user adds the Service’s service account (the email address shown on the settings screen) as a viewer to that property and registers the property’s ID on the settings screen.

• The property’s name and time zone, and the domains of its web data streams (used to confirm that they match the registered site)
• Aggregated data by date and by traffic source (sessions, engaged sessions, key events, and the first page viewed in sessions that came from AI services)

The Service has viewer (read-only) permission only, and does not change Google Analytics settings or data. It reads aggregated values only; it does not read the number of people who visited the site (users) or any information that identifies individual people. This connection uses neither sign-in to nor authorization of the user’s Google account, and we do not receive authorization information for that account.

We use the information we collect for the following purposes.

1. Providing, operating and improving the Service
2. Providing user support
3. Billing and payment processing for fees
4. Notices about the Service (maintenance, outages, changes to the terms, etc.)
5. Creating statistical data (in a form that does not identify individuals)
6. Preventing fraudulent use

We do not provide personal information to third parties except in the following cases.

1. With the user’s consent
2. When based on laws and regulations
3. When necessary to protect a person’s life, body or property

The Service uses the following external services. Each company’s own privacy policy applies to these services.

• Clerk (authentication platform): Used for user authentication and account management.
• Stripe (payment platform): Used to process credit card payments. Card information is processed and stored directly by Stripe and is not stored on our servers.
• OpenAI, Google and Anthropic (LLM providers): Used to send queries based on keywords. Users’ personal information is not sent to the LLM providers.
• Google Search Console (search data connection, optional): If a user sets up the connection, we obtain the search performance data of the selected property on a read-only basis and use it only to show it to that user on the dashboard. We do not use the data obtained for advertising, for sale or provision to third parties, or for training AI models, and we do not send it to LLM providers. We also do not use it to create the statistical data in Section 3 of this policy. Our staff view this data only when the user asks us to, when necessary for security, or when required by law. Our use of information received from Google APIs complies with the Google API Services User Data Policy (including the Limited Use requirements).
• Google Analytics (GA4) data connection (traffic data connection, optional): If a user adds the Service’s service account as a viewer to their own GA4 property and sets up the connection, we obtain the aggregated data by traffic source for that property on a read-only basis and use it only to show it to that user on the dashboard. We do not use the data obtained for advertising, for sale or provision to third parties, or for training AI models, and we do not send it to LLM providers. We also do not use it to create the statistical data in Section 3 of this policy, or in totals combined with other users’ data. Our staff view this data only when the user asks us to, when necessary for security, or when required by law. Our use of information received from Google APIs complies with the Google API Services User Data Policy (including the Limited Use requirements). This is separate from Google Analytics below, which is used for analytics of the Service’s own website.
• Google Cloud Platform (infrastructure): Used to host the backend servers.
• Vercel (infrastructure): Used to host the frontend.
• Supabase (database): Used to store data.
• Google Analytics (web analytics): Used to measure how the site is used and to improve the Service. It uses cookies to collect the pages viewed, actions, approximate region and device information, but we do not send information that directly identifies individuals, such as names or email addresses. You can turn off this measurement with the Google Analytics Opt-out Browser Add-on.
• Vercel Analytics (web analytics): Used to measure page load speed and usage. It does not collect information that identifies individuals.
• Google AdSense (ad delivery): Used to show ads on some information pages. Personalized ads may be shown using cookies. You can turn off personalized ads in Google’s ad settings.

1. Personal information is sent and received over encrypted connections (TLS/SSL).
2. Access to the database is restricted by authentication.
3. We take reasonable security measures to prevent the leakage, loss or damage of personal information.
4. Authorization information used for the Google Search Console connection is stored encrypted.
5. For the Google Analytics connection, we neither receive nor store authorization information for the user’s Google account. A service account that we manage is used to read the data.

We keep data while the user’s account is active. After an account is deleted, we delete the data within a reasonable period, except where the law requires us to keep it.

Data obtained through the Google Search Console connection is deleted when the connection is removed. At the same time, if no other connection of the Service made with the same Google account remains, we revoke the authorization with Google (you can also revoke it at any time in your Google Account settings). We also remove the connection automatically and delete the data in the same way in the following cases: when 30 days have passed since measurement stopped, for example because the contract ended; when reconnection has been needed for 30 days, for example because the authorization was revoked on Google’s side; and when 7 days have passed without a property being selected. Daily data is kept for up to 16 months.

Data obtained through the Google Analytics connection is deleted when the connection is removed. We also remove the connection automatically and delete the data in the same way in the following cases: when 30 days have passed since measurement stopped, for example because the contract ended; and when reconnection has been needed for 30 days, for example because the Service’s service account was removed from the viewers of the property. Daily data is kept for up to 16 months.

Users have the following rights.

1. To request disclosure, correction or deletion of personal information
2. To request that the use of personal information be stopped
3. To delete their account

You can remove the Google Search Console connection at any time from the Service’s settings screen. You can also revoke our access from the Third-party apps & services settings of your Google Account.

You can also remove the Google Analytics connection at any time from the Service’s settings screen, and removing it deletes the stored data. If you delete the Service’s service account under “Property access management” in Google Analytics, the Service can no longer read that property’s data from then on. When you remove the connection, please also delete the service account in this way.

Please send these requests to info@aiopulse.jp.

The Service uses cookies and similar technologies for the following purposes.

• Keeping you signed in and providing the Service
• Web analytics (Google Analytics and Vercel Analytics; see Section 5)
• Ad delivery (Google AdSense; see Section 5)
• Recording the first page visited, to improve the Service (a random identifier cookie such as “aiopulse_vid”; it contains no information that identifies individuals, such as names or email addresses)

You can turn off cookies in your browser settings. If you refuse cookies, some features of the Service may not be available.

When we change this policy, we will give notice by posting it on our website. If a user continues to use the Service after the change, the user is deemed to have agreed to the changed policy.

Please send inquiries about the handling of personal information to the contact below.