Privacy policy

1. Who operates iArchi

iArchi is operated by yehkuanyew, an individual based in Mainland China (“iArchi”, “we”, “us”). This policy covers the iArchi web application at app.iarchi.cloud and our architecture service at mcp.iarchi.cloud, including access through a client you authorize.

For privacy questions and requests, contact yehkuanyew@gmail.com. Google, Supabase, Paddle and any AI client you use also have their own privacy notices for the services they provide.

2. Information we process

• Account information: your Google account identifier, email address, display name and profile picture, an iArchi account identifier, authentication tokens and session information.
• Architecture content: workspaces, models, elements, relationships, views, names, descriptions, properties, diagram geometry and files you import or submit to our cloud service. Model records can include change history and creation or modification times.
• Connection and technical information: network addresses and request metadata needed to deliver the service, authorization details for a connected MCP client, and limited authentication, security and error records generated when operating the service.
• Support correspondence: your contact information and the messages or attachments you choose to send us.
• Billing information, when paid plans launch: customer and transaction identifiers, the purchased plan, subscription status and billing contact information supplied by Paddle. Payment details are entered into Paddle’s checkout; iArchi does not receive or store your full payment-card number or security code.

Please include only information you are authorized to process. Architecture descriptions can contain confidential or personal information; keep credentials, secrets and unnecessary sensitive personal data out of your models and support messages.

3. Google sign-in and Google user data

Google is currently our only account sign-in option. You choose your Google account through Google Identity Services or Google’s OAuth sign-in flow. Supabase Auth verifies the credential and creates or signs you into your iArchi account. We do not receive your Google password.

We access your basic Google identity and profile information: account identifier, email address, name and profile picture. We use it to authenticate you, associate your cloud content with the correct account, display your account identity and respond to account or support requests. This information is stored with your authentication account in Supabase; session credentials are also used by your browser and our service.

Google sign-in does not authorize access to Gmail, Google Drive, Google Calendar, contacts or Google documents. Connecting an MCP client to iArchi is a separate authorization to use your iArchi account and architecture tools.

We share Google identity information only as necessary to provide authentication and account features through our service providers, with your authorization, or where disclosure is legally required. An authorized OAuth client may receive the identity information covered by the scopes you approve. Your Google profile is not added to architecture tool results for AI context.

We do not sell Google user data, use it for advertising or credit decisions, or use it to train AI models. Human access to Google user data is restricted to the cases allowed by Google’s policy, such as support with your affirmative permission, investigating abuse or security incidents, and complying with legal obligations. Our handling of Google user data follows the Google API Services User Data Policy and its Limited Use requirements.

You can remove iArchi’s access from your Google Account connections. Removing a Google connection alone does not delete your iArchi account or cloud models; use the account deletion request process for that.

4. How and why we use information

We use information to provide sign-in and cloud storage, retrieve and update architecture models, execute authorized tool requests, deliver exports, diagnose errors, prevent unauthorized access, provide support and meet legal obligations. When paid subscriptions are available, we also use billing records to provide the plan you purchased and handle cancellations or refunds.

Where a law requires a legal basis, we rely on performing our agreement with you for requested service features; legitimate interests in maintaining a secure and functioning service, where permitted; applicable legal obligations; and your consent where required for an optional feature or a new use of data. You may withdraw consent for consent-based processing without affecting processing that was lawful before withdrawal.

We do not sell or rent your personal information, use your architecture content for advertising, or use account information or cloud models to train an iArchi AI model.

5. Service providers and connected AI clients

• Google: provides the sign-in interface and identity credential. See Google’s Privacy Policy.
• Supabase: provides managed authentication, account and session storage, and OAuth authorization. See Supabase’s Privacy Policy.
• Hosting infrastructure: the web application and architecture service run on a VPS in Los Angeles, United States. Our hosting provider supplies the infrastructure used to store and serve cloud models and operational records.
• Paddle, when checkout is available: acts as merchant of record for purchases it processes and handles payment, applicable transaction taxes, receipts and billing support. See Paddle’s Privacy Notice.
• An MCP or AI client you authorize: may receive the model content, tool results and identity information needed for the permissions and requests you approve. The client may also create, edit or delete model content through authorized tools. Its own terms and privacy settings determine how it processes information after receiving it. If you use ChatGPT, see OpenAI’s Privacy Policy and your account’s data controls.

We do not automatically send your cloud models to an AI provider merely because you sign in. Content is returned when an authorized client requests it, or when you submit it through a feature that sends it. Once a client has received data, disconnecting it does not remove copies that it already holds.

We may also disclose information when required by law, to address abuse or security threats, or to protect legal rights. If the service is transferred to another operator, we will notify users of material changes and continue to protect personal information under the applicable policy.

6. Storage, international access and security

Cloud architecture models are stored in account-specific databases on our United States VPS. Authentication data is stored in our United States Supabase project. Data may also be processed in countries where Google, Paddle or your chosen client operate. The operator is based in Mainland China and may access service data there when necessary for administration or support.

These locations may have different data-protection laws from your country. Where applicable law requires a transfer safeguard or another legal mechanism, that requirement applies to our processing and to the relevant provider’s processing. We do not offer a contractual data-residency commitment in this early-access service.

We use HTTPS in production, verify authentication credentials on protected requests and separate cloud storage by account. Access is limited to what is needed to operate the service. No security measure eliminates all risk; contact us promptly if you suspect an account or data-security issue.

7. Cookies and local browser storage

Supabase authentication uses browser cookies to maintain and refresh your session. iArchi uses local storage for canvas preferences and unsigned-in model drafts. These are used to provide features you request; we currently do not install advertising trackers or third-party marketing analytics in the app.

An unsigned-in draft remains in your browser unless you explicitly import it into your signed-in cloud account. Signing in or signing out does not automatically erase that draft. Export any draft you wish to keep before clearing browser storage. Clearing authentication cookies signs you out of that browser.

The Google sign-in interface can process cookies and technical information under Google’s own policy. If you open a future Paddle checkout, Paddle’s own notice applies to the checkout.

8. Retention and deletion

We keep account information and cloud content while your account is active and as needed to provide the service. Removing an item from a diagram is different from deleting it from the model; changes may remain in model history. Use the deletion request process to request deletion of your account and its cloud data.

We verify account ownership, arrange removal of the authentication account and account-specific cloud models, and tell you when the request is completed or if a specific exception applies. Necessary transaction, security or legal records may be retained for the period required for their purpose or by law. Any retained backup copies are kept out of ordinary use and removed through the applicable backup lifecycle; if a backup is restored, completed deletion requests must be reapplied.

Deletion from iArchi does not delete Google, Paddle or AI-client records, nor drafts and downloaded exports on your devices. Billing records held by Paddle follow Paddle’s retention obligations. Deleting your iArchi account is also separate from cancelling a paid subscription.

9. Your choices and privacy rights

You can export models through ArchiMate XML and diagram views through PNG or SVG, stop using the service, disconnect an authorized client, and request account deletion. Correct Google profile details through Google; contact us if your iArchi account information needs correction.

Depending on your location, you may have rights to access, correct, delete or obtain a copy of personal information; restrict or object to processing; withdraw consent; or complain to the relevant data-protection authority. We do not sell personal information or share it for cross-context behavioral advertising.

Send a request to yehkuanyew@gmail.com from the email associated with your account, describing your request. We may need reasonable verification before disclosing or deleting data. We respond within the period required by applicable law and do not require you to send passwords, access tokens or payment-card details.

10. Age and changes to this policy

iArchi is intended for adults using architecture and software tools. You must be at least 18 and able to enter a binding agreement to create an account. We do not knowingly collect personal information from children. Contact us if you believe a child has supplied personal information.

We update the date on this page when the policy changes. We will provide an appropriate notice for material changes, and obtain further consent before a new use of Google user data where required. Contact yehkuanyew@gmail.com with any questions.