Ai4Growth

Ai4Growth — Privacy Policy

Version 1.0 · Effective date: 2026-10-27

1. Who is responsible

HUANG JIANJUN, the individual operator of Ai4Growth in China, is responsible for account, service administration, usage and support processing described here. Contact jerryhuang@wantai.ai for privacy questions and rights requests.

For materials processed under an organisation's instructions, that organisation may determine the purpose of the research and have its own responsibilities. The actual activity and applicable law determine each party's role. A software rights holder is not automatically responsible for every processing activity.

2. Information processed

You supply account and research material. Enabled source services supply source records. Payment providers supply transaction records when used.

3. Purposes and applicable grounds

We process information to create and secure accounts, provide requested research functions, keep usage and transaction records, resolve support and rights requests, prevent misuse and meet applicable obligations.

Depending on applicable law and the activity, processing relies on performing a requested service or contract, legal obligations, a permitted legitimate interest or consent where required. Source collection and organisational instructions must have an appropriate lawful basis; being publicly visible is not a universal permission. Optional marketing and unrelated secondary uses are not authorised merely by using the service.

4. AI processing

Requested AI features send the material needed for the task to the external Intern model service. This may include prompts, conversation excerpts, selected source or research material, and images for image analysis.

Ai4Growth does not itself use customer research questions, conversations, uploads, collected content or outputs for model training, human evaluation or product improvement. This operator-level rule is not a promise that an upstream provider has zero retention or no secondary use.

Intern's published general service terms permit use of conversation context after de-identification for model evaluation and optimisation. The operator has no separate API data-protection agreement overriding those published terms. The exact application of the provider's published terms to a particular API use remains subject to those terms; no promise of upstream zero retention or no model training is made. Review those terms before submitting material; do not use a model feature where the provider's processing is incompatible with your authority or requirements. Contact us about the applicable processing arrangement before submitting confidential or sensitive material.

Provider notices: Intern Service Terms and Intern Privacy Policy.

5. Recipients and international processing

Recipient or categoryPurpose and relevant data
Oracle Cloud InfrastructureApplication and worker hosting in the United States; requested service content and operational records
Supabase managed servicesAccount authentication, database and uploaded-file storage; the configured project region is Tokyo, Japan
Intern external model serviceRequested model analysis; prompts and selected task material as described above, under the provider's own processing arrangements
ResendAccount verification and transactional emails, including recipient address and email contents
Enabled collection services and source platformsRetrieval for the selected operation; relevant queries, platform identifiers and retrieval parameters
Waffo Pancake, where identified at checkoutMerchant-of-record payment, receipts, transaction support and refunds; subject to its transaction privacy notice
Authorised operational/support personnel or legally required recipientsLimited access for support, security, legal obligations or protecting rights

Data can be processed outside the country where you live, including the United States, Japan and locations used by external providers. Providers' purposes, retention and legal obligations may differ from ours. Contact us for the recipients and transfer arrangements relevant to a proposed use. A location listing does not by itself establish a particular contractual transfer safeguard. Do not submit material that requires an arrangement not yet agreed for your use.

Provider privacy notices: Oracle Services Privacy Policy, Supabase Privacy Policy and Resend Privacy Policy.

6. Storage and retention

Account and workspace records are retained while the account/workspace is maintained. Research questions, source records, files and saved results remain available as part of that workspace until removed through an applicable request or retention action. Signing out or closing a browser does not delete server-held research.

A refresh-session cookie has a maximum age of 30 days; access-session state uses browser session storage. Saved research form preferences can remain in browser local storage until cleared. You can clear site storage in your browser, which may sign you out or remove saved preferences. Email-verification credentials are valid for 24 hours; credential expiry is not a promise that all related account records are deleted at that time.

Operational database backups are configured to retain the latest seven successful backup sets, rather than a guaranteed seven-calendar-day window. Access/error logs and container logs rotate under their configured time or capacity rules. Recovery and incident copies may need separate handling. The 180-day validity of purchased credits is not a personal-data retention period.

Usage and transaction records are retained as necessary to account for usage, resolve the relevant complaint or dispute and meet applicable recordkeeping duties. We assess continued retention against those purposes. An append-only accounting record is not a reason to keep unrelated research content indefinitely.

Contact us to request removal, restriction or account closure. Requests are handled individually; there is no automatic one-click account deletion. Where information must be retained, we explain the reason and relevant limits. Deleting active information does not necessarily erase a backup or provider-held copy at the same moment. Required restrictions and removal must also be addressed when restoring a backup.

7. Your rights and choices

Depending on applicable law, you may request information, access, correction, deletion, restriction, portability, objection or withdrawal of consent, and complain to the competent authority. Send the relevant account email or record/task reference to jerryhuang@wantai.ai. We verify requests proportionately, apply the response periods required by law, and explain limits or the relevant organisational contact when another party controls the processing.

Do not email passwords, full financial-account details or government identity documents without a justified secure verification process. You may stop requesting optional model/source operations. Withdrawal of consent does not reverse prior lawful processing or remove other applicable retention duties.

8. Security, children and changes

We use authenticated workspace access controls, transport protection and uploaded-file checks. These measures do not guarantee absolute security. Report a suspected security or privacy issue to the contact above.

The service is intended for people with the legal capacity required for its use and is not directed to children. Research/source records may nevertheless concern a child or contain sensitive information. Do not deliberately request unlawful profiling or sensitive processing. Contact us if a record requires correction, restriction or removal; an account eligibility rule does not remove rights in source data.

Material changes will be communicated as required. A new notice does not by itself authorise a new purpose or replace consent required by law.

Terms · Pricing · Refunds