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

An example Stripe connection: a restricted key, encrypted with AES 256 in GCM mode before it is stored; a check on our server that sends two read requests and refuses a refund request before it leaves; customers, subscriptions and payments coming back into your workspace; and nothing written back to Stripe.

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

Pasting a key

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.

What StartupDeckAI reads from each connected tool
ToolWhat we readHow it connectsRead only key
Amplitude
  • Totals of daily active users and new users
A key you createNo, full access only
Chargebee
  • Subscriptions: plan, status, recurring amount and billing period
A key you createYes
GitHub
  • Repositories you choose
  • Their commits, pull requests and releases: titles, authors and dates
  • Not file contents
Approval in GitHub, grant checked, or a keyYes
HubSpot
  • Contacts: name, email and lifecycle stage
  • Deals: name, amount, stage, close date and which contacts they belong to
Approval in HubSpot, grant checked, or a keyYes
Intercom
  • Conversations: subject, state, rating, reply time and the customer email
  • Not the messages inside them
Approval in Intercom, grant not reported, or a keyYes
Jira
  • Issues: title, status, priority, assignee, labels and dates
A key you createNo, full access only
Linear
  • Issues: title, priority, state, assignee and completion date
Approval in Linear, grant checked, or a keyYes
Mailchimp
  • Sent campaigns: title, send time, emails sent, open rate and click rate
  • Not your audiences or subscribers
A key you createNo, full access only
Mixpanel
  • People profiles: id, name, email, and when they were first and last seen
  • Not individual events
A key you createNo, full access only
Notion
  • Page and database titles and when they were last edited
  • Only the pages you share with the integration, not their contents
Approval in Notion, grant not reported, or a keyYes
Paddle
  • Subscriptions: plan, status, amount and billing period
  • Completed transactions
A key you createYes
Pipedrive
  • Deals, their stages and their value
A key you createNo, full access only
PostHog
  • Event names and how many times each happened, for the project you choose
A key you createYes
Razorpay
  • Customers (name and email)
  • Subscriptions and their plans
  • Payments: amount, status and date
A key you createNo, full access only
Sentry
  • Issues: title, how many events and users each affects, and when it was last seen
  • Not stack traces or event details
A key you createYes
Slack
  • 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
Approval in Slack, grant checked, or a keyYes
Stripe
  • Customers (name and email)
  • Subscriptions and their plans
  • Charges: amount, status and date
Approval in Stripe, grant checked, or a keyYes
Vercel
  • Projects and their deployments: status, time and duration
A key you createNo, full access only
Zendesk
  • Tickets: subject, status, priority, dates and the requester's email
  • Not the messages inside them
A key you createNo, 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 StartupDeckAI keeps
WhatWhat exactly
The key you paste, or the access token a tool gives usEncrypted 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 toolOnly the fields listed for it in section 4, and nothing it says we do not read.
Totals we work outFigures such as monthly recurring revenue, churn and customer counts, kept as company totals with no names or emails in them.
What you writeYour notes, decisions and the questions you ask Founder OS.
What Founder OS writesIts 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

7. Accounts and workspaces

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