1. Controller and contact
The controller responsible for data processing on this website and for the operation of the Valued platform is:
Digital Pioneers GmbH, Lilienstraße 11, 20095 Hamburg, Germany
Managing Director: Heiko Hubertz
Commercial register: Amtsgericht Hamburg, HRB 108462
Data protection contact: privacy@valued.com
2. Two roles: Controller and processor
Valued processes data in two distinct roles, and it is important to distinguish between them:
Controller
For data relating to the customer relationship itself — account and profile data, user administration, billing, support communication and website usage — we act as the controller. This section of the policy describes that processing.
Processor
For the investment content the customer uploads or imports (fund documents, capital calls, distributions, reports, cap tables, shareholder and loan data, and any personal data contained therein), we act as a processor on the customer's instructions. The customer remains the controller for that content and determines its purposes. This processing is governed by a data processing agreement pursuant to Art. 28 GDPR, which we make available on request.
3. Categories of data we process
Account and organisation data
- Name, business email address, password (stored only as a salted hash), preferred language and display settings.
- If you choose to sign in with Google: Google Ireland Limited confirms who you are and passes us your name, your email address and the address of your profile picture. We receive no password and nothing else from your Google account. Google learns that you signed in to Valued; Google’s own privacy policy applies to its part.
- Organisation and team data, invitations, roles and permissions.
- Plan, subscription status and billing data (invoice address, VAT ID, payment status; card data is processed exclusively by our payment provider).
- A record of the emails we send you: the kind of email, the address it went to, its subject and language, when it was sent, and whether it was delivered, opened, clicked, rejected or reported as spam.
- Your notification settings, including the kinds of email you have switched off or unsubscribed from.
- From the sign-up: the country your browser’s time zone or language setting indicated (we do not look up your IP address for this) and whether the browser ran on a computer, a phone or a tablet, stored with the campaign details described under “Where you came from”.
Investment content (processed on customer instruction)
- Uploaded documents such as capital call and distribution notices, quarterly and annual reports, capital account statements, tax documents, term sheets, SPAs, SHAs, loan and convertible loan agreements and cap tables.
- Financial data extracted from those documents: commitments, called and distributed amounts, equalisation, NAV, valuations, share classes, ownership percentages, shareholder names and loan terms.
- Names and contact details of natural persons that appear in these documents, for example shareholders, founders or signatories.
- Documents received via inbound email ingestion at platform email addresses configured by the customer.
Portal access data
Where a customer activates automated portal retrieval, we store the access credentials required for that portal in encrypted form and use them exclusively to log in on the customer's behalf and download documents made available to the customer.
Crypto exchange access data
Where a customer connects a crypto exchange (currently Binance, Bitpanda, Coinbase, Crypto.com or Kraken), we store the API key and secret the customer creates there in encrypted form. We accept only keys that the exchange confirms may read and nothing else, and delete a key once the exchange reports that it may trade, transfer or withdraw. We use the key exclusively to read the balances and transactions of that account. The exchange is chosen by the customer and is not our subprocessor; it processes the requests under its own terms and privacy policy, which the customer has agreed to with it.
Technical data
- Log data: IP address, timestamp, requested resource, status code, referrer, browser and operating system.
- Security and audit records: sign-in events, document access, processing jobs and administrative actions.
Activity history and sign-in records
Every change to a record in a workspace is attributed to the person it was made for, whether they made it on a page, confirmed it in the chat or had one of our functions make it for them, and is shown to the members of the workspace under Settings, Activity history, with what was changed. Where a member opens a document or exports data, that is recorded there too. Where a member of our support team acts in a workspace, signed in as the customer or through our admin panel, the entry says that Valued support made it; it is never shown under the customer's name, and the staff member's identity is kept in our administrative audit log.
A sign-in, a failed sign-in and a change of the password or of the second factor are recorded with the time, the IP address, the kind of event and, for a sign-in, the method used (password or Google). Our administrators can read these records for a person on that person's page in our admin panel, to answer why somebody cannot get in.
4. Purposes and legal bases
- Provision of the Service, account administration, document processing and support — Art. 6(1)(b) GDPR (performance of a contract).
- Processing of investment content containing personal data — on the customer’s instruction, Art. 6(1)(b) and Art. 28 GDPR; the legal basis vis-à-vis the data subject is determined by the customer as controller.
- Answering the questions you ask in the chat, and writing the changes it proposes once you confirm them — Art. 6(1)(b) GDPR; for the investment content the chat reads, on the customer’s instruction as above.
- Research on the web about the organisations and people named in a workspace’s cap tables, holder lists and loans, started by a member of the workspace — Art. 6(1)(f) GDPR (legitimate interest of the customer in knowing who its co-investors and counterparties are, and ours in offering it); the persons concerned may object at any time.
- Billing, accounting and retention of commercial documents — Art. 6(1)(c) GDPR (legal obligation).
- Internal notice to our team when a payment is received, posted to a channel of our team in Slack (the name on the invoice, the name of the workspace, the amount, what was paid for and the invoice number) — Art. 6(1)(f) GDPR (legitimate interest in noticing incoming payments promptly and following up on them); you may object at any time.
- IT security, abuse prevention, logging, backups and troubleshooting — Art. 6(1)(f) GDPR (legitimate interest in a secure and stable service).
- Product improvement based on aggregated, anonymised usage statistics — Art. 6(1)(f) GDPR.
- Emails that the use of the Service requires, such as sign-in codes, security notices, invitations and billing notices — Art. 6(1)(b) GDPR.
- Notifications about your portfolio and emails that help you set up and use your account, including measuring whether they are opened and clicked — Art. 6(1)(f) GDPR (legitimate interest in informing customers about their own account and in sending only emails that are read); you can object at any time through the unsubscribe link in each of these emails. Details are under “Emails we send you”.
- Marketing emails and newsletters — Art. 6(1)(a) GDPR (consent), revocable at any time.
5. AI-assisted document processing, chat and research
Reading documents
To classify documents and extract financial data, the content of uploaded documents — or a machine-readable rendition of it — is transmitted to our AI provider Anthropic via its commercial API and processed there transiently to generate the extraction result.
- Customer documents and the data derived from them are not used to train AI models, neither by us nor by our AI provider.
- The API is used under a commercial agreement with data processing terms; inputs and outputs are not retained by the provider for its own purposes beyond the limited period required for abuse monitoring under its terms.
- Extraction results are always presented to the customer for review before they are stored in the portfolio; there is no automated decision-making producing legal effects within the meaning of Art. 22 GDPR.
- Where a customer selects file-only storage, no AI analysis of the document takes place.
Customers who do not wish specific documents to be processed by AI can upload them in file-only mode or enter the corresponding data manually.
The chat and the agent
The page of each asset (a fund, a company, a loan, a property, a listed security, a crypto wallet or exchange account) and the portfolio overview have a chat. When you ask a question there, we send to Anthropic your question, the stored data the question is about (figures, dates, the names of funds, companies, shareholders, lenders and borrowers, and stored notes), the stored documents or document pages the model needs to answer, and any file you attach to the question. The answer is stored with the conversation in your workspace, so that it can be read again and the conversation continued. A member of the workspace can delete a conversation; conversations are deleted with the workspace and with the account.
The chat can propose a change to a stored record: a figure, a date, a new entry. A proposal is written only after a member of the workspace confirms it, and the activity history records who did; a proposal that is rejected is not applied.
The same provider is used to classify the emails received at a workspace's import address (the sender, the subject and an excerpt of the text are sent), to prepare the outlook of a fund from its stored figures and terms, to translate stored AI texts into the workspace's language, and to decide whether two spellings in a cap table name the same holder. The terms on training and retention above apply to all of these uses.
Commentary and presentations of a report
When a member ticks the commentary of a report, we send to Anthropic the figures and names the report prints, so that the model can write a short commentary on them; every number in the commentary is checked against the report before it is shown. When a member has a report laid out as a presentation (“Designed by Claude”), we send the report's contents (its figures, tables, charts, texts and the names it prints) and the workspace's logo and colours to Anthropic, where a model builds the presentation file in Anthropic's code execution environment, using its Files API to hold the logo and the finished file during that run. The file is downloaded to the member's browser, and the files at Anthropic are deleted at the end of every run, also when it fails. Nothing of the report is stored at our end beyond the usage record. The terms on training and retention above apply to these uses as well.
Research about organisations and people
A member of a workspace can have a shareholder of its cap tables or a company on its watchlist researched on the web, using Anthropic's web search and page reading tools: what the organisation is, its website and logo, the people in its management and the companies it lists as investments. Since 27 October 2026 a natural person named in a workspace's cap tables or holder lists, or as the lender or borrower of one of its loans, can be researched in the same way, for what is public and professional only: who the person is as an investor, the positions they hold and the companies they are reported to have invested in. For this the person's name is sent to the provider, with the name of the company the record belongs to; for a portrait, their city and the other parties of their loans. Their street, postal code and any other detail from the documents are never sent.
- What we store: the description and positions found, the address of a public LinkedIn profile where a search result returned one, and, where a page we are allowed to read names the person and shows a portrait of one person, that photo with the address of the page it came from. Photos of the people in a watchlist company’s management are also taken, with their licence credit, from Wikidata and Wikimedia Commons, where those people’s names and the company’s name are looked up.
- Where it is shown: on the shareholder’s page, beside the loan and on the watchlist company’s page, to the members of the workspace. A portrait is stored in a private store of the workspace and shown through a short-lived signed link, never as a public image.
- When it happens: on a member’s click. In addition, a person on a cap table or a loan is looked up once by a scheduled run for a portrait; what it finds is kept as a suggestion that nobody sees until a member of the workspace accepts it, and a rejected suggestion is deleted and not looked for again.
- How it is removed: an owner or administrator of the workspace can remove a photo at any time, and the research of a person is kept in that workspace only, never shared with another, and deleted with the workspace. The research of an organisation is kept once per language and read by other workspaces whose cap tables name the same organisation.
The basis is our and the customer's legitimate interest in knowing who the co-investors and counterparties in a portfolio are (Art. 6(1)(f) GDPR); a person who is researched may object at any time through the contact details below, and we will then delete what was stored about them. Where the record a person appears in is investment content of which the customer is the controller, informing that person under Art. 14 GDPR is the customer's responsibility; we do not contact the persons researched.
6. Connecting Valued to ChatGPT
Users can connect a Valued workspace to ChatGPT, OpenAI's AI assistant, so that ChatGPT can read their investment information while answering their questions. The connection is optional, is set up only by the user and can be ended at any time.
What the user decides
- The user starts the connection in ChatGPT, signs in to Valued and selects one workspace.
- The user chooses which categories ChatGPT may read: investments and financial records (funds, direct investments, loans with the names of their lenders and borrowers, listed securities and real estate), stored document text and summaries, stored emails, and investment notes. Nothing is preselected.
- The connection can only read. It cannot change investments, upload or delete documents, send emails or execute transactions.
- Access ends after 30 days without use, and after 90 days at the latest; after that it requires the user’s consent again. The user can disconnect earlier under Settings → ChatGPT. Changing the password or the multi-factor authentication settings, or removal from the workspace, also ends it. Signing out of Valued does not.
- Every new connection is announced to the user by email.
What is transmitted to OpenAI
While the connection is active, ChatGPT requests information from Valued in response to the user's questions. Valued returns only records from the selected workspace and the selected categories, together with links to the corresponding pages in Valued. These records can contain personal data, for example names of shareholders, founders or signatories that appear in investment documents.
OpenAI is not our subprocessor. The transmission takes place on the user's instruction, and OpenAI processes the information it receives as a separate provider under its own terms and privacy policy, which the user has agreed to with OpenAI, including processing outside the European Union. Information already returned to ChatGPT remains in the existing conversation after the user disconnects; deleting it is done in ChatGPT.
What we record
- The connection itself: the user, the selected workspace and categories, the client (ChatGPT), when access was granted and last used, when it expires and when it was ended.
- For each read: the user and connection, which kind of information was requested, the identifier of a record that was opened, the outcome and the number of rows returned. We do not record the text of questions or searches, the content returned, or access tokens.
- Security events of the connection, such as consent granted, access revoked by the user or revoked after a reused credential, which are kept for 90 days and deleted after that at the next routine clean-up, which runs when a connection is set up.
These records serve the security of the Service and the investigation of misuse, on the basis of Art. 6(1)(f) GDPR. Transmitting the selected information to ChatGPT is part of performing the Service as requested by the user (Art. 6(1)(b) GDPR); for investment content uploaded by a customer, it takes place on that customer's instruction as described under "Two roles". Technical log data is retained as described under "Retention and deletion".
7. Sending documents to DATEV
A workspace on a plan that includes it can send a capital call or a distribution notice to its tax adviser through DATEV. Nothing is sent automatically: a member of the workspace opens the document, sees what will be sent and presses Send.
- What is sent: the original PDF and a short note built from the stored record, which can contain the fund’s name, the number of the notice, the amount and its currency, the dates, the payment reference, the IBAN and internal account or fund numbers. A value that is not stored is left out.
- How it is sent: either through DATEV’s interface to DATEV Unternehmen online, after a member of the workspace has signed in with DATEV and chosen the client, or by email to a DATEV Upload Mail address (always ending in uploadmail.datev.de), which we deliver through Google Workspace.
- What we store: the connection to DATEV (the chosen client and the access tokens DATEV issues, which only our backend can read and which are revoked on disconnecting), the Upload Mail address, and a record of each document sent: which document, by whom, when and the outcome.
DATEV eG is not our subprocessor. The transmission takes place on the customer's instruction to the customer's tax adviser, and DATEV processes the document under its agreement with the tax adviser or the customer. The basis is the performance of the Service as requested (Art. 6(1)(b) GDPR); for investment content uploaded by a customer, it takes place on that customer's instruction as described under "Two roles".
8. Hosting and place of processing
The application, the database and all uploaded documents are hosted within the European Union, in AWS data centres in the EU only. Backups, and a continuous copy of the database and the documents kept against the loss of a data centre, are stored in the EU as well.
Some of the specialised services listed below are provided by companies established outside the EU, and process data outside the EU (see the table below; for example, the payment notices to our team in Slack). In those cases, transfers are based on the EU Standard Contractual Clauses together with supplementary technical and organisational measures, and are limited to the data required for the respective function.
9. Subprocessors and service providers
We work with the following subprocessors and service providers. Those that handle personal data on our behalf are bound by a data processing agreement and process it only on our documented instructions; the providers of market and reference data receive no personal data.
| Provider | Purpose | Location |
|---|---|---|
| Amazon Web Services (AWS) | Hosting of the application database, document storage, authentication and backend functions; delivery of the application files; sending the emails described under "Emails we send you" and reporting whether they were delivered, opened and clicked, and receiving inbound documents sent to platform email addresses (Amazon Simple Email Service) | European Union, in AWS data centres in the EU only; application files, and the links counted in our emails, also delivered from AWS edge locations |
| Anthropic | AI models used to classify documents and extract financial data from uploaded files; to answer the questions asked in the chat of an asset’s page and of the portfolio, and to propose the changes a member confirms there; to classify emails received at a workspace’s import address; to prepare a fund’s outlook; to translate stored AI texts; to tell whether two spellings in a cap table name the same holder; and, on request, to write the commentary of a report and to lay out a report as a presentation in Anthropic’s code execution environment. Its web search and page reading tools are used for the research described under “Research about organisations and people” | United States (Standard Contractual Clauses; no training on customer data) |
| Stripe | Processing of subscription payments and billing data | EU / United States (Standard Contractual Clauses) |
| Browserbase | Automated, customer-initiated retrieval of documents from investor portals | United States (Standard Contractual Clauses) |
| PostHog | Product analytics and session recording: which pages are opened, which elements are clicked, and where the Service fails. Every form field and every text other than the Service’s own labels is masked in the browser before transmission, so no portfolio or document content is included | European Union (PostHog EU Cloud) |
| Slack | Internal notice to our team when a payment is received: the name on the invoice, the name of the workspace, the amount, what was paid for and the invoice number. No email address, no payment method and no portfolio or document data | United States (Standard Contractual Clauses) |
| Google Workspace (Google Ireland Limited) | Our company email: messages you send to our support or security addresses and our replies. For a workspace that sends documents to DATEV by email (DATEV Upload Mail, see "Sending documents to DATEV"), the delivery of that email | European Union and other locations (Standard Contractual Clauses under Google’s Cloud Data Processing Addendum) |
| Better Stack | Our status page at status.valued.com: announcements of maintenance and incidents, and, if you subscribe to it, your email address to notify you | United States and other locations (EU-U.S. Data Privacy Framework; Standard Contractual Clauses) |
| Twelve Data | Market data for listed securities (prices, dividends, company information) | European Union / United States |
| CoinGecko | Prices, price history and reference data for crypto assets. Receives the identifiers of coins and dates, no personal data | Outside the European Union; no personal data is transmitted |
| Frankfurter (European Central Bank data) | Foreign exchange reference rates for currency conversion | European Union |
We will inform customers of any intended change to this list in advance, giving them the opportunity to object for good cause. To be notified of changes, write to privacy@valued.com.
10. Retention and deletion
- Investment content and derived data are retained for the term of the contract and are deleted upon deletion of the account or on the customer’s documented instruction.
- Account data is deleted after the end of the contract, unless statutory retention periods apply.
- Invoices and accounting records are retained for the statutory periods under German commercial and tax law (generally six to ten years).
- Application, sign-in, firewall, network and load balancer logs are retained for 90 days, unless required longer to investigate a specific security incident. The access log of the document store and the record of maintenance run against the production database are retained for one year; the log of administrative actions in our cloud account for 400 days and its configuration history for 13 months; the audit log of our admin panel for three years.
- The activity history of a workspace is kept for three years, like the audit log of our admin panel, and goes earlier with the workspace.
- When a member leaves a workspace or deletes their own sign-in, the workspace keeps their name, email address and user identifier, so that it can still show who made the decisions and changes it records, for example who confirmed a figure, accepted a value or hid an entry. This record is kept as long as the workspace exists and is deleted with it. A former member may object to it at privacy@valued.com.
- The record of emails sent to you is deleted together with your account and, in any case, twelve months after the email was sent.
- Data contained in encrypted database backups is removed within the backup rotation of 14 days after deletion from the live system.
- Earlier versions of a deleted or replaced file are kept for up to 90 days, so that an accidental deletion can be undone, and are then removed.
Account deletion can be initiated from the account settings and is confirmed via a one-time code sent by email.
11. Your rights
As a data subject, you have the following rights under the GDPR:
- Access to the personal data we process about you (Art. 15).
- Rectification of inaccurate data (Art. 16).
- Erasure (Art. 17) and restriction of processing (Art. 18).
- Data portability in a structured, commonly used, machine-readable format (Art. 20).
- Objection to processing based on legitimate interests (Art. 21).
- Withdrawal of consent with effect for the future (Art. 7(3)).
Requests can be sent to privacy@valued.com. If your data was uploaded to the platform by one of our customers, we will forward your request to that customer as the responsible controller.
You also have the right to lodge a complaint with a supervisory authority, for example the Hamburg Commissioner for Data Protection and Freedom of Information (Der Hamburgische Beauftragte für Datenschutz und Informationsfreiheit).
12. Security measures
- Encryption of all traffic in transit via TLS and encryption of stored data at rest.
- Row-level security in the database so that each account can access only its own records.
- Role-based access control for team members and support for multi-factor authentication.
- Time-limited signed URLs for document downloads instead of publicly accessible file links.
- Separation of production and test environments, least-privilege access for administrators, and logging of administrative actions. Our staff reach a customer’s workspace only to give support or to handle abuse, through the admin panel or by signing in as the customer; each such action is written to our administrative audit log and appears in the workspace’s activity history as made by Valued support.
- Automated backups with point-in-time recovery and regular restore verification.
- Encrypted storage of portal credentials and secrets in a dedicated secret store.
Suspected vulnerabilities can be reported confidentially to security@valued.com. We investigate all reports and will not pursue good-faith security research.
13. Emails we send you
We send email only to people who have an account with us or who have written to us, and to third parties a customer asks us to contact on their behalf. All email is sent through our processor Amazon Web Services (Amazon Simple Email Service) in the European Union, except the email a workspace sends to DATEV, which is described under "Sending documents to DATEV", and our replies from our company email at Google Workspace.
Emails the Service requires
- Sign-in and confirmation: verification and reset codes, confirmation links.
- Security: notices that a password, a second factor, an email address or a connected application has changed, and the confirmation that an account has been deleted.
- Your team: invitations, and notices that an invitation was accepted, a member was removed or a role was changed.
- Your plan: notices about a failed payment, a plan that starts, changes or ends, and credits you have bought.
- Messages a member of our support team writes to you.
These emails belong to the contract and cannot be switched off. We do not measure whether they are opened or clicked.
Notifications about your portfolio
Members of an account are notified when something happens in it: a capital call, a distribution, a new document, a weekly report, a payment falling due, a price alert you set. These are switched on when an account is created. Each kind has its own switch under Settings, Notifications, and every such email carries two links: one that unsubscribes you from that kind of email and one that unsubscribes you from all notifications. Both work with one click and without signing in.
Emails that help you use your account
We look once a day at where an account stands (whether investments or documents have been added, whether documents are waiting for review, how many credits are left, when its owner last signed in) and may send the owner an email that fits: a first step after signing up, a reminder that documents are waiting, a notice that credits are running out, a note when you have not signed in for some weeks. An account's owner receives at most one of these per day, and none within two days of the last; a reminder that a data request you sent is still unanswered may come in addition. These emails have their own switches under Settings, Notifications, and the same two unsubscribe links. No profile is built beyond the state of the account described here, and nothing is passed on to third parties for advertising.
What we record and measure
- For every email we keep a record of what was sent to which address and when, and whether the receiving mail server accepted it, rejected it or the recipient reported it as spam. We need this to answer the question whether an email arrived, and to stop writing to addresses that do not exist.
- In notifications, in the emails that help you use your account and in the welcome email we also measure whether the email was opened and whether a link in it was clicked. For this the email contains a small image, and its links lead through the address links.app.valued.com, operated for us by Amazon Web Services, before they open the page. We record that and when this happened, not what you do afterwards.
- Most mail programs let you stop images from being shown automatically; the opening of the email is then not recorded.
- If you report one of our emails as spam, we switch off all notifications for your address.
The record is deleted together with your account and, in any case, twelve months after the email was sent.
15. Automated decisions, minors and changes
Automated decision-making: we do not carry out automated decision-making producing legal effects concerning you or similarly significantly affecting you.
Minors: the Service is directed exclusively at businesses and professional investors and is not intended for persons under 18 years of age.
Changes: we may update this policy to reflect changes to the Service or to legal requirements. Material changes will be communicated by email or through a notice in the application. The version and effective date at the top of this page always indicate the current version.
16. Contact
Privacy enquiries: privacy@valued.com
Security reports: security@valued.com
General contact: contact@valued.com
A data processing agreement pursuant to Art. 28 GDPR, including the current list of subprocessors, is available on request.
Effective date: 17 November 2026 · Version 2.18