lacks analytics Privacy Policy
Last updated: 2026-11-07
This Privacy Policy sets out how information is collected, used, and managed in lacks analytics (hereinafter "this service"), a social media analytics tool provided by lacks japan Co., Ltd. Before using the features of this service, users are asked to agree to this policy. If we revise this policy, users will be asked to agree again when they use this service after the revision.
1. Information We Collect
This service collects the information necessary for social media management agency operations within the scope set out below. Information is obtained through the official APIs of social media platforms (Instagram / TikTok / YouTube / Threads), direct input from users, and other lawful data sources.
- Email address and authentication credentials entered when registering to use this service
- Access tokens and refresh tokens of each platform obtained via OAuth connection (stored encrypted on the server side)
- Profile information of connected social media accounts (username, profile image, follower count, etc.)
- Post metadata (caption, thumbnail, body text, publication date and time, video file URL, etc.)
- Insights information (reach, impressions, likes, comments, view count, follower attributes, etc.)
- Instagram direct message (DM) conversation metadata and message bodies (obtained with the instagram_business_manage_messages scope in order to carry out reply operations within the official 24-hour response window and to generate AI reply drafts)
- Instagram and YouTube comment bodies, comment author usernames, and comment reply history (obtained for comment management and AI reply generation). In addition, only when a reply to an Instagram comment is sent from this service, we record the identifier (ID) of that reply returned by Instagram (to correctly tell replies sent from this service apart from replies by other users; this record does not include the reply text or the identifier of the comment being replied to)
- Reply bodies, replier usernames, and mention bodies on Threads posts (obtained via the official Threads API and webhook notifications for reply moderation and mention review)
- Data entered by users within this service (scheduled posts, draft posts, comment templates, team member information)
- Information obtained only when a user connects a client company's TikTok account for comment management: the identifier, display name, and username of the connected account; the list of videos (caption, thumbnail, link to the video); and the comments on those videos and their replies (text, whether the comment includes an image, the author's username and display name, posting date and time, visibility status, whether the comment was posted by the connected account itself, whether the connected account has liked the comment). This information is used to display the comment list, reply to comments, hide and unhide comments, delete comments posted by the connected account itself, like and unlike comments, and generate AI replies. Items included in TikTok's responses that are not used for these purposes, such as the commenter's identifier, profile image, like count, and the image in a comment itself, are discarded without being stored or displayed. The comment management connection can be disconnected at any time from the settings screen of this service; once disconnected, we stop obtaining this information and request TikTok to revoke the access token
- Account and post analytics obtained only when a user connects a client company's TikTok account for comment management: the profile of the connected account (display name, username, profile image, profile link, bio, whether it is verified, whether it is a Verified Business Account, whether it has Advanced Access) and its lifetime figures (followers, following, likes, number of posts); daily figures for the selected period (video views, unique viewers reached, profile views, likes, comments, shares, engaged audience, total followers and follower changes); follower demographics (shares by gender, age group, country and city) and the hours when followers are active; and, for each post, the posting time, video length and figures (views, likes, comments, shares, saves, reach, watch time, full-watch rate, new followers, profile views, traffic sources, and viewer breakdowns by follower status, new or returning viewers, gender, country and city). The figures and demographics are aggregated values calculated by TikTok and do not include information that identifies individual viewers. This information is used to display analytics on the dashboard (the captions, thumbnails and links in the video list are also used to show the post list on the dashboard). Once the comment management connection is disconnected from the settings screen of this service, we no longer obtain it.
- TikTok direct message (DM) information obtained only when a user connects a client company's TikTok account for comment management and the client company permits access to DMs: the list of conversations (conversation identifier and last updated time); for the most recently updated of those conversations, the most recent messages in each conversation (the text of text messages, the message type, the time sent, whether the message was sent by the connected account, and the message identifier); and the other participant's identifier, display name, and username. This information is used to display the DM list, to send text replies that the user reviews before sending, and to generate AI replies. For messages other than text (such as images and shared posts), only the type is displayed, not their content. Items included in TikTok's responses that are not used for these purposes, such as the other participant's profile image and the content of messages other than text, are discarded without being stored or displayed. Because DM information is obtained through the comment management connection, disconnecting the comment management connection from the settings screen of this service stops us from obtaining it
2. Purposes of Use
The information obtained is used only for the following purposes.
- Providing the SaaS features of this service (dashboard analytics, post planning, post publishing, comment management, and DM replies)
- Supporting social media management agency operations and creating performance reports
- Statistical analysis for service improvement (in a form that cannot identify individuals; information obtained from YouTube API Services and TikTok APIs is excluded)
- Detection of unauthorized use and support response
- Compliance with legal obligations (tax, accounting, regulatory compliance)
We do not use personal information for the purpose of advertising delivery or sale to third parties.
3. Provision to Third Parties
Each of the following service providers maintains security standards equivalent to or exceeding industry standards, and exchanges only the minimum data necessary to provide this service. We do not provide information to third parties for advertising or marketing purposes.
- Meta Platforms, Inc. (Instagram / Threads API integration)
- TikTok Pte. Ltd. (TikTok Display / Content Posting API integration), and the provider of TikTok API for Business (comment management integration, which handles comments, DMs, and account and post analytics)
- Google LLC (YouTube Data API and YouTube Analytics API integration / generative AI "Gemini" integration). For the handling of YouTube information, see "11-2"
- Supabase, Inc. (database and authentication infrastructure, Tokyo region)
- Vercel Inc. (web application hosting / CDN)
If we add or change any provider other than the above, we will update this policy and notify users. Where the addition of a provider has a material effect on the rights and obligations of users, we will provide an opportunity for prior notice.
4. Retention Period
The retention period for information is determined as follows, in accordance with the API specifications of the source, business necessity, and the user contract period. Data that has passed its prescribed retention period is automatically deleted. Retention and removal of browser operation hold markers are described in section 8, Cookies and Local Storage.
- OAuth tokens: deleted upon disconnection or termination of the contract
- Instagram / Threads / TikTok (analytics and posting connection) Insights data (analytics data such as reach, impressions, and engagement): retained during the contract period (for year-over-year comparison, long-term trend analysis, and strategic decision-making support), deleted within 30 days after termination of the contract. Analytics obtained through the TikTok comment management connection are not stored, as described below
- Data obtained from YouTube API Services: see "11-2"
- Post metadata and profile information: retained during the contract period, deleted within 30 days after termination of the contract (excluding information obtained from YouTube API Services, which is handled as described above, and information obtained through the TikTok comment management connection, which is handled as described below)
- Daily snapshots: retained during the contract period, deleted within 30 days after termination of the contract (excluding information obtained from YouTube API Services, which is handled as described above)
- Data entered by users (scheduled posts, comment templates, etc.): retained during the contract period, deleted within 30 days after termination of the contract
- Backups: taken once a day and kept for 7 days (data that has been deleted is also erased from the backups within 7 days at the latest)
- Instagram / Threads webhook event payloads (including comment bodies and message bodies): up to 30 days from receipt. Automatically deleted after 30 days. Deleted immediately upon receipt of a data deletion request
- Threads reply and mention cache (reply bodies and mention bodies): deleted immediately upon receipt of a data deletion request
- The comments and video lists obtained through the TikTok comment management connection: not stored in this service's database. They are retrieved from TikTok when the comments screen is opened or the client company is switched, and are kept temporarily in the memory of the user's browser for display (in addition to the client company being displayed, data for other client companies that the user may switch to may be retrieved in advance; all of it is cleared when the page is reloaded or closed)
- DM information obtained through the TikTok comment management connection: not stored in this service's database. When the DM screen is opened or the client company is switched, only the data for the client company being displayed is retrieved from TikTok, and it is kept temporarily in the memory of the user's browser for display (data for other client companies is not retrieved in advance; all of it is cleared when the page is reloaded or closed)
- Account and post analytics obtained through the TikTok comment management connection: not stored in this service's database. They are retrieved from TikTok when the dashboard is opened or the period or client company is switched, and are kept temporarily in the memory of the user's browser for display (cleared when the page is reloaded or closed)
- Connection information stored for the TikTok comment management connection (the identifier, display name, and username of the connected account): retained while connected, and deleted together with the access tokens when the connection is disconnected from the settings screen of this service, when we confirm that access has been revoked on TikTok, or upon termination of the contract
- Identifiers (IDs) of Instagram comment replies sent from this service: 90 days from recording. Records older than 90 days are not used to identify replies and are deleted the next time a reply is recorded for the same client company. They are deleted at that point if the client company or organization is deleted, or if a data deletion request is received from Meta
5. User Rights
Users have the right to request access to, correction of, deletion of, suspension of processing of, and data portability (export in a standard format) of their own data. After verifying the requester's identity, we will respond as follows (unless otherwise stated, the periods are counted from the completion of identity verification).
- Deletion requests: handled in principle within 30 days (information obtained from YouTube API Services is deleted within 7 days of receiving the request, including identity verification; if a user disconnects YouTube from the settings screen of this service, it is deleted on the spot; see "11-2")
- Access and correction requests: handled in principle within 14 days
- Data portability requests (export in a standard format such as CSV): handled in principle within 30 days
For the specific procedure, please see Data Deletion Procedure.
6. Notification in the Event of a Data Breach
In the event of a serious data breach (leakage, loss, or damage of personal information) in this service, we will take the following measures.
- Prompt reporting to the Personal Information Protection Commission (based on the Act on the Protection of Personal Information)
- Prompt notification to affected users (to the registered email address)
- Content of notification: an overview of the breach, the scope of impact, the measures this service will take, and the countermeasures users can take
7. Handling of Minors' Information
This service is a B2B SaaS, and contracting users (social media management agencies) are assumed to be corporate representatives aged 18 or older. This service does not collect personal information directly from minors.
However, insights data obtained through the social media accounts of the client companies that users manage on their behalf may include aggregated values for followers classified as minors by each platform's estimation (for example, the 13-17 age category). Although these are obtained in a statistical form that does not identify individuals, this service handles them under the following policy.
- Aggregated data on minor followers is not used for anything other than the analysis necessary for management agency operations
- It is not used for the purpose of direct targeted advertising or marketing toward minors
- We comply with each social media platform's policy for the protection of minors (Meta's "no access for those under 13", TikTok's "restricted mode for those under 13", YouTube's "Made for Kids", etc.)
- Requests for the deletion of minors' data are handled in the same manner as ordinary deletion requests
8. Cookies and Local Storage
For the purpose of maintaining the logged-in state and saving UI settings, we use httpOnly cookies and the browser's local storage. At present, we do not use third-party cookies for advertising tracking purposes. If we introduce usage analytics tools (such as Google Analytics) for service improvement, we will update this policy and notify users. If cookies are disabled, some features such as maintaining the logged-in state may be restricted.
Hold markers for operations with unknown outcomes
If the outcome of a comment reply, a comment status change or deletion, or a TikTok DM reply cannot be confirmed, we store a hash identifying the operation target and the time the hold was recorded in the browser's local storage to help avoid duplicate operations. The hash is derived from values that distinguish the client company, social media connection, and target comment or conversation. These markers do not contain message bodies, drafts, names, credentials, or the original identifiers themselves, and are not sent to this service's server. Hashing alone does not guarantee anonymization or encryption. These records are separate from the temporary display cache of comments and DM information.
Markers are not automatically deleted by reloading or closing the page, logging out, disconnecting a social media account, or the passage of time. After checking the state at the operation's destination, users can remove the marker for that target by acknowledging the hold in the interface. For comment status changes and deletions, users must retrieve the list again before acknowledging. Retrieving data or acknowledging a hold does not by itself establish successful delivery to the social media platform. Old markers may remain in storage even when a reconnected account is treated as a new connection. Users can also clear this site's stored data in browser settings and reload the page.
Markers are shared between tabs using this site in the same browser profile. Storage is not separated by logged-in user, so another user of a shared browser may see a hold for the same operation target. When using a shared browser, check the state at the operation's destination before acknowledging a hold.
If browser storage is denied or a write fails, for example because storage is full, the hold is kept in the current page's memory; persistence across reloads or other tabs cannot be guaranteed. If removing a stored marker fails, the hold can be acknowledged on the current page but may return after a reload. This safeguard does not completely prevent duplicate operations, including across devices or browsers, after stored data is cleared, after reloading before an unknown outcome is recorded, or during simultaneous operations in multiple tabs.
9. International Data Transfers
The database of this service is stored in Supabase's Tokyo region (ap-northeast-1). Because content delivery passes through Vercel's global CDN, some static assets and request processing may pass through servers outside Japan.
10. About the Use of AI
This service uses third-party generative AI (LLM) services for purposes such as assisting in the generation of draft posts, transcribing video content, generating reply drafts for comments and DMs, and generating draft text for monthly reports. When generating reply drafts, when a user chooses to create them, we send to the AI service the body of the comment concerned (Instagram, YouTube, TikTok) or the body of the DM message (Instagram, TikTok), and the name of its author or sender. Reply drafts for comments are also created automatically when a user displays unreplied comments on the comments screen (including shortly before they appear on the screen), and the same information is sent to the AI service in that case as well. For comment reply drafts, we also send the client company name. If the user has registered AI information about the client company (such as its industry, business description, region, tone of voice, expressions to avoid, actions it wants viewers to take, and FAQs), it is also sent when generating comment reply drafts. If the organization's common rules are registered, they are also sent when generating reply drafts for comments and DMs. When generating draft text for monthly reports, when a user creates a report (including when the user chooses to regenerate the draft), we send to the AI service aggregated Instagram figures (reach, number of saves, engagement rate, number of followers, post views, etc., together with the values for the previous month) and, for the top posts by views, the posting date, figures, post type, and the beginning of the post text (up to 120 characters, excluding usernames beginning with @). We do not send the client company name, follower demographics, comments, or DMs. For generating reply drafts and monthly report drafts, we currently use the Gemini API of Google LLC. This service selects and uses paid plans (such as a paid tier) under which data sent via the API is not used by the AI service provider for the purpose of training generative AI models. The provider of this service (lacks japan Co., Ltd.) also does not use this data to train AI models. We do not create our own metrics (such as scores) from data obtained through YouTube API Services.
The AI service providers currently in use are as described in "3. Provision to Third Parties". The AI services used may change in the future in line with technological progress, in which case we will update this policy and notify users.
Generated results may contain inaccurate content (so-called hallucinations). Before publishing or using generated results, users should verify and edit the content at their own responsibility.
11. About Data Obtained on Behalf of Others
The primary users of this service are social media management agencies, which obtain and process the information of client companies (and their end users such as followers) on their behalf. The agency bears the primary management responsibility in its relationship with end users, and the provider handles data within the scope of the processing entrusted to it by the agency.
The agency bears responsibility for compliance with the Act on the Protection of Personal Information and other related laws and regulations with respect to information obtained from end users.
11-2. Use of YouTube API Services
(1) Use of YouTube API Services
This service uses YouTube API Services. For the handling of information obtained or used through YouTube API Services, please also refer to the Google Privacy Policy (http://www.google.com/policies/privacy) in addition to this policy. lacks analytics' use of information received from Google APIs will adhere to Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
(2) YouTube information we obtain
Only when a user (a social media management agency) connects a client company's YouTube channel to this service, we handle the following information. It consists of information obtained from YouTube through Google OAuth authorization and information that a user enters in this service to publish videos.
- The identifier of the connected Google account
- Channel information (channel name, channel ID, handle, description, profile image, subscriber count, video count, total view count)
- List of videos and their information (title, description, thumbnail, publication date and time, duration, view count, like count, comment count)
- YouTube Analytics figures (views, engaged views (times viewers kept watching instead of leaving right at the start), watch time, average view duration, average percentage of a video watched, subscribers gained and lost, audience retention (the share of views still watching at each point in a video), the type of video (Short, regular video, or live stream) and figures by type, views and watch time by traffic source (such as YouTube search and suggested videos), views by search term when a video was viewed from YouTube search, views and watch time split by whether the viewer is subscribed to the channel, the percentage of viewers by age group and gender, and views by country). Figures by age group, gender, country, traffic source, search term, and subscription status are aggregated by YouTube and do not include information that identifies individual viewers
- Comments (comment text, the author's display name and channel ID, posting date and time, replies, publication status). When a user replies to a comment from this service, publishes a comment held for review or flagged as likely spam, or rejects (hides) a comment, that action is sent to YouTube
- Information that a user enters or selects when publishing a video from this service (title, description, tags, category, privacy setting, made-for-kids setting, and a declaration of whether the video contains AI-generated content), and the video file and thumbnail image. These are used to send them to YouTube. What the user entered or selected is not information obtained from YouTube; it is stored in this service as a record of scheduled and published posts. Records of posted videos (the YouTube video ID and the link to the video) are stored to manage posts
- Google authorization tokens (access tokens and refresh tokens, stored encrypted)
(3) Purposes of use
YouTube information we obtain is used solely to enable users to operate the YouTube channel of the connected client company (such as displaying analytics, publishing videos, and handling comments). It is not used for advertising delivery or sale to third parties. This service does not allow third parties to serve advertisements or other content.
(4) Sharing
YouTube information is handled by the following providers to the extent necessary to provide this service. We do not provide it to third parties for advertising or marketing purposes.
- Google LLC (provider of YouTube API Services; the source of the information and the destination of videos, replies, and changes to comment publication status)
- Supabase, Inc. (database, stored in the Tokyo region)
- Vercel Inc. (web application hosting and relay of communications)
- Google LLC (generative AI "Gemini"; when a user creates reply suggestions for comments, and when a user displays unreplied comments on the comments screen, including shortly before they appear on the screen, the comment text, the author's name, and the name of the client company replying are sent)
(5) Retention period
The retention periods for YouTube information are as follows.
- Daily statistics obtained from YouTube API Services are deleted within 30 days of acquisition
- Records of posted videos (video ID and link to the video) are deleted within 30 days of posting (the record that the post was published remains)
- YouTube comments are not stored in this service's database. They are retrieved from YouTube when the comments screen is opened or the client company is switched, and are kept temporarily in the memory of the user's browser for display (in addition to the client company being displayed, data for other client companies that the user may switch to may be retrieved in advance; all of it is cleared when the page is reloaded or closed)
- This service checks every day whether the connection is still valid, and when the check succeeds, it updates the channel name and handle of the connected channel to the latest information
- If the connection cannot be checked for an extended period and more than 25 days have passed since it was last successfully checked, the connection is automatically disconnected and the information described in (6) is deleted
- Connection information (authorization tokens and the identifier of the Google account) and channel information (such as channel name and handle) are deleted when the connection is disconnected or revoked (the timing is as described in (6))
(6) Revoking access
Users of this service can disconnect a YouTube channel from the settings screen of this service. In addition, the holder of the Google account that authorized the connection can revoke this service's access at any time via the Google security settings page (https://security.google.com/settings/security/permissions).
- If disconnected from the settings screen of this service: we immediately request Google to revoke the access token, and delete on the spot the connection information, channel information, daily statistics, and records of posted videos for that channel stored in this service. Anything that could not be deleted on the spot is deleted within 7 days at the latest
- If revoked via the Google security settings page: this service checks every day whether the connection is still valid, and deletes the same information when it detects the revocation. Deletion takes place within 30 days of the revocation
(7) Deletion requests
Users or client companies may at any time request deletion of the YouTube information stored in this service via "13. Contact". We delete it within 7 days of receiving the request, including identity verification and confirmation of the agency relationship; for the procedure, see "Data Deletion Procedure". If a user disconnects YouTube from the settings screen of this service, the information is deleted on the spot as described in (6). Deletion in this service does not affect data on YouTube (such as videos or comments already posted to YouTube). To delete data on YouTube, please use a YouTube application or similar means.
(8) Cookies and contact
For the use of cookies and local storage, see "8. Cookies and Local Storage"; for questions or complaints about this service's privacy practices, see "13. Contact".
(9) Protection of YouTube information
YouTube information is always sent and received over encrypted connections (HTTPS). Google authorization tokens are encrypted with AES-256-GCM before they are stored. The database is separated by each user's organization, and a channel's information can be viewed only by users of the organization that connected the channel. However, with the consent that users give by agreeing to this policy, our administrators can see the name and handle of a connected channel to manage accounts and plans. Our administrators access any other YouTube information only when a user asks us to investigate a specific problem, for security purposes such as investigating a bug or abuse, or to comply with applicable law.
12. Applicable Laws
This policy complies with Japan's Act on the Protection of Personal Information. Where a user is a resident of the EU, we operate with reference to the intent of the GDPR; where a user is a resident of the State of California, USA, we operate with reference to the intent of data protection laws such as the CCPA.
In addition, we comply with the terms of use and related policies of each connected platform.
- Meta Platform Terms / Meta Developer Policies (Instagram / Threads)
- TikTok Developer Terms of Service / TikTok API Services Terms
- YouTube API Services Terms of Service / YouTube API Services Developer Policies
- Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy)
- Google Gemini API Terms / Generative AI Prohibited Use Policy
13. Contact
For inquiries regarding this policy, please contact us at the following.
- Provider: lacks japan Co., Ltd.
- Representative: Shunya Hamada
- Address: 2-17-27-401 Makishi, Naha City, Okinawa 900-0013, Japan
- Corporate number: 9360001034333
- Contact email: r-oosaki@lacks-japan.co.jp