Privacy Policy

Who we are

This Privacy Policy explains how Trenston (“we”, “us”), operated by Tansher Dhawan, Founder, collects and uses information when you use Trenston, our company cockpit product. Contact: contact@trenston.com. Postal address: BGC, Taguig, Philippines.

Who can use Trenston

Trenston is open to individuals and businesses worldwide. There is no geographic restriction. Before creating a company workspace, you must confirm that you are 18 or older, or that you are using Trenston under a parent or guardian's supervision. Trenston records that confirmation on your account. We do not independently verify age or guardian consent beyond that acknowledgment.

Account & profile data

When you sign up, we collect your name, email address, and company information needed to create your workspace. Authentication is handled by Clerk; we receive basic identity details (such as name, email, and profile picture when provided) to create and secure your session. We do not ask for additional personal profile fields beyond what is required to run your account.

Financial & business data

Trenston stores the business data you enter or generate in the product, for example revenue and expense entries, categories, tasks, decisions, reports, team roster, pipeline deals, and related workspace content. Financial figures come from what you manually enter, from documents you upload, or from accounting systems you explicitly connect (QuickBooks, Xero, or SAP Business One). Pipeline deal records may also come from HubSpot when you connect it.

Uploaded documents

Documents you upload (such as bills, receipts, or invoices) are stored in a private Cloudflare R2 bucket. Files are not publicly accessible. When you upload a document for extraction, it is sent to Anthropic's Claude API for automated parsing. No human at Trenston views your uploaded documents, only the automated Claude process does, solely to extract suggested entries for your workspace.

Google data

If you connect Google from Integrations, Trenston requests access to Google Calendar (read events, and write events when you create or update them in Trenston), Google Sheets (create a Financials export spreadsheet you trigger), and Google Drive files you pick in Trenston (bill import via drive.file, not full Drive). Trenston does not request any access to Gmail. Each teammate connects their own Google account; Trenston never surfaces another person's Google Calendar or files to you. Nothing from Google is accessed until you explicitly connect. Company-shared OAuth grants (QuickBooks, Xero, HubSpot, SAP) may only be used by the teammate who connected them, or by a workspace owner.

Trenston's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide and improve the features you trigger in Trenston (Calendar, Sheets export, and Drive file pick). We do not sell Google user data, do not use it for advertising, and do not transfer it to third parties except as needed to operate those features or as required by law.

CRM data (HubSpot)

HubSpot CRM data is pulled only if and when you explicitly connect HubSpot via Integrations. We sync deal metadata (name, associated company name, value, stage, and close date) into your workspace Pipeline. OAuth tokens for HubSpot are encrypted at rest. Nothing is accessed before that connection.

QuickBooks & Xero data

QuickBooks (Intuit) or Xero accounting data is pulled only if and when you explicitly connect that account via Integrations. From QuickBooks we sync invoices, sales receipts, credit memos, refund receipts, purchases, bills, vendor credits, and profit-and-loss lines from journal entries into your workspace Financials. From Xero we sync invoices and bills, credit notes, authorised bank receive/spend transactions, and revenue or expense lines from posted manual journals. Synced rows store amounts, categories, counterparty or description names, dates, notes, currency and tax fields when present, and provider transaction ids. OAuth tokens are encrypted at rest. Nothing is accessed before that connection. Connecting one accounting provider does not disconnect the other if both are configured.

SAP Business One data

SAP Business One data is pulled only if and when you explicitly connect it via Integrations by providing your Service Layer URL, company database name, username, and password. Those credentials (including the password and session identifiers used to sync) are encrypted at rest on Trenston servers. We sync A/R invoices, A/P purchase invoices, A/R credit notes, and A/P purchase credit notes into your workspace Financials (amounts, business partner names, comments, document dates, currency and tax fields when present). Nothing is accessed before that connection.

Slack alerts

If you configure a Slack Incoming Webhook on Integrations, Trenston stores that webhook URL encrypted at rest and may post to the channel you choose: a one-time connection test message, and later high-severity Decision Engine alert titles and details with a link back to Decisions in Trenston. Trenston does not use a full Slack OAuth app and does not read your Slack workspace history.

Payments

Paid subscriptions are processed by Paddle as merchant of record. Paddle collects billing details and may share limited transaction and customer identifiers with us so we can activate and manage your plan. We do not store full card numbers on Trenston servers. See our Refund & Billing Policy and the Billing page for plan details.

Email

Transactional emails (for example invitations or notices) are sent through Resend. Email addresses and message metadata needed to deliver those emails are processed accordingly.

AI processing

Trenston uses a third-party AI provider, Anthropic (Claude), for features including Ask Trenston chat, document and bill/receipt extraction, Decision Engine suggestions, Weekly Pack and Briefing summaries, report digests, and spreadsheet import. Ask Trenston chat messages (your questions and assistant replies) are stored in Trenston's database for your user in the workspace so you can reopen the conversation. When you use Ask Trenston, Trenston transmits a company snapshot to Anthropic that can include financial figures (when your role may access Financials), pipeline and department queue data you can access, people-roster counts, risk and open-decision titles, plus recent chat turns for multi-turn context. When you import a spreadsheet, Trenston sends the sheet names, header row, a few sample rows, and line labels so the AI can match columns; the whole file is not sent, and every value saved comes from your file, not from the AI. Other AI features transmit the document or workspace records needed for that request. Anthropic uses that context to generate the requested response or suggested entries for your workspace. Do not submit data you are not authorized to process with third-party AI providers. Trenston does not claim SOC 2, HIPAA, GDPR, or similar certifications based solely on this disclosure.

Trenston reaches Anthropic through its commercial API. Under Anthropic's commercial terms, inputs and outputs are not used to train its models by default, and Anthropic processes them on our behalf. Trenston itself does not train or fine-tune any model on customer data. When enabled, bill and receipt uploads may first be read by Google Cloud Document AI (Invoice Parser) to pull out vendor, date, and amounts, with Anthropic used when that parser is unavailable or not confident. That processing is run by Trenston and is separate from any Google account a teammate connects.

Cookies & session

We use a session/auth cookie to keep you logged in. We do not use tracking or advertising cookies. A small local preference may also record that you dismissed our cookie notice. You can clear cookies and site data in your browser.

Analytics & tracking

Trenston uses Vercel Web Analytics to count visitors and page views. It is cookieless and does not identify you personally. We also record first-party product usage events (for example which departments you enable) in our own MongoDB so we can improve Trenston. That usage data stays in Trenston's database and is not sent to Google Analytics or other advertising or analytics vendors. We do not use Google Analytics, session-recording, or advertising trackers.

To see where visitors drop off, we also count anonymous button clicks and sign-up page views (for example, which plan button was pressed). These counts carry no cookie, account, email, or IP address, and are skipped entirely if your browser sends Do Not Track.

Where data is stored

MongoDB Atlas: primary database for account and business data

Cloudflare R2: uploaded document files (private bucket)

Clerk: authentication and login/session data

Anthropic: processes AI feature inputs (documents, Ask Trenston context, summaries)

Google Cloud Document AI: optional first read of uploaded bills and receipts

Paddle: payment processing

Resend: transactional email

Vercel: hosting and cookieless web analytics (page views)

QuickBooks (Intuit): only for workspaces that connect it

Xero: only for workspaces that connect it

SAP Business One: only for workspaces that connect it (credentials stored encrypted; data pulled from your Service Layer)

HubSpot: only for workspaces that connect it

Google: only for teammates who connect their own Google account

Slack: only when you configure an Incoming Webhook (alert delivery to your channel)

Retention & deletion

When you delete your account, your personal data is removed from Trenston's database immediately, with no hold period on our side, and any workspace where you are the only owner is deleted with it. Where other people worked in a workspace, their history stays and your name in the activity log becomes "Deleted user". Our database and storage providers keep their own backups for a limited time, so a deleted record may remain in a provider backup until it ages out.

Workspace owners can export a data package for companies they own (database records as JSON, up to 5,000 rows per collection, integration tokens stripped, original uploaded files not included). Non-owner members receive their own account data plus a summary of workspaces they belong to. Account export is available on every plan. You can export and delete from Account Settings ( /app/settings). The full picture is on our Security page.

Governing law

This policy is governed by the laws of the Philippines. This may change once the business entity is formally registered in another jurisdiction.

Security practices

How Trenston protects workspaces, credentials, and uploaded files is described on our Security page.

Contact

Privacy questions: contact@trenston.com · Trenston · BGC, Taguig, Philippines.