Security
Connecting a payment account takes trust. This page says exactly what StartupDeckAI can do with a connected tool, what it keeps, and how to take it all back.
Updated 16 November 2026 Read only connections
On this page 1 of 9
- 1. The short version
- 2. Read only, enforced in code
- 3. Your keys and approvals
- 4. What we read from each tool
- 5. What we keep
- 6. Disconnecting and deleting
- 7. Accounts and workspaces
- 8. Where data is processed
- 9. Reporting a problem
1. The short version
- We only read. StartupDeckAI is built to read and nothing else. It does not move money, issue refunds, or create, change or delete anything in a tool you connect, and our server refuses any request that is not a read before it leaves.
- Many tools do not need a key from you. You approve StartupDeckAI in the tool's own screen, we ask for read access only, and we refuse the connection if the tool grants more.
- Your keys and tokens are encrypted. With AES 256 in GCM mode, before they are stored.
- We keep only what we list. Section 4 names the fields we read from each tool. We do not keep card details or the text of your messages.
- You can take it all back. Disconnecting a tool deletes its key and every record we imported from it, straight away, and for an approved tool asks the tool to end our access too.
No service is perfectly secure, so we describe what we actually do rather than promise the impossible. If anything here is unclear, email support@startupdeck.in and a person will answer.
2. Read only, enforced in code
Every request StartupDeckAI sends to a connected tool, payment tools included, goes through one check on our server. It lets a request through only if it reads: a GET, or one of three named lookups that some tools send as a POST (a Slack token check, a Notion search and a Linear query). The only other requests allowed are the sign in steps for GitHub, HubSpot, Intercom, Linear, Notion, Slack and Stripe, which swap the code you approved for an access token and change nothing in your account. Anything else is refused and never sent. A separate, equally short list covers the one request that is not a read: asking a tool to end our own access when you disconnect.
That check is the second lock. The first is the key itself. Where a tool lets you limit a key to read access, the connect dialog asks you to, so even a mistake on our side could not write with it. Stripe keys must be restricted keys, starting with rk_. We refuse full secret keys.
Tools whose keys cannot be limited
Some tools only issue keys with full access: Amplitude, Jira, Mailchimp, Mixpanel, Pipedrive, Razorpay, Vercel, Zendesk. For these, our read only check is the only safeguard, and the connect dialog says so. If that is not enough for you, start with a tool whose key can be limited and add the others later.
3. Your keys and approvals
Approving StartupDeckAI in the tool
- For GitHub, HubSpot, Intercom, Linear, Notion, Slack and Stripe, you can connect without creating a key. The tool's own screen asks you to allow the read permissions the connect dialog lists, and nothing else.
- Where the tool reports what it granted, we check the grant before storing anything. If it can do more than read, we refuse to connect and ask the tool to end that grant. Intercom and Notion does not report this, so there we rely on the read only check in our code and on the capabilities you chose when the integration was created.
- Access tokens are checked with the tool, then encrypted with AES 256 in GCM mode before they are stored. Where a tool's tokens expire, we renew them before use and store the new one the same way.
- When you disconnect, we delete our copy and ask the tool to end our access. If the tool does not confirm, we tell you and where to remove StartupDeckAI yourself.
Pasting a key
- You create the key in your own account with the tool. We never ask for your password to that tool.
- The key is checked with the tool, then encrypted with AES 256 in GCM mode before it is stored.
- The encryption secret is kept apart from the database, and the server will not store a key without it.
- We never show a key again after you paste it, and keys are kept out of our logs.
- Revoking the key in the tool cuts our access at once, whatever happens on our side.
4. What we read from each tool
This is the same list the connect dialog shows before you approve or paste anything. The third column says how the tool connects, and the last whether the tool can limit a pasted key to read access.
| Tool | What we read | How it connects | Read only key |
|---|---|---|---|
| Amplitude |
| A key you create | No, full access only |
| Chargebee |
| A key you create | Yes |
| GitHub |
| Approval in GitHub, grant checked, or a key | Yes |
| HubSpot |
| Approval in HubSpot, grant checked, or a key | Yes |
| Intercom |
| Approval in Intercom, grant not reported, or a key | Yes |
| Jira |
| A key you create | No, full access only |
| Linear |
| Approval in Linear, grant checked, or a key | Yes |
| Mailchimp |
| A key you create | No, full access only |
| Mixpanel |
| A key you create | No, full access only |
| Notion |
| Approval in Notion, grant not reported, or a key | Yes |
| Paddle |
| A key you create | Yes |
| Pipedrive |
| A key you create | No, full access only |
| PostHog |
| A key you create | Yes |
| Razorpay |
| A key you create | No, full access only |
| Sentry |
| A key you create | Yes |
| Slack |
| Approval in Slack, grant checked, or a key | Yes |
| Stripe |
| Approval in Stripe, grant checked, or a key | Yes |
| Vercel |
| A key you create | No, full access only |
| Zendesk |
| A key you create | No, full access only |
Amplitude
- What we read
- Totals of daily active users and new users
- How it connects
- A key you create
- Read only key
- No, full access only
Chargebee
- What we read
- Subscriptions: plan, status, recurring amount and billing period
- How it connects
- A key you create
- Read only key
- Yes
GitHub
- What we read
- Repositories you choose
- Their commits, pull requests and releases: titles, authors and dates
- Not file contents
- How it connects
- Approval in GitHub, grant checked, or a key
- Read only key
- Yes
HubSpot
- What we read
- Contacts: name, email and lifecycle stage
- Deals: name, amount, stage, close date and which contacts they belong to
- How it connects
- Approval in HubSpot, grant checked, or a key
- Read only key
- Yes
Intercom
- What we read
- Conversations: subject, state, rating, reply time and the customer email
- Not the messages inside them
- How it connects
- Approval in Intercom, grant not reported, or a key
- Read only key
- Yes
Jira
- What we read
- Issues: title, status, priority, assignee, labels and dates
- How it connects
- A key you create
- Read only key
- No, full access only
Linear
- What we read
- Issues: title, priority, state, assignee and completion date
- How it connects
- Approval in Linear, grant checked, or a key
- Read only key
- Yes
Mailchimp
- What we read
- Sent campaigns: title, send time, emails sent, open rate and click rate
- Not your audiences or subscribers
- How it connects
- A key you create
- Read only key
- No, full access only
Mixpanel
- What we read
- People profiles: id, name, email, and when they were first and last seen
- Not individual events
- How it connects
- A key you create
- Read only key
- No, full access only
Notion
- What we read
- Page and database titles and when they were last edited
- Only the pages you share with the integration, not their contents
- How it connects
- Approval in Notion, grant not reported, or a key
- Read only key
- Yes
Paddle
- What we read
- Subscriptions: plan, status, amount and billing period
- Completed transactions
- How it connects
- A key you create
- Read only key
- Yes
Pipedrive
- What we read
- Deals, their stages and their value
- How it connects
- A key you create
- Read only key
- No, full access only
PostHog
- What we read
- Event names and how many times each happened, for the project you choose
- How it connects
- A key you create
- Read only key
- Yes
Razorpay
- What we read
- Customers (name and email)
- Subscriptions and their plans
- Payments: amount, status and date
- How it connects
- A key you create
- Read only key
- No, full access only
Sentry
- What we read
- Issues: title, how many events and users each affects, and when it was last seen
- Not stack traces or event details
- How it connects
- A key you create
- Read only key
- Yes
Slack
- What we read
- Channel names and member names with their job titles
- How many messages each channel received in the last day
- Not the text of messages: we count them and keep nothing else
- How it connects
- Approval in Slack, grant checked, or a key
- Read only key
- Yes
Stripe
- What we read
- Customers (name and email)
- Subscriptions and their plans
- Charges: amount, status and date
- How it connects
- Approval in Stripe, grant checked, or a key
- Read only key
- Yes
Vercel
- What we read
- Projects and their deployments: status, time and duration
- How it connects
- A key you create
- Read only key
- No, full access only
Zendesk
- What we read
- Tickets: subject, status, priority, dates and the requester's email
- Not the messages inside them
- How it connects
- A key you create
- Read only key
- No, full access only
5. What we keep
We do store data. Founder OS needs it to answer questions about your company and to keep a record of your decisions. This is everything it keeps from a connection.
| What | What exactly |
|---|---|
| The key you paste, or the access token a tool gives us | Encrypted before it is stored. Never shown again and never written to logs. For a Stripe approval we keep only the account id. |
| Payment tools (Stripe, Razorpay) | Customers (name and email), subscriptions and their plans, and payments: amount, currency, status and date. Not card details, billing addresses or anything else in the provider's record. |
| Every other tool | Only the fields listed for it in section 4, and nothing it says we do not read. |
| Totals we work out | Figures such as monthly recurring revenue, churn and customer counts, kept as company totals with no names or emails in them. |
| What you write | Your notes, decisions and the questions you ask Founder OS. |
| What Founder OS writes | Its answers and briefs, which can quote figures from your tools. |
The key you paste, or the access token a tool gives us
- What exactly
- Encrypted before it is stored. Never shown again and never written to logs. For a Stripe approval we keep only the account id.
Payment tools (Stripe, Razorpay)
- What exactly
- Customers (name and email), subscriptions and their plans, and payments: amount, currency, status and date. Not card details, billing addresses or anything else in the provider's record.
Every other tool
- What exactly
- Only the fields listed for it in section 4, and nothing it says we do not read.
Totals we work out
- What exactly
- Figures such as monthly recurring revenue, churn and customer counts, kept as company totals with no names or emails in them.
What you write
- What exactly
- Your notes, decisions and the questions you ask Founder OS.
What Founder OS writes
- What exactly
- Its answers and briefs, which can quote figures from your tools.
We do not sell any of it, and we do not use it to train public AI models. When you ask Founder OS a question, the relevant records are sent to the AI providers listed in our privacy policy to write the answer.
6. Disconnecting and deleting
- Disconnecting a tool deletes its key and every record we imported from it in one step. Either all of it goes, or nothing changes and you can try again. There is no waiting period.
- Notes and decisions you wrote yourself are not deleted when you disconnect a tool.
- Company totals we already worked out, such as last month's recurring revenue, stay in your history. They hold no names or emails.
- Answers and briefs Founder OS already wrote also stay in your history, and they can quote figures from the tool. Deleting your account removes them.
- To delete your whole account and everything in it, email support@startupdeck.in from the address on your account. The privacy policy says how long that takes.
7. Accounts and workspaces
- Passwords are never stored. We keep only a salted hash.
- Two step sign in is available, by email code or an authenticator app.
- Every request is checked on the server against the account and company it belongs to, so one customer cannot reach another's workspace or connections.
- All traffic uses HTTPS.
- Payments to us go through Razorpay. We never see your card number.
The full list of what we do is in the privacy policy.
8. Where data is processed
StartupDeckAI is run from India. Some of our providers process data in other countries, including the United States for AI processing. The privacy policy names each provider and what it does. Businesses doing procurement can ask for our security answers at support@startupdeck.in.
9. Reporting a problem
Found a security problem?
Please tell us before you tell anyone else. Email support@startupdeck.in with the subject "[Security]" and the steps to reproduce it. Do not include real customer data, passwords or keys. Our security.txt says the same. We will not take action against people who report in good faith and do not harm others' data.
Worried about a connection?
Revoke the key in the tool first, then disconnect it in Founder OS. That cuts access at once. Then email us and we will check what happened.
Read next
- Privacy Policy What we collect, why, and how long we keep it.
- Terms of Service The rules for accounts, plans and connected tools.
- Documentation How connections work and what each tool is read for.
- Help and support Get a person to look at your account or bill.
- Contact us Questions about these documents or your data.