1. Scope and contact information
This policy explains how personal data is processed in connection with the Aistant website, chatbot and connector tools. Legal name, address and privacy contact email of the data controller/operator: [TBD]. Official effective date: [To be confirmed].
This policy covers the features actually enabled and the permissions you grant. Data processing carried out independently by third-party platforms is governed by their own policies.
2. Data we process and its sources
Account and connection data: account identifiers, display names, email addresses (if provided), account connection relationships, login sessions and necessary authorization information that you provide or that is returned by the platform you log in with.
Conversation data: channel or group identifiers, message content, sender identifiers, timestamps, mentioned users and attachment-related information provided by the chat platform through bot events. The actual scope received depends on platform permissions and feature settings.
Feature data: to-dos, assignments and reminders, scheduled messages, bill-splitting records, personal preferences, group descriptions, and plan, allowance and usage records.
Service operations data: technical and operational logs necessary for login, security, debugging and running the service. Logged fields in production, website analytics tools and payment service providers: [To be added after inventory is completed].
Data may be provided directly by you, obtained from platforms you connect, or provided by other group members; sources are not necessarily limited to registered Aistant users.
3. Purposes and legal bases
Data is used for account verification, permission management, message storage and search, AI answers and translation, to-dos and reminders, bill splitting, scheduled sending, plan and allowance management, and necessary security, operations and support.
Each processing activity should have a basis permitted under applicable law. The official version will confirm contract, consent or other applicable bases according to the operating region and actual use cases. Neither this draft nor use of the service itself constitutes blanket consent to all data processing.
If you do not provide necessary data or revoke platform authorization, some login, search or automation features may not be available. Whether you provide optional data should not affect unrelated features.
4. Group monitoring and access scope
Group features may process messages from other members, even if those members do not have an Aistant account. When enabling monitoring, affected members should be informed of the scope of collection, purposes, who has access and how to stop it; the specific notification process must still be confirmed before official launch.
The service limits access through mechanisms such as accounts, group service permissions and platform membership verification. When querying through ChatGPT or other MCP clients, authorized query results are returned to that client.
Disabling one user's monitoring settings does not necessarily stop monitoring enabled by other authorized users for the same group. Leaving a group, revoking permissions, stopping collection and deleting existing data must each be handled separately.
5. AI and attachment processing
To perform the AI features you use, the service may send relevant messages, necessary context and feature data to the configured AI provider. Content returned through MCP tools may also be further processed by the AI client you connect.
In the current implementation, LINE attachments are retrieved from the platform on demand and returned to the client; this path does not write attachment files to local disk. This does not mean that third-party platforms or receiving clients do not store the content.
Models and providers used in production, fields transmitted, provider retention periods and training-use conditions: [To be confirmed based on the production environment and provider agreements]. Until confirmed, we do not claim that all data is anonymized, retained zero days or never used for training.
6. Recipients and cross-border processing
As needed for features, data may be provided to chat platforms, AI/MCP clients you authorize, AI model providers, and contracted vendors providing hosting, database or necessary operations services. Necessary staff access should be restricted by permissions and purpose.
Necessary data may also be provided to comply with applicable law, lawful requests or to handle rights disputes. The official version should list categories of vendors or recipients, actual storage and processing locations, and safeguards required for cross-border processing: [TBD].
7. Retention, deactivation and deletion
Retention periods or criteria for each data category: [To be confirmed, listing accounts, messages, to-dos and bill splitting, schedules, usage, logs and backups separately]. Day limits on history search do not mean data has been automatically deleted from the database.
Disabling monitoring, logging out, unlinking accounts or disconnecting a client should not be understood as deleting existing data. When a deletion request is made, the scope of handling for original messages, derived feature data and shared group data should be confirmed.
Account deletion: You can request deletion in the Account Center or through support. After the request, there is a 30-day cooling-off period (during which you can cancel). When it ends, connected account identities, personal preferences, nicknames, service settings, scheduled messages and private message content are erased. Group messages are shared group records and are retained but disassociated from your account. Billing, subscription and usage records are retained, as required for accounting and by law, in a form no longer linked to your personal data. See “Suspension, termination and account deletion” in the Terms of Service for details.
Identity verification method, processing time and backup purge cycle when support handles deletion requests on your behalf: [TBD]. Copies already received by third-party platforms and clients are handled under their own mechanisms.
8. Cookies and data security
The website uses cookies necessary for login sessions and OAuth authentication, as well as a preference cookie to remember the website language you choose. Whether non-essential analytics or advertising cookies and other tracking technologies are used: [To be inventoried]. If used, their purposes, providers and applicable choices should be added.
We should take technical and organizational measures appropriate to the nature and risk of the data to limit unauthorized access. Encryption, backup and security incident handling in production must still be verified; this draft does not claim any specific certification or guarantee absolute security.
9. Your rights and how to make a request
Under applicable law, you may request to inquire about, review or obtain a copy of your data, correct or supplement it, stop its collection, processing or use, or delete it; applicable limitations and exceptions are handled according to law.
Privacy request email or form, response time and identity verification method: [TBD]. Unregistered members whose messages are involved in group features should also have an available request channel. Where the rights of others or shared data are involved, we should assess the appropriate handling and explain the reasons for our decision.
10. Minors and policy updates
Minimum age, minors' data and the parent/guardian request process: [To be confirmed based on target users and region].
Material changes to this policy should be communicated in a reasonable manner, with update and effective dates indicated. If a new purpose legally requires additional consent, it should be obtained separately. Until officially published, this page will remain marked as a draft that is not yet in effect.