Account and startup information
We store the information you provide to run your account and workspace: your name, email, startup profile, fundraising records, contacts and uploaded materials. Authentication, security and billing records support access, abuse prevention and payment reconciliation. Hosted payment providers handle card entry; FounderAss does not ask you to enter full card details into the workspace.
Optional Google and Microsoft connections
Connecting email and connecting a calendar are separate choices. After you grant permission, FounderAss can process the account identifier, email address, message and thread metadata, message bodies and attachments needed by mailbox features, or the calendar lists and events needed by calendar features. We use this information to display and organize your conversations, prepare drafts, synchronize events and carry out the actions you authorize. Signing up alone does not connect a mailbox or send messages.
Private mail and deliberate sharing
Your connected mailbox is private to its owner by default. Team membership alone does not open another founder’s private inbox. Selected messages and related information can become available to authorized workspace members when you explicitly share them. Sending a message or invitation shares the selected content with its recipients; external application forms and provider sites have their own policies.
Use of Google API data
FounderAss handles information received from Google APIs in accordance with the Google API Services User Data Policy, including its Limited Use requirements. Connected mailbox and calendar data is used for the user-facing productivity features you enable. It is not sold, used for advertising or unrelated profiling, or used to train general-purpose AI models. AI drafting, when available, is a separate configured feature; it does not itself send a message or publish workspace information.
Google API Services User Data Policy ↗Storage and retention
Authorization tokens and cached message bodies are encrypted before storage. Access controls protect workspace records and operational metadata. Private imported message bodies use a seven-day cache expiry by default; shared message bodies use a longer retention window of up to 365 days under the current rules. Message metadata, records you save to the workspace, security logs and payment history can remain for their respective operational purposes. Copies in backups may remain until those backups rotate.
Disconnecting and deleting information
You can disconnect an account in Settings → Connections. This removes its stored authorization tokens and pauses queued work that depends on the connection. Provider revocation is attempted, and you can also remove access in your Google or Microsoft account settings. The disconnect screen offers a separate choice to erase cached message bodies. Disconnecting does not delete the original messages or events in your provider account. For account or workspace deletion requests, contact info@camvi.uz; we verify ownership before handling a request.
Service providers and public pages
FounderAss uses infrastructure and service providers to operate hosting, authentication, transactional email, payment checkout and connected services. They receive the information needed for those functions. External map tiles, linked services and provider registration pages can receive browser requests under their own policies. Public investor and opportunity records are separate from private founder workspaces.
Questions and changes
We update this page when the service’s data handling changes. The date above identifies the current version. Send privacy questions, access concerns and deletion requests to info@camvi.uz. Do not include passwords, payment card details or mailbox authorization tokens in an email to support.