1. Information we collect
We collect:
- Information you provide: your email address; authentication identifiers; information you submit about a company, offering, or holding; profile information you choose to publish (such as a profession, description, services, and social links); documents you upload; and the contents of your communications with us.
- Document viewing: when an Issuer shares a document with you through a share link, we collect the email address you enter to open it and your viewing activity (such as the pages you viewed and the time you spent on them) and report that activity to the Issuer that shared it.
- Identity passport: when you verify your identity, we keep your passport: a random secret, and the credentials that verification providers attest about you, such as your KYC level, residency, investor type and accreditation. They are sealed, so our database alone cannot read them. Our proving service opens them for three purposes only: to prove, for a wallet you activate, that you meet a company's rules, and the company learns only yes or no; to seal them again when a credential is renewed or updated; and to show them to you, sealed to a key your browser makes for that viewing, so that only your browser can read them. We log each activation (the wallet, the platform that asked, the company and the rules proved) and each time your claims are shown. A wallet joins your passport only with that wallet's own signature, and a platform that uses obolos can use your passport with a wallet only after that wallet signs its permission. When a platform links a new wallet to a passport that already exists, it always needs your code as well: a code we email to the passport's address, naming that wallet. Attaching a passport another platform verified to your obolos account needs a code we email to that passport's address, even when you sign in with a wallet that platform linked to it. You can ask us to erase your passport. Erasure removes its secret and claims, the key that ties it to your email address, its wallet links and the permissions those wallets gave platforms, its codes, and the log of each time your claims were shown. The activation log stays as the record of what obolos did: which wallet was proved for which company, and when. What is already recorded on the blockchain stays too, as Section 2 explains.
- Agent wallets: when you make an agent wallet, we keep which agent wallets belong to your account, which of your wallets each one acts for, what you let it do there with what your wallet signed for it, and which command-line tools are connected as it, with each one's name, host and when its session ends. An agent with Read opens that wallet's documents and confidential values on your behalf, with the read permission your wallet gave it. Privy, our wallet-infrastructure provider, holds the agent wallet's key and signs for it only on the authorization of a command-line tool you connected. An agent's public check stays off until you turn it on. Once it is on, anyone can look up whether a verified person stands behind that agent, and until when, with your accreditation if you allow that too. The check never says who you are, but anyone who sees the agent act for one of your wallets can then tell that the wallet's owner is verified.
- Connected assistants: when you connect an assistant such as Claude or ChatGPT to your account, we keep the connection: the assistant's name and address as it gives them, what you let it do (read, form companies, messages), when you connected it and last used it, and fingerprints of its keys, never the keys themselves. It sees only what you can see on the Platform, and amounts encrypted for your account stay encrypted: it never receives them. It cannot sign, pay or change a company's records. What it reads for you goes to the company that runs the assistant, under that company's terms and privacy policy. We do not receive your conversations with it. A message it sends for you, or a company it prepares, is kept like one you made in the app, with a note of which assistant made it. When a call fails, we log the tool's name and the kind of error, never what was asked. You can end a connection at any time in Passport › Assistants: its keys stop working at once, and we keep the ended connection's record with your account.
- Identity verification information: where you verify your identity or a business, our identity verification provider collects a government-issued identity document, a photograph or short video of your face to compare against it, and, where an address check is required, a document evidencing your address. For a business it also collects company registry records and information about its officers and beneficial owners. The provider screens the names involved against sanctions, politically exposed person, and adverse media lists, and returns its decision to us. Section 3 explains what we keep from that decision and what we do not.
- Wallet and blockchain information: your wallet address or addresses and the on-chain transactions and holdings associated with them. In obolos a wallet address is titled as "identifier". You can use a separate one at each company; one used at several companies links what you do at each of them. We keep the link between your account and each of your identifiers, including which company each one serves; your wallet or sign-in provider holds their keys.
- Payment information: when a company pays for the Plus plan or buys credits by card or bank debit, our payment processor, Stripe, collects the card or bank details directly and processes them under its own privacy policy; we never see full card or bank account numbers. We give Stripe the company's name; the email address of the admin who most recently started a Plus checkout or opened Manage plan, where Stripe sends Plus invoices and receipts; and, for each card or bank payment for credits, the email address of the member who makes it, for its receipt. We keep the company's Stripe customer reference; the amount, date, and status of each of its card and bank payments, including any dispute, and the account that made each credit purchase; and the status of its Plus subscription. We send billing notices, such as each Plus payment and any failed renewal payment, to the company's admins in the Platform, and by email to those who are members of its workspace, as their notification settings allow.
- Charon usage: for each reply from Charon, the Platform's assistant, and each document analysis it runs, we keep a record of its cost, its date, the account that asked, and the company it was for, to count each month's included use and to charge use beyond it. We also keep your conversations with Charon so you can return to them: each one for 30 days after its last message, or for as long as you keep it pinned, unless you delete it sooner.
- Information from authentication and service providers: when you sign in with a passkey, an emailed one-time code, or Google, we receive the limited information needed to authenticate you.
- Information collected automatically: device and usage data, log data, approximate location derived from IP address, and similar information collected through cookies, local storage, and analytics tools.
2. On-chain and published data
The Platform records certain data on public blockchain networks and may publish documents to decentralized storage (such as IPFS). Information recorded on a public blockchain or published to such systems is public, replicated, and generally permanent: it cannot be changed or deleted by us, and may remain accessible indefinitely. Privacy-enhancing features (such as encryption of certain terms and documents) reduce, but do not guarantee, the confidentiality of on-chain information.
Some data is encrypted on-chain so that, unlike ordinary public blockchain data, it is not publicly readable and is intended to be visible only to the Issuer or user it belongs to and the parties they permit. Authorized users ordinarily decrypt that data through their own wallet in the application. An Issuer can also appoint users to roles that let them claim access to particular confidential records. Because access already granted to a wallet for a particular ciphertext may be technically durable, removing a role stops future claims but may not withdraw access already claimed. Earlier versions of a data-room document cannot lose readers or be removed, so a person a document was shared with directly keeps the earlier versions shared with them; removing someone from a folder, which rotates the folder's key, is how an Issuer cuts their access to that folder. A profile photograph or logo you upload is published to decentralized storage without encryption, so treat it as public and permanent.
Some records are written on-chain in plain form by design: fundraise rounds, their published terms and limits, the addresses on their whitelists, and how many investors each has, the record of a qualified financing (its threshold, the pre-money share count it converts against, and which instruments it covers), allocations (the investor's address, whether the Issuer or the investor opened it, who brought its capital, any payment deadline, and, in a priced fundraise, the number of shares it buys), each signature's wallet, time and a salted hash of the signer's identity, each paper signature with the address that filed it (never an agreement's contents or a signer's name, which stay encrypted for the parties, nor which document a negotiated allocation was signed over), transfer notices (the seller and buyer addresses, the amount, the applicable time limits, and a link to the offer document), a hash of the document behind an issuance or corporate action, salted where the document is private (it identifies the document to the parties without revealing its contents), a grant holder's acceptance of their grant (their wallet, the time and the signature, or a link to the signed paper copy, with a hash of it where the copy is kept in the data room, salted where it is private, and the address that filed it), refunds and withdrawals, and the outcome of confidential checks (for example that a payment the Issuer recorded was within its fundraise's limits, or whether an exercise or release was permitted, without the confidential amounts behind it). For an exercise you pay the Issuer for, the number of shares you request is public, though it does not show your name. Whether the request is within what you can exercise also becomes public as soon as you file it, so that the Issuer can confirm your payment, and both stay public if the request is later withdrawn or declined. The date the Issuer records for your payment is public too; the price you pay is never made public. For a cashless exercise, the number of options you ask to exercise stays confidential: the Issuer counts the shares you receive from a valuation only the Issuer sees, and only the number of shares issued becomes public, when the exercise settles.
Amounts in a fundraise are recorded in encrypted form. An allocation's amount may be viewed by its investor and by the Issuer and persons it authorizes, and a fundraise's total and each investor's total by the Issuer and persons it authorizes. The Issuer may publish a fundraise's total after the fundraise is finalized. In a priced fundraise, the price per share is also recorded in encrypted form and may be viewed by:
- the Issuer and persons it authorizes;
- any address the Issuer adds to the fundraise's whitelist (its list of admitted investors);
- an investor, once the Issuer signs that investor's allocation;
- the holder of a SAFE or convertible note that converts in the fundraise; and
- any person who requests it, while the fundraise is open, from a wallet that meets the fundraise's eligibility requirements.
A request for the price is recorded publicly, so it shows that the requesting wallet met those requirements, and access to the price, once granted, is permanent. Public records may nevertheless reveal or narrow these figures:
- a payment in the payment asset to an Issuer's vault is a public transfer that shows its amount and, with the allocation's share count, the price per share;
- the share counts, public limits, and check outcomes of a priced fundraise narrow its price, and where its minimum and maximum investment are equal, the first recorded subscription reveals the price;
- any person who can view the price can calculate each priced allocation's amount from its share count;
- publishing the total of a priced fundraise reveals its price; and
- when a SAFE or convertible note converts, the number of shares issued on conversion is public and may reveal the instrument's amount.
Activating a wallet from your identity passport also writes public records: whether that wallet meets each rule it proved, and until when, which attestor's credential tree vouched for it, and identity ciphertexts that only the configured escrow recipients can open. Each tree carries a name that identifies the platform that attested you. At each company where you activate a wallet, the wallet is also linked on-chain to a handle for you at that company. The link is written once, at the wallet's first activation for that company, and kept at every later activation there, so anyone can see that the wallets activated at one company belong to the same person, though not who that person is. Your handle differs from company to company. Where a company's rule accepts only verified accreditation, the week your accreditation was verified is public too, recorded with your handle at that company.
Each grant of credits to a company and each charge to its credit balance, with its amount, is recorded on the Platform's public ledger. A grant or charge for Plus, a top-up by card or bank, Charon use, or a disputed payment carries a random reference; what it is for is kept by obolos and shown on the company's statement. These records carry no personal data.
The protocol factory maintains a single obolos-controlled platform Operator address for limited protocol administration, including credit-account adjustments. Issuers do not appoint this address, and it is not registered separately by each entity. The factory Operator has no access to confidential instrument terms, data-room documents, or folder keys by virtue of that role. Separately, an Issuer may appoint its own Terms Operators and other company role holders. A Platform service receives confidential instrument or data-room data only where an authorized user deliberately delegates the access needed for a feature, such as a time-limited permit covering the exact records needed to prepare a conversion proof, or where you otherwise provide the data to us. Data-room access is governed separately by the Issuer's roles and access groups. These arrangements do not give us your wallet private keys, passkeys, or recovery credentials. Section 6 of the Terms describes them in more detail. The underlying data remains owned by the Issuer or user to whom it belongs.
3. Identity verification and your credential
The Platform obtains identity checks from a specialist identity verification provider so that Issuers can apply their investor eligibility rules. The provider performs the checks. The checks are a tool for Issuers; they do not make obolos an agent of any Issuer for investor verification, and they are not a determination that obolos is a broker-dealer, transfer agent, or financial institution.
From that provider's decision we derive a short, fixed set of coded facts: your verification level, whether screening was clear, whether you are a politically exposed person, your country of residence, your nationality, whether you are a US person, the kind of holder you are, your tax form, and the dates between which the result is valid. We do not keep your identity document, your photograph, or the underlying screening report. Those remain with the provider under its own retention policy.
Those coded facts are sealed into a credential in your identity passport, described in Section 1. What is recorded on the blockchain discloses neither your identity nor the facts themselves to anyone observing the chain, and proving that you meet an offering's requirements does not reveal which facts satisfied it. Each credential carries a reference to your verification file at the provider. We can resolve that reference back to your verification file, and we may do so where required to respond to a lawful request from a regulator, court, or other competent authority, or to meet our own legal and compliance obligations.
Some facts are declared by you rather than checked by anyone, including accreditation and qualified purchaser status, and your country of residence before an address check has been completed. The credential records that those were self-declared, and you are responsible for their accuracy.
Where you verify a business, the provider collects information about its officers and beneficial owners. If you are one of those people and did not give us that information yourself, we process it so that the Issuers that business invests with can apply their investor eligibility rules, and this policy describes how.
4. Legal bases for processing
If you are in the European Economic Area or the United Kingdom, we rely on the following bases: the performance of our contract with you, to operate the Platform and the features you use, including the identity verification and screening you ask for so that Issuers can apply their eligibility rules to you; compliance with the legal obligations that apply to us, such as tax and accounting requirements and lawful requests from authorities; our legitimate interests in securing the Platform, preventing fraud and abuse, improving our services, and, where a business is verified, handling information about its officers and beneficial owners so that Issuers can apply their eligibility rules to it; and your consent where it is required, including for the biometric comparison of your photograph against your identity document carried out by our identity verification provider. You may withdraw consent at any time, though without verification we cannot make verification-gated features available to you.
5. How we use information
We use information to operate, maintain, and improve the Platform; to authenticate you and secure accounts; to enable the features you use; to communicate with you, including about security and service updates; to detect, prevent, and address fraud, abuse, and security issues; and to comply with legal obligations and enforce our terms.
6. How we share information
We share information:
- with service providers that help us operate the Platform (for example, identity verification and screening providers, authentication and wallet-infrastructure providers, blockchain RPC and indexing providers, email delivery providers, decentralized-storage providers, hosting, and analytics), under appropriate confidentiality and data-processing obligations;
- with Stripe, our payment processor, to take a company's card and bank payments, and with the AI provider behind Charon, which receives each question you ask Charon with the conversation before it; the records Charon reads to answer, which are the records of the company you have open that your role lets you see, including its holders' names and holdings, or, in your portfolio, your own holdings and companies; and the documents you give Charon to analyze, including the paperwork used to fill in a new company;
- with an assistant you connect, such as Claude or ChatGPT, and the company that runs it: what obolos answers when the assistant asks for you, which is only what you can see on the Platform. That covers the records of your companies that your role lets you see, including holders' names and holdings; your own holdings and the rounds you are in; the data room files you can read; your conversations, if you let it use messages; and your formation requests with their details. Amounts encrypted for your account are never sent. That company handles what it receives under its own terms and privacy policy;
- with other participants as inherent to the Platform; for example, information you make part of an offering or transaction, or whether you opened a company's update, may be visible to the relevant Issuer or investor, and on-chain activity is publicly visible;
- with anyone who looks up an agent whose public check you turned on: whether a verified person stands behind it, until when, and your accreditation if you allow it;
- with a company when you accept its invitation: the company's list of people can then hold your email address, the identifier you use there and your legal name, if we have it;
- when required to comply with law, legal process, or a governmental request, or to protect the rights, safety, and property of obolos, our users, or others; and
- in connection with a merger, acquisition, financing, or sale of assets.
We do not sell your personal information.
7. Cookies and local storage
We use cookies, local storage, and similar technologies to keep you signed in, remember preferences, and understand usage. You can control these through your browser settings, though some features may not work without them.
8. Data retention
We retain personal information for as long as needed to provide the Platform, comply with our legal obligations, resolve disputes, and enforce our agreements. As noted above, data recorded on a public blockchain or decentralized storage is outside our control and may persist permanently regardless of your relationship with us.
9. Security
We use technical and organizational measures designed to protect information. No system is completely secure, and we cannot guarantee absolute security. You are responsible for safeguarding your wallet, devices, passkeys, and credentials.
The most sensitive fields in your account record are encrypted before they are written to our database, and the key needed to read them is held outside it, so a copy of the database alone does not reveal them. That covers your legal name, date of birth, tax identification number, mailing address, and entity name, together with the corresponding values returned by identity verification. Information we need in readable form to sign you in and to keep accounts unique, such as your email address, is not encrypted this way, and neither is a company's list of people (Section 6).
10. Your choices and rights
Depending on where you live, you may have rights to access, correct, delete, or port your personal information, or to object to or restrict certain processing. To exercise these rights, contact us at legal@obolos.io. We will respond as required by applicable law. Please note that we cannot alter or delete information stored on a public blockchain or decentralized storage.
11. International users
obolos is based in the United States, and we may process and store information in the United States and other countries that may have different data-protection laws than your own. Where required, we use appropriate safeguards for international transfers.
12. Children
The Platform is not directed to, and may not be used by, anyone under 18. We do not knowingly collect personal information from children.
13. Changes
We may update this Privacy Policy from time to time. We will revise the "Last updated" date above and, where appropriate, provide additional notice.
14. Contact
For questions or requests regarding this Privacy Policy, contact Obolos Group Incorporated at legal@obolos.io.