This policy explains what Solorva does with your information, in the plainest language we can manage. It describes how the product actually works today, not how we might like it to sound.
Who we are
Solorva is an AI brand and content platform operated by Antypas Ventures LLC, a limited liability company formed in Wyoming, United States (Wyoming filing number 2026-002040014). When you use Solorva, we decide how and why your personal data is processed, which makes Antypas Ventures LLC the data controller for that information.
When you put other people's personal data into Solorva, for example people named or pictured on a website you submit, in your uploads or in the posts we write for you, you decide what is done with it and we process it on your behalf, as your processor. Our Data Processing Addendum (solorva.com/dpa) sets out the terms for that, including the list of services we use to do it. The rest of this policy is about the information we hold about you.
You can reach us about anything in this policy at privacy@solorva.com.
Our representatives in the EU and UK
Antypas Ventures LLC has no establishment in the European Union or the United Kingdom, so it has appointed representatives there under Article 27 of the GDPR and of the UK GDPR. You, and the data protection authorities, can contact them about anything to do with how we process your personal data, as well as contacting us directly.
In the European Union: Ioannis Antypas, Leof. Vasilissis Sofias 23, Athina 106 74, Greece, ioannis.antypas@solorva.com.
In the United Kingdom: Ioannis Antypas, 128 City Road, London, EC1V 2NX, United Kingdom, ioannis.antypas@solorva.com.
What we collect
We collect only what the product needs to work:
- Account details — your name, email address, a password, and the country you live in. Passwords are stored only as a bcrypt hash; we never hold the password itself and cannot recover it for you. We use your country, and the country of the billing address you pay with, only to check that we can lawfully offer you the service and that our payment provider can take your payment (section 3 of our Terms of Service lists the few places this limits, and why).
- Brand and business information — the website addresses you submit, the brand profile extracted from them (voice, palette, typography, positioning), product details you import, and any assets you upload.
- Content you create — generated posts, articles, images, research reports, and anything saved to your library.
- Usage records for billing — a ledger of what each generation cost, so credits and spending limits can be enforced. This records the operation and its cost, not the content of what you generated.
- Support correspondence — anything you send us by email at support@, privacy@ or legal@solorva.com, and our replies.
- Support requests you send in the app — the subject and category, your messages and our replies, and, to save a round of questions, the page you were on and your browser's user agent (the text a browser sends that names it, its version and your operating system). Our team may add internal notes while handling a request; those notes are not part of the self-service download.
- Sign-in and security records — when you sign in, we record the IP address and the browser's user agent of that device, with a short label such as "Chrome on Windows", so that you can see where you are signed in and end a session in Settings, under Security. The activity log records the IP address and user agent with each action it logs, such as signing in, failed sign-in attempts (with the email address that was tried), changes to your account, exports and deletions. We use these records to keep accounts secure and to detect and investigate fraud and misuse.
- Server logs — like most websites, our web server logs each request it receives, with the IP address, the time, the address requested and the browser's user agent. We use these logs only to keep the service running and secure.
- Feedback you choose to send through the Feedback page — a category, an optional rating, your message, an optional feature request and an optional screenshot. Our team may add internal notes while reviewing it. Sending feedback is optional, and support never depends on it.
- Team details — if you invite someone to a workspace, the email address you enter for them, the role, and who invited them and when. If you join a workspace, the role you hold there.
- Newsletter subscription — if you subscribe to our newsletter, The Solorva Briefing: your email address, when and where you subscribed (our newsletter page, the site footer or the box at sign-up), the exact wording you agreed to, and when you unsubscribed. See Our newsletter, below.
- Error reports from your browser — if a Solorva page crashes, your browser sends us the error's name, its message and technical trace, and which page it was (the path, without any query string). The report we save is not linked to your account and does not include your IP address or browser details. We use these reports only to find and fix faults.
What we do not collect
We do not run analytics, advertising, or tracking software of any kind. There is no Google Analytics, no advertising pixel, no session recording, and no third-party script watching what you do on the site.
We do not sell personal data, and we do not share it for advertising.
Cookies
Solorva sets one cookie, and it remembers whether you left the sidebar open or closed. It is strictly functional and carries no identifier that can be used to track you.
Your sign-in session is held in your browser's local storage rather than a cookie, and is sent only to our own API.
Why we process your data
Where the UK GDPR or EU GDPR applies to you, our lawful bases are:
- Performance of a contract — to run your account, produce the content you ask for and answer your support requests.
- Legitimate interests — to keep the service secure and to prevent and investigate fraud and abuse (this is why we keep the sign-in, session and activity records and the server logs described above), enforce spending limits, diagnose faults, check that we can lawfully offer the service where you live and that our payment provider can take your payment, and improve Solorva using feedback you choose to send us.
- Legitimate interests, for people invited to a workspace — someone we invite at a customer's request is not a party to our contract with that customer, so we rely on legitimate interests, ours and the customer's, in the collaboration the customer asked for. We use the invited person's email address only as far as that needs: one invitation email, a link that works once and expires after 7 days, and acceptance while signed in with that address.
- Consent — if you subscribe to our newsletter. You can withdraw it at any time by unsubscribing; that does not affect anything sent before you did.
- Legal obligation — to keep records we are required to keep, such as those relating to payments.
Who we share it with
Solorva is built on other companies' services. These are the ones that may receive your data, and what each of them gets:
- OpenRouter — receives the prompts and brand context needed to generate your content, and routes them to model providers including Anthropic, OpenAI and Google. United States.
- Perplexity — reached through OpenRouter, receives the research queries built from your brand and business details when you run a research report. United States.
- Image model providers — Google, Black Forest Labs, Sourceful and OpenAI, reached through OpenRouter, receive the image prompts derived from your brief. They may process them in the United States or elsewhere.
- DigitalOcean — hosts the application and the database in Amsterdam, and stores the images you upload and generate in Frankfurt. Both are in the European Union. DigitalOcean also keeps backups of our server.
- Resend — delivers transactional email, such as password resets and receipts. Your email address and the message are processed to send it. United States.
- Beehiiv — if you subscribe to our newsletter, receives your email address and the date and source of your sign-up, and sends the newsletter to you. United States.
- Outstand — connects your social accounts and publishes to them on your behalf. When you connect an account you approve it on the network itself; Outstand holds that permission, and we never see or store your social password or access token. When a post goes out, the caption and the image links for that post are sent to them.
- Backblaze — stores an encrypted copy of our nightly database backup. The copy is encrypted on our servers before it is sent, and Backblaze does not hold the key. United States.
- Google — hosts our email through Google Workspace. Messages you send to support@, privacy@ or legal@solorva.com, and our replies, are stored by Google.
- Stripe — takes payments through Stripe Managed Payments, under which Stripe, through its Link service, is the merchant of record for your payment. Stripe receives your payment details, email address, billing address and the details of what you bought, to take the payment and work out the tax. Card details are entered with Stripe and never reach our servers. Stripe's own privacy policy also applies to what it collects at checkout.
We share the minimum each service needs. We do not give any of them your data for their own marketing. Where we process personal data on a customer's behalf, the services that help us do it are listed in our Data Processing Addendum.
Connecting an app to your account
You can connect an AI assistant or another app to your Solorva account by signing in from it and approving the request on our page. For each connected app we store the app's name and the address its sign-in returned to, the permissions you granted, the one workspace you chose, when you connected it and when it last used the connection, and the app's access and refresh tokens, which we keep only as one-way hashes so they cannot be read back. We keep this so the app can act for you within the permissions and the workspace you approved, using your plan and credits as you would in the dashboard, and so you can see and end the connection. An access token lasts one hour. A refresh token lasts 30 days and is replaced each time the app uses it, so a connection stays live while the app keeps using it, and lapses 30 days after its last use. You can disconnect an app at any time in Settings, under API, Connected apps; it stops working straight away. A password reset or a deactivated account also ends every connection. Each token record is deleted automatically a day after it expires, and all of them straight away if you delete your account. The app itself receives what you ask it to fetch or make through the connection; what it does with that is governed by its own terms and privacy policy.
Workspaces and teams
Workspaces let more than one person work on a brand. This is what happens to the information involved.
- When you invite someone, you give us their email address. We use it to send them one invitation email through Resend, and to let them accept the invitation while signed in with that address. The invitation link works once and expires after 7 days; resending it replaces the link, and the owner or an administrator can withdraw it. Our lawful basis for this is legitimate interests, as set out under Why we process your data.
- Please invite only people who would expect to hear from you. The invitation tells them who invited them.
- An invitation record, including the address, is deleted automatically 90 days after the date its link expires (7 days after it was last sent), whether it was accepted, withdrawn or never used. It is deleted sooner if the workspace owner deletes their account, or if the invited person deletes a Solorva account registered with that address. Sending, accepting and withdrawing an invitation are recorded, with the address, in the activity log, which is kept as described under How long we keep it.
- Everyone on a workspace's team can see the workspace's name and the names and email addresses of its owner, its members and the owner's account administrators. The owner and administrators can also see pending invitations, with the invited addresses, and the workspace's team activity.
- Being on someone else's workspace does not let them see your own account, brands, billing or data, and does not let you see theirs beyond that workspace. You can leave a workspace at any time, and the owner or an administrator whose role is above yours can remove you; either takes effect straight away.
- If ownership of a workspace is transferred, the brand and its content move to the new owner's account, and from then on appear in their data export and are deleted with their account. Generation history and spending records stay with the previous owner.
- If a workspace owner deletes their account, the workspace and its content, memberships and invitations are deleted with it, and its members lose access straight away. Ownership is never handed to a member automatically. Your own account and data are not affected.
AI provider keys
Generation is included in your subscription. You do not supply an AI provider key and we do not store one for you. Until 7 September 2026 you could supply your own OpenRouter key; that option has been removed, and any key supplied before then has been erased from our database.
Sending data outside the UK and EU
Our application, database and image storage are in the European Union, with DigitalOcean in Amsterdam and Frankfurt. Some of the services listed above process data outside the UK and EU:
- OpenRouter, in the United States, and the model providers it routes to, several of which are in the United States. When you generate content, the prompt and the brand context it needs travel there.
- Resend, in the United States, for transactional email.
- Beehiiv, in the United States, for the newsletter, if you subscribe to it.
- Backblaze, in the United States (US West), for the offsite copy of our database backup. That copy is encrypted on our servers before it is sent, and Backblaze does not hold the key, so it cannot read it. We still treat it as a transfer of personal data, with the same safeguards as the others.
- Stripe, which may process payment information in the United States.
- Google, which hosts our email and may process it outside the UK and EU.
- Outstand, and the social networks you choose to publish to, which may process the content of your posts outside the UK and EU.
Where personal data goes from the UK or EU to a country without an adequacy decision, we rely on the safeguards in each provider's data processing terms, including standard contractual clauses where they are required.
How long we keep it
We keep your account, brand profiles, and generated content for as long as your account exists, because that content is the thing you came for and deleting it on a timer would be unhelpful.
When you delete a brand, a piece of content, a deck or an uploaded asset, it moves to your trash, where you can restore it for 30 days. After 30 days it is permanently removed from our live systems, together with its images. To have something removed sooner, delete your account as described below or email privacy@solorva.com.
You can delete your whole account yourself in Settings, under Your Data. That removes your account, brand profiles, generated content and images from our live systems straight away, including anything in your trash, and ends your social account connections. If a plan is still running, including a cancelled plan that has not yet reached the end of its period, the plan has to end first. To have your account deleted sooner, email privacy@solorva.com.
Some records are kept after an account is deleted. Purchase records are kept as financial and tax records for 10 years after the end of the year in which the payment was made; once the account is deleted they no longer carry your name or email address. Refund requests are kept as financial records too, without your words: when the account is deleted, any message you wrote with a request, and our note on it, is removed, leaving the amount, the payment reference, the decision and the dates. Each refund request is deleted automatically seven years after it was made. Activity log entries, which record what was done on the account and include its email address and the IP address and user agent each action came from, are kept to protect the security of the service and to show what happened; they cannot be edited, and each entry is kept for six years from the action it records and then deleted. Records of refunds and payment disputes received from Stripe are deleted automatically after 180 days.
Session records, with their IP address and user agent, are deleted automatically 30 days after the sign-in that created them, and straight away if you delete your account. Support requests you send in the app are kept while your account exists and are deleted with it. Emails to our support and privacy mailboxes, including requests to exercise your rights and our replies, are kept for three years after the last message in the conversation and then deleted. Emails to our legal mailbox are kept for six years after the matter is closed, and longer only while a legal claim about it is open.
Our web server's request logs, with the IP address, time, address requested and user agent of each request, are deleted automatically, at the latest 16 days after they are written. The logs our application and database keep about their own running are rotated daily and each rotated file is deleted after 30 days; the operating system's journal keeps at most 90 days.
Feedback you send through the Feedback page, and any screenshot with it, is deleted automatically two years (730 days) after you send it. Deleting your account deletes it straight away.
Error reports sent from your browser are deleted automatically 30 days after that error was last reported.
Newsletter records are kept as described under Our newsletter: 30 days after you unsubscribe your email address is replaced by a one-way code.
When something goes wrong on our servers, we keep a record of the error so we can fix it. A record may include the account identifiers of up to five accounts the error affected. We remove an account's identifier from these records as soon as the account is deleted, and in any case 90 days after the error last occurred. Records of failures at our AI and image service providers are handled the same way and are deleted entirely 90 days after the failure last occurred.
Our backups are encrypted, and each kind is deleted on a fixed schedule: the nightly backups on our server after 28 days, DigitalOcean's daily backups of that server after 7 days, and the offsite copy with Backblaze 31 days after it is uploaded, and we check every night that no offsite copy is older than 35 days. Because DigitalOcean's backups also contain the nightly backups stored on the server, information you delete may remain in our backups for up to 35 days after it leaves our live systems, and is then deleted. One exception applies to information deleted before 6 November 2026, when this schedule took effect: older backups, including a copy of the server taken on 2 November 2026 before a planned maintenance change, may hold it until no later than 7 December 2026, when they are deleted. We use backups only to recover the service.
How we protect it
- All traffic is encrypted in transit with TLS.
- Passwords are stored as bcrypt hashes. Solorva API keys are stored only as a hash, and webhook signing secrets are encrypted at rest.
- Our database backups are encrypted before they leave the server.
- The database is not reachable from the public internet — only our application servers can connect to it.
- Sessions expire, and changing your password invalidates any session issued before the change.
- No security is absolute. We assess and record every security incident that affects personal data. If a breach is likely to put your rights and freedoms at high risk, we will tell you without undue delay, and where the law requires it we report a breach to the relevant data protection authority.
Your rights
You can ask us to:
- Give you a copy of the personal data we hold about you. You can also download it yourself in Settings, under Your Data. That download leaves out the internal notes our team adds to your feedback and to our decision on a refund request. If you ask us for a copy by email, we also review those notes and give you the ones that concern you.
- Correct anything that is wrong.
- Delete your account and its data. You can also do this yourself in Settings.
- Restrict or object to how we process it.
- Provide your data in a portable form.
Email privacy@solorva.com and we will respond within one month. If you are in the UK or EU and you think we have handled your data badly, you can also complain to your national data protection authority — in the UK, that is the Information Commissioner's Office.
Children
Solorva is not intended for anyone under 18, and we do not knowingly collect data from children. If you believe a child has given us personal data, email privacy@solorva.com and we will delete it.
Changes to this policy
If we change this policy in a way that materially affects you, we will update the date at the top of this page and, where the change is significant, tell you by email.
Contact us
Questions about this policy, or a request about your data, go to privacy@solorva.com.
The terms that apply when we process personal data on your behalf are in our Data Processing Addendum.
Connecting a social account
This is the part of the product where you give something away, so it is worth setting out in full. The short version is on the Connected Accounts screen; this is the whole of it.