Veraya Privacy Policy
How Veraya handles personal information
This Privacy Policy explains how Hewn Ventures LLC (“Veraya,” “we,” “us,” or “our”) collects, uses, discloses, and otherwise processes personal information when you use Veraya websites, applications, interfaces, and related services that link to this Policy (collectively, the “Service”), communicate with us, or otherwise interact with us.
1 Scope and roles
This Policy applies when Veraya determines why and how personal information is processed. If an organization uses Veraya to process personal information under its instructions, that organization may be the controller or business and Veraya may act as its processor or service provider. In that situation, direct requests about the organization’s data to the organization unless the Service says otherwise. Veraya does not currently offer business accounts or a data processing addendum; today this Policy covers individual, invite-only accounts.
This Policy does not govern a Connected Service, AI provider, website, or application operated by another company. Review that provider’s privacy notice before authorizing a connection.
2 Information we collect
Information you provide
- Account and profile information, such as name, email address, username, authentication and recovery information, organization affiliation, and profile preferences. Today this is your email address, a display name, and your GitHub username or Google account name and email if you sign in with them.
- Identity and Cognitive Passport information that you choose to provide, such as biographical details, preferences, creative history, identity attributes, memory items, rights preferences, and permission instructions. Today the Passport holds evidence from your conversations and imports, claims and principles derived from them, libraries, and the permission grants you create. Veraya has no dedicated fields for sensitive information, but your conversations may contain it.
- Content and communications, such as prompts, files, notes, records, feedback, support requests, and communications with Veraya.
Information from connected services and other sources
At your direction, Veraya may receive information from services you connect, such as AI providers, storage platforms, content tools, or other applications. This may include account identifiers, tokens or authorization grants, content, histories, model interactions, permissions, metadata, or results, depending on the scopes you approve. Today the only live sources are an Obsidian vault that you choose to import (note contents and file metadata) and sign-in with GitHub or Google (described below). Apps you grant access to through Permissions receive the Passport views you allow; they do not send information into Veraya.
When you sign in with GitHub (scopes read:user and user:email) or Google (scopes openid, email, and profile), we receive your account identifier, email address, and name or username from that provider. When you sign in by email, we send a single-use link through our email provider, Resend.
Information collected automatically
- Device and network information, such as IP address, browser type, operating system, device identifiers, language, and general location inferred from IP. Our servers record IP address, request path, and browser user-agent in operational logs, and we store the IP address that requested an email sign-in link.
- Usage and event information, such as pages or features viewed, actions taken, permissions changed, connection activity, timestamps, referring pages, and diagnostic events. Today Veraya records events in your Ledger, such as conversations, imports, permission changes, and deletions. Veraya does not currently run third-party product analytics. We plan to add PostHog analytics limited to usage metadata, not message content, and will update this Policy before enabling it.
- Log, security, and provenance information, such as authentication events, audit records, consent or permission changes, relevant system actions, error logs, and integrity signals. Ledger events are append-only during normal use and are deleted when you delete your account. Access attempts by connected apps are recorded separately and kept after account deletion as an audit record.
- Cookie and similar-technology information. Veraya uses only essential cookies: a sign-in session cookie and short-lived cookies that protect the sign-in flow. Your browser’s local storage keeps your theme, your active space, and your active thread. Veraya does not use advertising cookies, pixels, session replay, third-party analytics SDKs, or consent tooling.
3 Sensitive information
Identity, memory, and connected-service content may reveal sensitive information, including precise location, health information, racial or ethnic origin, religious or philosophical beliefs, sexual orientation, citizenship or immigration status, financial information, government identifiers, account credentials, biometric information, or information about children. Veraya should collect or process these categories only when the relevant feature supports them, the user has appropriate authority, and an applicable legal basis or consent exists. Veraya does not request, infer, or block specific sensitive categories. Anything you type in chat or import is stored with your conversations and Passport.
Do not provide sensitive information that the Service does not request or support.
4 How we use information
Subject to your settings, instructions, and applicable law, we use personal information to:
- provide, personalize, maintain, and support the Service;
- create and manage accounts, profiles, Cognitive Passport features, governed memory, permission states, provenance or audit records, exports, and connections;
- carry out your instructions and transmit information to Connected Services you authorize;
- authenticate users, prevent fraud and abuse, protect the Service, and investigate security incidents;
- communicate about accounts, transactions, changes, security, support, and service operations;
- analyze performance and improve usability, reliability, and features, using aggregated or de-identified information where appropriate;
- comply with law, enforce agreements, protect rights and safety, and establish or defend legal claims; and
- carry out another purpose disclosed when information is collected or with your consent.
Veraya does not use personal information for profiling, automated decision-making, fraud scoring, or research. Personalization is limited to Sam using your Passport and recent conversation history to answer you.
5 AI processing and model training
Veraya may process prompts, connected histories, governed memory, identity attributes, permissions, and other content to provide AI-enabled features or route instructions to Connected Services. The categories sent, provider, purpose, and applicable controls depend on the feature and the connection you choose. Today, chat messages, recent conversation history, and relevant Passport context are sent to OpenRouter, which routes them to the provider of the configured model. Web search and image generation requests are also handled through OpenRouter.
Veraya’s own model-training practice: Veraya does not train or fine-tune any model on your personal information or content.
Provider training practice: OpenRouter and the model providers it routes to process requests under their own terms and privacy policies, which may permit limited retention. Veraya does not currently offer a setting to choose providers.
Human access: The operator of Veraya can access stored data on the server for support, debugging, and safety. Server access is limited to the operator’s own accounts.
6 Legal bases for processing
Where a law requires a legal basis, we rely on one or more of the following: performance of a contract to provide the Service; our legitimate interests, such as securing, maintaining, and improving the Service, balanced against your rights; consent, which you may withdraw for future processing; and compliance with legal obligations or protection of vital interests.
7 How we disclose information
We may disclose personal information in the following circumstances, as applicable and verified:
- At your direction, including to a Connected Service, collaborator, organization, recipient, or public destination you select.
- To service providers that perform hosting, storage, authentication, security, analytics, communications, support, payment, or professional services under contractual restrictions. Today these are Fly.io (hosting and storage, United States), OpenRouter and the model providers it routes to (AI features), Resend (sign-in email), and GitHub and Google (sign-in).
- For legal and safety reasons, when we reasonably believe disclosure is required by law or necessary to protect rights, safety, security, users, or the public; prevent fraud or abuse; or establish or defend legal claims.
- In a corporate transaction, such as a financing, merger, acquisition, reorganization, bankruptcy, or sale of assets, subject to applicable law.
- With your consent or as otherwise disclosed when information is collected.
We may use and disclose aggregated or de-identified information where permitted by law.
8 Sale sharing and targeted advertising
Veraya does not sell personal information, does not share it for cross-context behavioral or targeted advertising, and does not disclose it in exchange for any benefit.
9 Cookies and similar technologies
We and our providers may use cookies and similar technologies for functions such as authentication, preferences, and security. Veraya does not use non-essential cookies, so there is no cookie settings page. Browser settings may block some technologies, but doing so can affect Service functions. Where required, we request consent before using non-essential technologies.
10 Data retention
We retain personal information for as long as reasonably necessary for the purposes described in this Policy, including to provide the Service, preserve user-selected provenance or audit records, comply with law, resolve disputes, enforce agreements, and protect the Service. Retention depends on the information type, user settings, account status, legal obligations, security needs, and whether deletion would undermine the integrity of a record the user asked us to maintain.
Account data, your Passport, conversations, generated images, and Ledger events are kept until you delete them or your account. Email sign-in links expire after 15 minutes. Encrypted Fly.io volume snapshots are kept for 5 days. Veraya does not hold connector tokens, analytics, marketing, or billing data. Deleting your account removes your conversations, chat history, Passport, Ledger, generated images, and sign-in records; only records of connected-app access attempts are kept as an audit record. Copies in encrypted backups expire within 5 days.
Deletion or withdrawal of permission may not delete information already sent to a Connected Service, information another party independently controls, records retained to meet legal obligations, or limited backup copies until they are overwritten. Backups are daily volume snapshots kept for 5 days. Ledger events cannot be edited; claims in your Passport can be corrected, disputed, marked private, or deleted.
11 Security
We use administrative, technical, and organizational safeguards designed to protect personal information. No system is completely secure, and we cannot guarantee absolute security. Data is stored on an encrypted Fly.io volume in the United States, connections use HTTPS, and session cookies are HttpOnly. Veraya does not hold security certifications.
If you believe your account or information is at risk, contact todd.anstis@hewnventures.com.
12 Your choices and controls
- Account and profile. Review or update information through Settings, or by emailing todd.anstis@hewnventures.com.
- Permissions and connections. Review or revoke supported permissions through Permissions. Revocation generally affects future access and cannot undo prior third-party processing.
- Export and portability. Request or create an export through Settings (Export Passport and Export Ledger), which immediately downloads JSON files.
- Deletion. Delete your Passport or your whole account in Settings (Delete Passport or Delete Account). Explain any retained provenance records, legal holds, backups, or organization-controlled information at the point of request.
- Cookies and advertising choices. Use your browser settings.
- Consent. Where processing relies on consent, withdraw it by emailing todd.anstis@hewnventures.com, without affecting processing before withdrawal.
We may need to verify your identity before completing a request. If an authorized agent submits a request, we may require proof of authority and direct verification where permitted. We will not unlawfully discriminate against you for exercising a privacy right.
13 U.S. state privacy rights
Depending on where you live and subject to exceptions, you may have rights to know or access personal information; correct inaccuracies; delete information; obtain a portable copy; opt out of certain sales, sharing, targeted advertising, or profiling; limit certain uses of sensitive information; and appeal a denied request. These rights vary by jurisdiction.
Submit a request through todd.anstis@hewnventures.com. Appeal a denied request by replying to our decision by email.
14 EEA UK and Swiss rights
If applicable, you may have rights to access, correct, erase, restrict, or object to processing; receive portable data; withdraw consent; and complain to a supervisory authority. You may also have rights relating to decisions based solely on automated processing that produce legal or similarly significant effects. Veraya does not make such decisions. The controller is Hewn Ventures LLC. Veraya has not appointed an EU or UK representative or a data protection officer.
Contact todd.anstis@hewnventures.com to exercise a right. You may also complain to the data protection authority where you live or work or where you believe a violation occurred.
15 International data transfers
Veraya and its providers may process information in countries other than where you live. Veraya’s servers are in the United States (Fly.io, Chicago region); OpenRouter and model providers may process requests in other countries. Where required, we use a recognized transfer mechanism, such as an adequacy decision or standard contractual clauses, and supplementary safeguards where appropriate.
16 Children
The Service is not intended for children under 18. We do not knowingly collect personal information from children under that age. If you believe a child provided personal information contrary to this Policy, contact us at todd.anstis@hewnventures.com. Accounts are created only by invitation, and Veraya does not offer teen, school, or family accounts.
17 Changes to this Policy
We may update this Policy to reflect changes in the Service, law, or our practices. We will update the “Last updated” date and provide additional notice or request consent when required. We post updates on this page and email account holders about material changes.
18 Contact us
Hewn Ventures LLC