Preparing the next screen, account state, and workspace data.
This page summarizes what Aimesh collects, how that data is used to operate the service, and which infrastructure providers may process it.
Aimesh may collect your Google account email and profile name for authentication, account records in Supabase, API key metadata, billing state, manual payment requests, uploaded slips, and request-level usage logs needed to run the proxy and billing workflows.
We use account and usage data to authenticate users, issue and revoke API keys, authorize billing holds, process manual payment review, investigate abuse, support customers, and keep request history visible in the dashboard and admin tools.
Aimesh relies on third-party infrastructure providers including Google for authentication, Supabase for database services, Upstash Redis for rate limiting and caching, Vercel for hosting, and Telegram for admin payment notifications when slip alerts are enabled. Data is shared only as needed to operate those service flows.
Authentication and billing records may be retained as long as needed for account operation, payment review, fraud prevention, dispute handling, and security. Aimesh uses server-side controls for admin-only data such as provider keys and payment review artifacts, but no system can guarantee perfect security.
You can stop using the service at any time, revoke your user API key from the dashboard, and contact the site operator if you need account-level data handling reviewed. If you continue using Aimesh after this policy changes, the updated policy will apply going forward.
Read the Terms of Service together with this Privacy Policy so the signup flow covers both operational rules and data handling expectations.