This policy explains what Solo Platform Inc. (“Solo”, “we”, “us”) collects when you use thesolo.ai and the Solo application at app.thesolo.ai, why we collect it, where it is stored, and who else can see it.
Solo helps you build and operate a software business: it scaffolds an application on your own infrastructure and then runs ongoing operations — including, if you connect them, your advertising accounts. That last part means Solo can be granted access to third-party accounts you own. Section 4 covers exactly what that access involves.
1. Information we collect
Information you give us
- Waitlist submissions. If you join the waitlist on thesolo.ai, we store the email address you enter, the segment you select (solopreneur, startup or enterprise), and — if you choose to fill them in — your company name and a free-text description of what you want to build.
- Account details. When you create a Solo account we store your email address, name, and authentication identifiers. Authentication is handled by Clerk; we do not store your password.
- Billing details. Payments are processed by Stripe. Stripe handles your card details directly — Solo never receives or stores full card numbers. We retain the subscription status, plan, and invoice records Stripe returns to us.
- Content you create. Business descriptions, goals, tasks, approvals and other material you enter while using Solo.
Information we collect automatically
- Request metadata. When you submit the waitlist form we record the originating IP address, browser user-agent string, and referring URL, to detect abuse and understand where sign-ups come from.
- Product analytics. We use PostHog to record how the application is used — pages viewed, features used, and errors encountered — so we can find and fix problems.
- Operational logs. Application and infrastructure logs that record requests, errors and system events.
Information from connected accounts
If you connect a third-party account (see section 3), we receive data from that account. What we receive depends on the provider and is described below.
2. How we use it
| Purpose | What we use |
|---|---|
| Provide and operate the service | Account details, content you create, connected-account data |
| Authenticate you and keep accounts secure | Account details, request metadata, logs |
| Bill you and manage subscriptions | Billing details |
| Fix bugs and improve the product | Product analytics, operational logs |
| Send service and access-invite emails | Email address |
| Detect, prevent and investigate abuse | Request metadata, logs |
We do not sell your personal information. We do not use your content or connected-account data to serve you advertising, and we do not use it to train generalised artificial-intelligence or machine-learning models.
3. Connected accounts
Solo only accesses a third-party account after you explicitly authorise it through that provider's own consent flow. You choose which accounts to connect, and you can disconnect any of them at any time.
Where a provider issues Solo a long-lived credential (such as an OAuth refresh token), that credential is stored encrypted in AWS Secrets Manager under an access policy scoped to your workspace. It is used only to carry out actions for the business you connected it to.
4. Google user data
This section describes Solo's use of data obtained through Google APIs. It applies when you connect a Google Ads account to Solo.
What we request
Solo requests a single OAuth scope: https://www.googleapis.com/auth/adwords. Google does not offer a read-only variant of this scope, so authorising it necessarily grants both read and write access to the Google Ads accounts reachable by the Google account you authorise. Solo's own controls — not the scope — are what restrict it to the specific advertising account you select.
What we access
- Account identifiers — the Google Ads customer IDs your authorised Google account can reach, so you can pick which one to connect, and the descriptive name and currency of the account you select.
- Campaign configuration — campaigns, ad groups, ads, keywords, budgets, geographic targeting and status for the connected account.
- Performance metrics — impressions, clicks, cost, and conversions for the connected account.
What we do with it
- Display your advertising configuration and performance inside your Solo dashboard.
- Create, update, pause and resume campaigns in the connected account, at your direction and subject to the spend limits and approvals you set. Solo requests your explicit approval before a campaign begins spending.
- Report on results so you can decide what to change next.
We do not use Google user data for any other purpose. We do not use it to serve advertising outside the connected account, we do not sell it, and we do not use it to train generalised AI/ML models.
How it is stored and shared
The OAuth refresh token for a connected Google Ads account is stored encrypted in AWS Secrets Manager. Campaign and performance data retrieved from the Google Ads API is stored in the datastore for your Solo workspace and is not accessible to other Solo customers. We do not transfer Google user data to third parties except to the infrastructure subprocessors listed in section 5, which process it on our behalf and under contract.
Limited Use commitment. Solo's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Revoking access
You can disconnect a Google Ads account from within Solo at any time, which deletes the stored refresh token. You can also revoke Solo's access directly from your Google Account at myaccount.google.com/permissions. Revoking access stops all further API activity; campaigns already running in your Google Ads account are unaffected and remain under your control there.
5. Who we share with
We share personal information only with service providers who process it on our behalf, and only as needed to run the service:
| Provider | Role |
|---|---|
| Amazon Web Services | Hosting, databases, encrypted secret storage |
| Clerk | Authentication and user management |
| Stripe | Payment and subscription processing |
| PostHog | Product analytics |
| Anthropic, OpenRouter | AI model inference for Solo's automated operations |
| Langfuse | Tracing and diagnostics for AI operations |
We may also disclose information where required by law, to enforce our terms, or to protect the rights and safety of our users. If Solo is involved in a merger, acquisition or sale of assets, information may transfer as part of that transaction; we will give notice before your information becomes subject to a different privacy policy.
6. Storage, security and retention
Data is stored on Amazon Web Services infrastructure in the United States. Credentials and secrets are encrypted at rest; traffic to and from Solo is encrypted in transit using TLS. Access to production systems is restricted to personnel who need it.
We keep account and content data for as long as your account is active. If you delete your account, we delete or anonymise the associated personal information within 90 days, except where we must retain records for legal, tax or accounting purposes. Waitlist entries are kept until you ask us to remove them. Operational logs are retained on a rolling basis and then discarded.
No system is perfectly secure, and we cannot guarantee absolute security — but we work to protect your information using measures appropriate to its sensitivity.
7. Your choices and rights
You can:
- Access, correct or export the personal information we hold about you.
- Delete your account and the data associated with it.
- Disconnect any connected third-party account.
- Unsubscribe from non-essential email at any time via the link in the message.
- Ask us to remove your waitlist entry.
Depending on where you live — for example in the European Economic Area, the United Kingdom, or California — you may have additional rights, including the right to object to or restrict processing, the right to data portability, and the right to lodge a complaint with your local supervisory authority. We do not sell personal information or share it for cross-context behavioural advertising.
To exercise any of these, email team@thesolo.ai. We respond within 30 days.
8. Children
Solo is not directed at children under 16, and we do not knowingly collect personal information from them. If you believe a child has provided us information, contact us and we will delete it.
9. Changes to this policy
We may update this policy as the product changes. When we do, we revise the “last updated” date above. For material changes we will give notice by email or in the application before the change takes effect.
10. Contact
Solo Platform Inc.
Email: team@thesolo.ai