Account privacy · Version 4 · Effective 16 November 2026
Private from the start.
Account privacy · Version 4 · Effective 16 November 2026
Private from the start.
We store your verified email, private account ID, chosen alias, notification preferences, whether your account page starts with buying or selling (a preference that grants nothing), security sessions and consent records. Authentication credentials stay on the server.
Payments are processed by Stripe, and your card details never reach Sorla.
Listing assistance sends your listing details to OpenAI only when a seller turns it on for that product.
Sorla does not sell your personal information.
If you connect another account, such as GitHub, GitLab, Bitbucket or Google Drive, to import a product or receive one, Sorla keeps an access token limited to the permission you approved. Tokens are encrypted and never shown on a page. Disconnecting in Connections erases the stored token, and closing your account removes them.
The accounts you can connect are GitHub, GitLab, Bitbucket, Google Drive and Google Sheets, Microsoft OneDrive and Excel, Dropbox and Make. A provider can be connected only once Sorla has switched it on, and each one sees only the request Sorla makes to it with your token; its own privacy policy covers what it holds. Sorla reads or copies only the files or items you select.
Sorla is for US residents aged 13 and over. We don’t ask for your date of birth; you confirm your age when you sign up. If you believe a child under 13 has an account, email support@sorla.ai and we will close it and delete its personal information.
To set up seller payouts you confirm that you are 18 or older, and we keep a record of that confirmation. Any parent or guardian permission records made earlier are kept.
Your email is not a public profile. Repository intake requires separate consent. Only the exact public teaser the creator approves is published, after automated checks of its public wording and links; no staff member reviews it first. An inquiry does not grant source access. Private inquiries and reports are available only to their authorized participants or assigned staff. Staff source access requires a separate, current grant for the selected files.
We measure visible cards, listing views, completed searches, saves and qualified inquiries using a first-party browser session that ends at midnight. Event records contain a keyed session digest, public listing references and controlled filters. They omit exact price filters, IP addresses, email addresses and private messages. Retained activity informs aggregate discovery and review reports; session counts are not counts of people.
When you search for products, we keep the words you typed, in lower case, with the product type you filtered to and how many products matched, under the same session digest and never with your account. Words that look like an email address, a link or a long number are not kept. Creators and affiliates see a search only once at least three different sessions made it, as a count, never who searched. Search words are kept for 90 days, and erasing your discovery data erases them.
Raw discovery events are kept for 365 days. No longer-lived aggregate store is maintained. Browser storage can be blocked or cleared, and core product controls still work.
This covers this browser’s session, including activity before signing in. It never closes a conversation or removes anything you saved. or .
If your browser sends Global Privacy Control (Sec-GPC: 1) or Do Not Track (DNT: 1), Sorla treats it as a request not to be tracked. It sets no discovery-measurement cookie, counts none of your visits or views, and sets no affiliate referral cookie (and does not use one set earlier). Browsing, searching, buying and signing in work as before.
More on what Sorla stores in your browser is on the cookies and browser storage page.
When affiliate programs are open and you follow a creator’s or affiliate’s referral link, Sorla records the visit and sets a first-party cookie (sorla_referral) holding a random reference. The reference does not name you. It lasts 30 days and is used only to credit a purchase of that product to the link that led you there. It is not set if your browser sends a privacy signal (above).
To spot people referring themselves, Sorla also keeps a keyed hash of the network address of a referral click, and of a sign-in to an account in affiliate mode, never the address itself. These are kept for a short period (14 days by default) and then erased.
This browser can remember which homepage message you last saw and keep it consistent during your visit. Only the message number is stored locally; it is not sent as a tracking event or linked to your account. Clearing or blocking browser storage resets the message to its default.
In account settings you can revoke sessions, change optional notifications and marketing preferences, disconnect your GitHub identity, and request a data export or account deletion. The account page shows progress. Withdrawing a listing removes its public visibility; deleting its source is a separate action. Account deletion also erases discovery sessions linked through your measured inquiries and the current browser session when available. For any other question about your data, email support@sorla.ai.
Correspondence and audit records follow the separate 12-month retention policy and backups expire after 35 days. A scoped legal hold can delay erasure. Restoring a backup clears raw discovery activity and preserves independent deletion and publication-removal records so erased material cannot become public again.
When you close your account, your sign-in email is erased 35 days later. Order, payment, refund and payout records, and the signed records of what was published, are kept without your email, because accounting and tax rules and the other party’s rights depend on them. A data export can be downloaded for 24 hours.
When this notice changes, its version number goes up. Signing in again records your acceptance of the current version.