Addness Privacy Policy

Established: November 7, 2025

Last revised: October 23, 2026 (effective the same day)

ADDNESS Inc. ("the Company") sets forth this Privacy Policy ("this Policy") regarding the handling of personal information and related data of customers ("Customers") who use the Addness service, including its website and applications ("the Service").

1. Personal Information We Collect

(1) Information provided directly by Customers

When registering to use the Service and in other similar situations, Customers may provide the following information.

Basic information

• Name, date of birth, gender, and other personal profile information
• Contact information such as email address, phone number, and address
• Company name, department, title, and other affiliation information
• Account information such as user IDs
• Authentication information (passwords are managed by the authentication provider and are not retained by the Company)
• Company size and consultation details entered in the document request and consultation forms

Payment information

• Payment-related information (card numbers and other payment details are processed by the payment provider and are not retained by the Company)
• Bank account information (when registered as the payout destination for affiliate partner commissions)
• Billing address
• Information about purchases made through app stores (such as purchase tokens, order numbers, transaction IDs, purchased products, and subscription status and expiration)

Service usage information

• Tasks and project content
• Uploaded files and documents
• Comments, messages, and other communication information
• Camera video, microphone audio, and screen-sharing data transmitted when a user enables those features in a Huddle or other real-time communication feature
• Inputs to AI functions and generated outputs

(2) Information obtained from third parties

If Customers permit integration with external services, the Company may obtain the following information.

• User IDs of external services
• Basic information on external services, such as name and email address
• Integrated data such as calendar information and task information
• Authentication information such as OAuth tokens

(3) Information collected automatically

When Customers use the Service, the Company automatically collects the following information.

Access information

• IP address
• Referrer information
• User agent information such as browser and OS
• Access date/time and usage duration

Device information

• Device ID and device identifiers
• Screen resolution and language settings
• Mobile app version

Behavior information

• Page transitions and click activity
• Feature usage frequency and usage patterns
• Search keywords and filter settings
• Error logs and performance data
• Opens of emails sent by the Company and clicks on links in those emails

Cookie and similar information

• Cookie IDs
• Session information
• Local storage data

2. Purposes of Use

(1) To provide the Service

• Provide, maintain, protect, and improve the Service
• Create, authenticate, and manage accounts
• Bill and process payments
• Provide customer support and respond to inquiries
• Investigate and respond to violations of the Terms of Service

(2) To improve and develop the Service

• Create and analyze usage statistics
• Develop new functions and improve existing functions
• Optimize UI/UX
• Check AI function behavior, maintain quality, and investigate defects

(3) To ensure safety and reliability

• Prevent and detect unauthorized use
• Investigate and respond to security incidents
• Monitor systems and respond to failures
• Ensure legal compliance and protect rights

(4) To send communications about the Service

• Send requested materials, respond to inquiries and consultation requests, and provide information about the Company's services to those who submit the document request or consultation forms
• Send emails that encourage Customers to start or continue using the Service, and announcements about features and updates
• Improve the content and timing of such communications by aggregating email opens and clicks
• Customers can stop these emails at any time via the unsubscribe link in each email

(5) Other purposes

• Provide Huddles, voice calls, video calls, online meetings, screen sharing, and real-time delivery of video and audio between participants
• Carry out operations incidental to the purposes above

2-1. Handling of Information Obtained from Google APIs

Based on user consent, the Company may obtain information related to Google accounts and Google Drive / Google Sheets through Google OAuth and Google APIs. The information obtained may include Google account identifiers, names, email addresses, profile images, OAuth tokens, Google Drive file IDs and Google Sheets file IDs, file names, sheet names, cell values, update timestamps, and other information necessary to provide the relevant feature for files explicitly selected or authorized by the user through Google Picker or similar methods.

The Company uses information obtained from Google APIs only for the following purposes.

• Authenticate, maintain, and manage Google account connections
• Connect Google Sheets selected by users to goals, dashboards, task management, and AI-assisted features in Addness
• Read, display, summarize, reflect, or update the contents of Google Sheets selected by users
• Provide, maintain, protect, and improve Google integration features
• Check connection status, investigate errors, respond to failures, prevent unauthorized use, and ensure security
• Respond to user inquiries

The Company does not use information obtained from Google APIs for purposes prohibited by the Google API Services User Data Policy or for purposes unrelated to providing, maintaining, protecting, or improving Addness user-facing features.

The Company does not sell information obtained from Google APIs to third parties. The Company provides or transfers such information to third parties only to the extent necessary to provide, maintain, protect, or improve Addness user-facing features, when the user has consented, when required by law, or when necessary to prevent unauthorized use or respond to security issues.

The Company retains information obtained from Google APIs for the period necessary to provide Google integration features. Users may request disconnection of Google integrations, account deletion, or data deletion through the method designated by the Company. Except where retention is required by law or legitimate business needs, information that is no longer necessary will be deleted or anonymized.

The Company implements reasonable security measures to protect information obtained from Google APIs, including encryption in transit, access controls, permission management, and log management.

The Company's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

2-2. Addness Meet Recorder (Chrome extension)

Addness Meet Recorder lets users invite a recording bot from Google Meet, check recording status, and open meeting notes and video in their selected Addness goal or meeting notes folder. The restrictions in this section apply to information obtained through the extension.

Information collected and its purposes

• Addness user identifiers, authentication sessions, and tokens: synchronizing sign-in through Clerk and using Addness APIs with the user's permissions. Authentication tokens are not passed to the Google Meet page.
• The current Google Meet URL and title: inviting the bot to the correct meeting and restoring recording status. The extension does not collect browsing history across all websites.
• Organizations, accessible goals and meeting notes folders, selected destinations, recording job identifiers and status, and result links: selecting a destination, managing recordings, and displaying notes and video.

Recording and service providers

When a user requests recording, Addness servers use Recall.ai to invite a recording bot. The meeting URL, bot name, and information needed to identify the processing job are sent to Recall.ai. Once admitted, the bot records meeting audio and video. Meeting settings may require a host or another authorized participant to admit the bot. The extension itself does not directly capture the device's microphone or screen.

To generate transcripts, Addness may send meeting audio, recordings, and related metadata to contracted external AI or transcription services. To generate summaries and meeting notes, Addness may send transcripts and meeting information to contracted external AI services or AI processing infrastructure. Retention and usage restrictions depend on the applicable contracts, settings, and retention policies.

Storage and deletion

Information needed for authentication and recording recovery, together with organization and destination preferences, is kept in Chrome extension local storage. Recordings and meeting notes are saved and displayed according to the selected Addness destination and its existing access permissions. Recording media on Recall.ai is configured with a retention period of up to 7 days (168 hours). Videos and notes saved in Addness follow this policy's storage and deletion rules rather than that retention period.

Minimizing the panel, closing the Meet tab, or uninstalling the extension does not stop a bot already recording in a meeting. To end recording early, the user who started it can request a stop from the panel's secondary menu. Uninstalling the extension does not delete information stored in Addness. Requests to delete information can be sent to the privacy contact in this policy. Extension usage questions can also be sent to development@team.addness.co.jp.

Chrome Web Store Limited Use requirements

Our use and transfer of information obtained through this extension adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. We restrict use to providing, maintaining, protecting, and improving the recording features described above. We do not sell this information or use or transfer it for advertising, creditworthiness, lending, or purposes unrelated to this extension.

Transfers to third parties are limited to what is necessary to provide or improve this single purpose, comply with law, prevent fraud or abuse, or complete a merger, acquisition, or sale of assets after the user's explicit prior consent. Our personnel and service providers may read this information only with the user's explicit consent to read specific information, when aggregated and anonymized for lawful internal operations, when necessary for security, or when required to comply with law.

3. Provision of Personal Information to Third Parties

(1) Cases where information may be provided

The Company may provide personal information to third parties only in the following cases.

With Customer consent

• When explicit consent has been obtained
• When the purpose of use has been explained and opt-in consent has been obtained

Provision to contractors

• Data center operators
• Cloud service providers
• Payment processors
• Customer support contractors

When required by law

• Legally required disclosure requests
• Inquiries from investigative authorities
• Court orders

Other legitimate grounds

• When necessary to protect life, body, or property and it is difficult to obtain consent
• When necessary for public health or the sound development of children and it is difficult to obtain consent
• In the event of merger, business transfer, or similar transaction

(2) Information not provided

As a general rule, the Company does not provide the following information to third parties.

• Authentication information such as passwords
• Data combined with information belonging to other Customers

(3) Processing by real-time communication providers

To provide Huddles and other real-time communication features, the Company uses LiveKit (LiveKit Cloud) to process camera video, microphone audio, screen-sharing data, participant information, room information, and communication quality information.

Camera video is processed for real-time communication. Unless a video-recording feature is explicitly provided and started, the Company's Huddle recording feature does not retain camera video as a recording. Participant, room, communication quality, and other metadata may be handled in accordance with applicable contracts, settings, and retention policies.

3-1. Contractors and External Services

To the extent necessary to provide the Service and its communication features, the Company may have the following external services or contractors handle information.

Anticipated contractors and external services

• Cloud infrastructure providers
• Storage, backup, monitoring, and log management services
• Voice call, online meeting, screen sharing, and recording platforms
• Transcription services
• AI models, AI APIs, and AI processing platforms
• Authentication, notification, email, payment, customer support, and analytics services

Information that may be transmitted or processed

• Account information, organization information, and permission information
• Chats, comments, attachments, goals, tasks, and meeting information
• Recordings, audio, screen sharing, transcripts, AI summaries, and generated outputs
• Communication metadata, logs, device information, and error information

Management measures

When selecting contractors or external services, the Company confirms confidentiality, information management, access restrictions, management of subcontracting, retention periods, deletion, restrictions on use, international transfers, security levels, and other necessary matters, and manages them in a reasonable manner.

List of contractors and external services

The main external services to which the Company entrusts the handling of information, or which the Company uses, are as follows.

Cloud infrastructure

• Provider or service: AWS (S3: ap-northeast-1), Vercel (hosting), Cloudflare (CDN and protection; storage of recorded video (R2))
• Information transmitted: account information, communication content, attachments, audio and video recordings, logs
• Purpose: service provision, storage, delivery, backup
• Retention and restrictions on use: in accordance with contracts, settings, and retention policies

Voice call platform

• Provider or service: LiveKit (LiveKit Cloud)
• Information transmitted: audio, video, screen sharing, participant information, room information, communication quality information
• Purpose: provision of Huddles, calls, and meetings; quality management
• Retention and restrictions on use: Camera video is processed for real-time communication and, unless a video-recording feature is explicitly provided and started, is not retained as a recording by the Company's Huddle recording feature. Participant information, room information, communication quality information, and other metadata are handled in accordance with contracts, settings, and retention policies

Transcription

• Provider or service: OpenAI (OpenAI API; United States; API inputs are not used for training under the contractual terms; retained for up to 30 days for abuse monitoring)
• Information transmitted: audio, recordings, metadata
• Purpose: transcript generation
• Retention and restrictions on use: in accordance with contracts, settings, and retention policies

AI summaries

• Provider or service: OpenAI (OpenAI API; United States; API inputs are not used for training under the contractual terms; retained for up to 30 days for abuse monitoring)
• Information transmitted: transcripts, chats, comments, goal information
• Purpose: generation of summaries, meeting minutes, and suggestions
• Retention and restrictions on use: in accordance with contracts, settings, and retention policies

Meeting bot

• Provider or service: Recall.ai (Tokyo region; media retained for up to 7 days). For transcription, the Company uses Speechmatics (Speechmatics Ltd.) through Recall.ai or Recall.ai's own transcription feature
• Information transmitted: meeting URL, bot name, meeting audio and video
• Purpose: meeting recording; generation of transcripts and meeting minutes
• Retention and restrictions on use: Recorded media is deleted from Recall.ai after a retention period of up to 7 days (168 hours) (see Section 2-2). The recording bot and recorded media are processed in the Tokyo region. Transcription is processed within the EU when Speechmatics is used, and in the United States when Recall.ai's transcription feature is used

Notifications

• Provider or service: APNs, FCM (via Expo Notifications on mobile), email, etc.
• Information transmitted: notification destination, part of the notification content, device information
• Purpose: notification delivery
• Retention and restrictions on use: in accordance with contracts and settings

Authentication

• Provider or service: Clerk
• Information transmitted: account information, authentication information
• Purpose: login and authentication
• Retention and restrictions on use: in accordance with contracts and settings

Integrated services

• Provider or service: LINE, GitHub (when the user enables the integration)
• Information transmitted: LINE user ID and profile; GitHub tokens and repository information
• Purpose: LINE integration; repository connection
• Retention and restrictions on use: in accordance with each provider's terms

Access analytics

• Provider or service: Google Analytics (Google LLC; United States)
• Information transmitted: type of screen viewed, cookie ID, browser, OS, and device type, language settings, IP address, and other technical information
• Purpose: understanding usage and improving the Service
• Retention and restrictions on use: as described in Section 5(2)

Error monitoring

• Provider or service: Sentry (Functional Software, Inc.; United States)
• Information transmitted: error information, user ID, device and browser information, IP address, part of the operation history, logs
• Purpose: investigating failures, maintaining quality, and assessing the scope of impact
• Retention and restrictions on use: in accordance with contracts and settings

Email delivery

• Provider or service: Resend (United States)
• Information transmitted: name, email address, company name, phone number, company size, and consultation details entered in the document request and consultation forms; name, email address, company name, and role entered in the AI Proficiency Assessment; and, for Customers registered with the Service, email address, registration date, and subscription status (such as in trial, subscribed, or canceled, including the plan and number of seats)
• Purpose: sending requested materials, responding to inquiries and consultation requests, delivering emails about the Company's services, delivering notification emails about the Service, and notifying the Company's internal inquiry desk
• Retention and restrictions on use: in accordance with contracts and settings (informational emails can be stopped at any time via the unsubscribe link in each email)

3-2. Transmission to External AI Services

To provide transcription, AI summaries, meeting minutes generation, search, classification, suggestions, answer generation, and other AI functions, the Company may transmit information that users input, send, speak, share, or upload to external AI services under contract with the Company and have those services process it.

Information transmitted to external AI services may include communication content, recordings, transcripts, attachments, goals, tasks, comments, chats, meeting information, and other information that users or organizations designate as subject to AI processing.

When using external AI services, the Company limits the information transmitted to the extent necessary to provide the relevant function.

The Company uses external AI services only under contractual terms or settings under which users' inputs, communication content, and similar information are not used to train or improve the external AI service's models.

However, logs and other information may be retained for a certain period in accordance with the external AI service's specifications, contracts, settings, security measures, or legal requirements. Details such as the specific external AI services used, the processing performed, retention, restrictions on use, and handling in foreign countries are provided in a separate schedule, in notices within the Service, on settings screens, in notifications when a function is used, or by other methods determined by the Company.

4. Joint Use of Personal Information

The Company does not jointly use personal information. If the Company begins joint use, it will publish in this Policy, in accordance with applicable law, the items to be jointly used, the scope of joint users, the purposes of use, and the person responsible for management.

5. Use of Cookies and Similar Technologies

(1) Purposes of using cookies

• Maintain login status
• Identify users
• Ensure security
• Analyze usage

(2) Third-party cookies

To understand and improve how the Service is used, the Company uses the access analytics tool "Google Analytics" provided by Google LLC and uses its cookies. Google Analytics runs on screens of www.addness.com (including screens displayed inside the mobile app, but excluding screens such as login, invitations, authorization of external service integrations, and screens shown after payment is completed) and does not run in the desktop app.

The Company removes URL query strings, IDs, tokens, and similar data from the screen information sent to Google Analytics and replaces it with fixed names that represent the type of screen. The Company does not send user-provided data such as names or email addresses. In the Company's tag configuration, Google signals and ads personalization are disabled, and the use of cookies for advertising purposes is denied. In the Google Analytics settings, the collection of granular location and device data is disabled. Cookies expire one year after the first visit and are not extended on each access.

For how Google handles data, please see Google's policy (https://policies.google.com/technologies/partner-sites).

The Company does not use cookies from customer support tools. Programs that transmit information from users' devices to external operators are listed in Section 5-1.

(3) Cookie management

Customers can disable cookies through browser settings, but some functions of the Service may become unavailable.

5-1. Programs That Transmit Information to External Operators

The SDKs, cookies, tags, and similar programs that transmit information from users' devices to external operators in connection with use of the Service are as follows.

Authentication SDK

• Recipient: Clerk (Clerk, Inc.)
• Information transmitted: account information, authentication information, device information, etc.
• Purpose at the Company: login and authentication
• Purpose at the recipient: provision of authentication services, prevention of unauthorized use, etc.

Notification SDK (mobile app)

• Recipient: Expo Notifications (Expo, Inc.; backed by Apple APNs / Google FCM)
• Information transmitted: push notification tokens (equivalent to device identifiers), part of the notification content, etc.
• Purpose at the Company: notification delivery
• Purpose at the recipient: provision of notification services, etc.

Analytics tool (web and screens displayed in the mobile app)

• Recipient: Vercel Speed Insights (Vercel Inc.)
• Information transmitted: performance information such as page load speed
• Purpose at the Company: measuring and improving display performance
• Purpose at the recipient: provision of measurement services, etc.

Access analytics (web and screens displayed in the mobile app)

• Recipient: Google Analytics (Google LLC)
• Information transmitted: type of screen viewed, cookie ID, browser, OS, and device type, language settings, IP address, and other technical information
• Purpose at the Company: understanding usage and improving the Service
• Purpose at the recipient: provision of measurement services, etc.

Error monitoring (web and screens displayed in the mobile app)

• Recipient: Sentry (Functional Software, Inc.)
• Information transmitted: error information, user ID, device and browser information, IP address, part of the operation history, logs
• Purpose at the Company: investigating failures, maintaining quality, and assessing the scope of impact
• Purpose at the recipient: provision of monitoring services, etc.

App updates (mobile and desktop)

• Recipient: Expo Updates (Expo, Inc.) / electron-updater
• Information transmitted: app version, build information, OS information
• Purpose at the Company: delivery of app updates
• Purpose at the recipient: provision of update delivery services, etc.

Speech recognition (mobile app; OS-provided APIs)

• Recipient: Apple (Siri API) / Google (Speech-to-Text)
• Information transmitted: audio data at the time of voice input (the Company does not store audio data on its servers)
• Purpose at the Company: voice input in chat, comments, and similar features
• Purpose at the recipient: provision of speech recognition services, etc.

Payment SDK (web)

• Recipient: Polar
• Information transmitted: information required for payment (card information is processed by the payment provider)
• Purpose at the Company: payment for paid plans
• Purpose at the recipient: provision of payment services, etc.

Payments (Android app)

• Recipient: Google Play Billing (Google LLC)
• Information transmitted: organization ID, the product being purchased, etc. (card and other payment details are processed by Google and are not obtained by the Company)
• Purpose at the Company: payment for paid plans in the Android app and verification of subscription status (using the purchase token issued by Google after the purchase)
• Purpose at the recipient: provision of payment services, etc.

Payments (iOS app)

• Recipient: App Store In-App Purchase (Apple Inc.)
• Information transmitted: organization ID, the product being purchased, etc. (card and other payment details are processed by Apple and are not obtained by the Company)
• Purpose at the Company: payment for paid plans in the iOS app and verification of subscription status (by receiving transaction information such as purchases, renewals, and refunds from Apple)
• Purpose at the recipient: provision of payment services, etc.

External integrations configured by the user

• Recipient: MCP servers and other external services connected by the user
• Information transmitted: information the user chooses to send through the integration feature
• Purpose at the Company: provision of the functions selected by the user
• Purpose at the recipient: in accordance with the specifications of the connected service

6. Retention Period of Personal Information

(1) General retention principles

• During the service contract period: retained continuously
• After cancellation: continues to be retained after the end of the contract term (you can continue where you left off by subscribing again)
• After deletion of an organization: a deleted organization cannot be opened by anyone and cannot be restored. Data belonging to the organization is not erased immediately and is retained (as described in (3))
• After deletion of an account: accounts can be deleted from My Page in the Service. A deleted account cannot be used by anyone and cannot be restored (any organization to which only you belong is deleted at the same time). Account information is not erased immediately and is retained (as described in (3))
• Goals and other items individually deleted by users: permanently erased 30 days after deletion (restorable within those 30 days)
• Records required to be retained by law: for the period prescribed by law

(2) Retention period by data category

• Account information: retained continuously during the service contract period, and after account deletion retained as described in (3)
• Usage history: 3 years from the last use
• Payment information: 7 years as required by law
• Inquiry history: 3 years after completion of response
• Cookie data: up to 1 year
• Camera video: processed as necessary for real-time delivery to participants and, unless a video-recording feature is explicitly provided and started, not retained as a recording by the Company's Huddle recording feature

(3) Data after deletion of an organization or account

Data of organizations and accounts deleted on or after October 17, 2026 is handled as follows.

• Deleted organizations and accounts cannot be opened by anyone and cannot be restored. As a rule, we also do not restore them from backups
• The data is not erased immediately after deletion and is retained by the Company
• Except where necessary, such as in response to a request based on laws and regulations, the Company does not view the contents of the retained data
• The retained data may be used to improve the quality of the Service in a form that does not use information specific to the customer (it is not used to train AI models)
• If you wish the data to be completely deleted, please contact us individually through the contact point in Section 12. We will respond to your request

Data received through Google integrations (Google API Services) is excluded from this handling and is deleted as before, in accordance with the Google API Services User Data Policy, including the Limited Use requirements.

Data of organizations and accounts deleted before October 17, 2026 is handled under the previous provision (erased upon completion of deletion processing, with backups expiring within 7 days).

7. Security Measures

(1) Organizational measures

• Appointment of a person responsible for personal information protection
• Regular training for employees
• Periodic audits

(2) Human measures

• Execution of confidentiality agreements
• Management of access permissions
• Immediate removal of access rights for departing personnel
• Implementation of education programs

(3) Physical measures

• Entry/exit control at data centers
• Storage of documents in lockable cabinets
• Measures to prevent device theft
• Appropriate disposal of documents

(4) Technical measures

• Encryption of data in transit and at rest
• Firewall deployment
• Monitoring of unauthorized access
• Regular security updates
• Logging and monitoring of access records
• Implementation of multi-factor authentication

8. Requests for Disclosure and Other Rights

(1) What may be requested

Customers may make the following requests regarding their personal information.

• Notification of purpose of use
• Disclosure
• Correction, addition, or deletion
• Suspension of use or erasure
• Suspension of third-party provision

(2) How to submit a request

• Submit the prescribed request form with identity verification documents
• Contact point: privacy@team.addness.co.jp
• Fee: JPY 1,000 per disclosure request

(3) Cases where a request may be denied

• When identity cannot be verified
• When complying would violate laws
• When it may infringe the rights of others

9. International Transfers

(1) Countries or regions to which data may be transferred

Customer personal information may be transferred to the following countries or regions.

• United States (use of external services such as AI services, authentication, error monitoring, access analytics, hosting, notifications, payments, and meeting bot transcription)
• European Union (use of Speechmatics, the transcription service for the meeting bot)

The Cloudflare R2 storage used for recorded video is shown in the Cloudflare dashboard with the location Asia-Pacific (APAC); the specific country in which the data is stored has not yet been identified.

(2) Safeguards for transfer

• Establishment of a framework that conforms to the standards prescribed by the rules of the Personal Information Protection Commission, through the execution of data processing agreements (DPAs) with recipients
• Securing appropriate safety measures
• Periodic review of the handling of personal information by recipients

10. Children's Personal Information

Users under 16 years old must use the Service with the consent of a parent or guardian. If the Company discovers that it has obtained personal information from a person under 16 without the consent of a parent or guardian, the Company will take measures such as suspending use of the relevant account and deleting the personal information.

11. Changes to the Privacy Policy

(1) Change procedures

• Material changes: notified 30 days in advance
• Minor changes: announced on this website
• Additions or corrections to disclosed matters and other changes that do not disadvantage Customers: take effect immediately upon publication on this website

(2) Consent to changes

If Customers continue using the Service after the changes take effect, they are deemed to have agreed to the revised Policy. However, for changes that require the individual's consent under applicable laws, continued use alone will not be deemed consent, and the Company will separately obtain the required consent.

12. Contact Information

Inquiries regarding personal information

ADDNESS Inc. Attention: Personal Information Protection Manager

• Address: Yotsuya Tosei Building 5F, 4-3-50 Yotsuya, Shinjuku-ku, Tokyo 160-0004, Japan
• Representative: Kota Mikami, Representative Director
• privacy@team.addness.co.jp

Complaint desk

If you have a complaint regarding the handling of personal information, please contact the inquiry desk above.

13. Personal Information Protection Principles

The Company protects personal information in accordance with the following principles.

• Legal compliance: comply with the Act on the Protection of Personal Information and other applicable laws
• Proper acquisition: obtain personal information through lawful and fair means
• No use beyond stated purposes: use personal information only within the scope of stated purposes
• Security management: prevent unauthorized access, loss, destruction, falsification, and leakage
• Continuous improvement: continuously review and improve our privacy protection framework

If you have any questions about this Policy, please feel free to contact us.