Privacy Policy
What StartupDeckAI collects, why we collect it, who sees it, how long we keep it, and what you can ask us to do with it.
Updated 16 November 2026
On this page 1 of 17
- 1. Overview
- 2. Who we are
- 3. What we collect
- 4. Connected accounts
- 5. AI and your content
- 6. How we use data
- 7. Cookies and similar tools
- 8. Service providers
- 9. Where data is processed
- 10. How we protect data
- 11. Keeping and deleting data
- 12. Your rights
- 13. If something goes wrong
- 14. Children
- 15. Changes to this policy
- 16. Complaints and the Grievance Officer
- 17. Contact
Ask about your data
Ask for a copy, a correction or deletion by email, from the address on your account.
support@startupdeck.in
1. Overview
This policy explains how StartupDeckAI handles personal data when you visit our website, create an account, validate an idea, use Founder OS, or connect other tools. It is written to be read. If a sentence is unclear, email us and we will explain it.
We do not sell your ideas, reports, connected account data or credentials. We do not use them to train public AI models. We do not show advertising inside your workspace. One thing to know: on the Free plan and during a trial, some AI requests can reach providers that keep what they receive and may use it to improve their own models. Section 5 says when, and what to avoid sending.
This policy is designed to meet India's Digital Personal Data Protection Act, 2023 and, where they apply to you, the GDPR, the UK GDPR and the California Consumer Privacy Act. It sits alongside our Terms of Service.
2. Who we are
StartupDeckAI is run by Yash Suthar from Mumbai, Maharashtra, India. For the personal data of people who use the product, such as your name and email, we decide why and how the data is used. In the privacy law of India we are the Data Fiduciary.
Your workspace may also contain personal data about other people, for example a customer's email address that arrives from a tool you connect. For that data, you decide why it is processed and we process it for you, only to provide the features you use. You are responsible for having the right to share it with us.
3. What we collect
Account information
- Your name, email address and username, and a hashed password if you sign up with a password.
- Sign in details from Google if you choose to sign in with it.
- Your plan, subscription status, trial status and notification choices.
- Whether two step sign in is on, and hashed backup codes if you create them.
Billing information
- Payment is handled by Razorpay. We receive references, the plan, amounts, dates and status, never your full card or UPI details.
- To save you typing, we fill in your name and email address in Razorpay's payment window. You can change them there before you pay.
- Invoices and the tax details you give us for an invoice, such as a GSTIN.
Content you create
- Ideas you submit, and the reports, scores and downloads made from them.
- Founder OS records you save: company details, memory entries, decisions and their outcomes, and briefings.
- What you write in the support chat, whether to the assistant or to a person on our team, and the replies. The assistant's replies come from an AI model, as section 5 explains.
Data from tools you connect
Only what is listed for each tool in section 4, and only after you connect it.
Technical information
- Your IP address, browser, device type and the pages and actions that run on our servers.
- The country your connection appears to be in, which we use to show prices in your currency. It does not change what you pay.
- Security events such as sign ins, password changes and failed attempts.
- Errors, so we can find and fix them.
- Your cookie choice.
4. Connected accounts
Connecting a tool is always your choice, and there are two ways to do it. For GitHub, HubSpot, Intercom, Linear, Notion, Slack and Stripe, you approve StartupDeckAI in the tool's own screen, so you do not create or paste a key. The tool gives us access limited to what you approved, and we encrypt what it gives us like a key. For every tool, you can instead create a key in your own account with that tool and paste it into Founder OS. Either way, StartupDeckAI then reads from the account. It never creates, changes or deletes anything in it.
- Read only is enforced in our code. Every request to a connected tool passes through one check that refuses anything other than a read.
- Approvals ask for read access only. When you approve StartupDeckAI in a tool's own screen, we ask only for the read permissions listed in the connect dialog. Where the tool tells us what it granted, we check the grant and refuse to connect if it can do more than read. Notion does not report this, and the dialog says so.
- Limit the key where you can. Where a tool lets you restrict a key to read access, the connect dialog asks you to, so even a mistake on our side could not write. Where a tool cannot, the dialog says so.
- Your keys and access tokens are encrypted. We encrypt them with AES 256 in GCM mode before they are stored. We never show them again and never write them to logs. For Stripe approvals we store no token at all, only the account id Stripe gave us.
- You choose the scope. For tools that allow it, you choose which repositories, pages, projects or channels a connection can reach.
- You can leave at any time. Disconnecting deletes the key and the records we imported from that tool. For a tool you approved, we also ask the tool to end our access, and tell you if it did not confirm. Revoking the key or the approval in the tool itself cuts access immediately.
- We identify ourselves. Requests carry a StartupDeckAI user agent, slow down when a tool asks us to, and stop after a few tries.
What we read from each tool, and how it connects, is shown below, and again in the connect dialog before you approve or paste anything.
| Tool | What we read | How it connects | Provider's terms |
|---|---|---|---|
| Amplitude |
| A key you create | Read the terms |
| Chargebee |
| A key you create, limited to read access | Read the terms |
| GitHub |
| Approval in GitHub (we check the grant is read only), or a key you create | Read the terms |
| HubSpot |
| Approval in HubSpot (we check the grant is read only), or a key you create | Read the terms |
| Intercom |
| Approval in Intercom (the tool does not report the grant), or a key you create | Read the terms |
| Jira |
| A key you create | Read the terms |
| Linear |
| Approval in Linear (we check the grant is read only), or a key you create | Read the terms |
| Mailchimp |
| A key you create | Read the terms |
| Mixpanel |
| A key you create | Read the terms |
| Notion |
| Approval in Notion (the tool does not report the grant), or a key you create | Read the terms |
| Paddle |
| A key you create, limited to read access | Read the terms |
| Pipedrive |
| A key you create | Read the terms |
| PostHog |
| A key you create, limited to read access | Read the terms |
| Razorpay |
| A key you create | Read the terms |
| Sentry |
| A key you create, limited to read access | Read the terms |
| Slack |
| Approval in Slack (we check the grant is read only), or a key you create | Read the terms |
| Stripe |
| Approval in Stripe (we check the grant is read only), or a key you create | Read the terms |
| Vercel |
| A key you create | Read the terms |
| Zendesk |
| A key you create | Read the terms |
Amplitude
- What we read
- Totals of daily active users and new users
- How it connects
- A key you create
- Provider's terms
- Read the terms
Chargebee
- What we read
- Subscriptions: plan, status, recurring amount and billing period
- How it connects
- A key you create, limited to read access
- Provider's terms
- Read the terms
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 (we check the grant is read only), or a key you create
- Provider's terms
- Read the terms
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 (we check the grant is read only), or a key you create
- Provider's terms
- Read the terms
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 (the tool does not report the grant), or a key you create
- Provider's terms
- Read the terms
Jira
- What we read
- Issues: title, status, priority, assignee, labels and dates
- How it connects
- A key you create
- Provider's terms
- Read the terms
Linear
- What we read
- Issues: title, priority, state, assignee and completion date
- How it connects
- Approval in Linear (we check the grant is read only), or a key you create
- Provider's terms
- Read the terms
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
- Provider's terms
- Read the terms
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
- Provider's terms
- Read the terms
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 (the tool does not report the grant), or a key you create
- Provider's terms
- Read the terms
Paddle
- What we read
- Subscriptions: plan, status, amount and billing period
- Completed transactions
- How it connects
- A key you create, limited to read access
- Provider's terms
- Read the terms
Pipedrive
- What we read
- Deals, their stages and their value
- How it connects
- A key you create
- Provider's terms
- Read the terms
PostHog
- What we read
- Event names and how many times each happened, for the project you choose
- How it connects
- A key you create, limited to read access
- Provider's terms
- Read the terms
Razorpay
- What we read
- Customers (name and email)
- Subscriptions and their plans
- Payments: amount, status and date
- How it connects
- A key you create
- Provider's terms
- Read the terms
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, limited to read access
- Provider's terms
- Read the terms
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 (we check the grant is read only), or a key you create
- Provider's terms
- Read the terms
Stripe
- What we read
- Customers (name and email)
- Subscriptions and their plans
- Charges: amount, status and date
- How it connects
- Approval in Stripe (we check the grant is read only), or a key you create
- Provider's terms
- Read the terms
Vercel
- What we read
- Projects and their deployments: status, time and duration
- How it connects
- A key you create
- Provider's terms
- Read the terms
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
- Provider's terms
- Read the terms
Your agreement with each tool still applies
You connect under the terms you already have with the provider. You must be allowed to share that account's data with us, and you should keep to any limits those terms set. Product names and logos belong to their owners and do not imply endorsement. See our trademark notice and the connection guide.
Developer API keys
If you create a StartupDeckAI API key, we store only a hash of it and show the full value once, when you create it. Keep it secret and revoke it if it is exposed. Use of the API is covered by our acceptable use rules.
5. AI and your content
- Validation reports, Founder OS briefings and the support assistant send the text they need to an AI model and return the result to you: first to Anthropic's Claude models, and through OpenRouter when Anthropic cannot answer. They do not send more than the request requires. A quick analysis uses fixed rules and sends nothing to an AI model.
- A validation report searches the web before the AI model is asked. The idea's title, industry and location, and sometimes a few single words from its description, are sent to the search services named in section 8. Your name, email and account are not sent to them. The methodology page lists every place that is searched.
- Documents you add to Founder OS (call notes, investor emails and the like) are stored with your company. To make them searchable by meaning, their text is sent to Voyage AI, which returns numbers that describe it. Deleting a document deletes its text, every passage taken from it and any saved Ask answer that quoted it.
- Ask answers a question from your connected tools and documents through the same Founder OS model. Each answer is saved with your company, with the evidence it cited, so you can read it again.
- We do not use your ideas, reports or workspace data to train public AI models, and we do not sell your prompts.
- On Pro, Pro Plus and Enterprise, validation reports and the support assistant run on paid models: Anthropic's Claude first, which under Anthropic's commercial terms does not train on what we send, and otherwise paid models through OpenRouter, where every request tells OpenRouter to use only providers that do not keep or train on what we send, as far as the provider's terms allow. Founder OS, on Pro Plus and Enterprise, runs the same way.
- On Free and during a trial, validation reports and the support assistant go to Anthropic's Claude first as well. When Anthropic cannot answer, they run on models that OpenRouter offers free of charge. The companies behind those models may keep what we send for a time and may use it to improve their models, under their own terms, which are theirs and not ours. The same is true of the support chat for people who are not signed in. So on those plans do not submit anything you would not want a third party to read.
- AI output can be wrong, out of date or incomplete. It is a draft for you to check, not advice. See the Terms of Service.
- Please do not put passwords, API keys, health records or government identity numbers into an idea, a note or the support chat.
6. How we use data
We use personal data to:
- Create and run your account, and give you the plan you chose.
- Produce the reports, briefings and support replies you ask for.
- Take payment, issue invoices and respond to billing questions.
- Send service emails: sign in codes, receipts, security alerts, notices about a problem that affected your account or a report, and changes to these documents.
- Send a weekly digest, product updates and the occasional request for feedback about the service, if you have left those switched on. You can switch them off in Settings, or reply "stop" to any of them.
- Answer support requests.
- Keep the service secure, stop abuse and fraud, and meet legal duties.
- Measure and improve the product. Google Analytics runs only if you accepted analytics cookies. Cloudflare and Vercel also count page visits, without cookies, as section 7 explains.
Where the law asks for a legal basis, ours are your consent, the contract we have with you, our legitimate interest in running a secure service, and our legal duties.
7. Cookies and similar tools
A banner on first visit lets you accept or decline cookies that are not essential. Your choice is stored, and declining never limits what you can do in a paid workspace.
| Kind | What it does | When it runs |
|---|---|---|
| Essential | Keep you signed in, protect forms against forgery, and remember your cookie choice. | Always on. The service does not work without them. |
| Analytics | Google Analytics shows us which pages and features are used, so we can fix and improve them. | Off until you accept. |
| Advertising | Google AdSense shows advertising on public pages. | Off until you accept. Never used inside your workspace. |
Essential
- What it does
- Keep you signed in, protect forms against forgery, and remember your cookie choice.
- When it runs
- Always on. The service does not work without them.
Analytics
- What it does
- Google Analytics shows us which pages and features are used, so we can fix and improve them.
- When it runs
- Off until you accept.
Advertising
- What it does
- Google AdSense shows advertising on public pages.
- When it runs
- Off until you accept. Never used inside your workspace.
Separately, Cloudflare, which carries traffic to our site, and Vercel, which serves it, count visits to pages with their web analytics. Neither sets a cookie or stores anything on your device, so they run whatever you choose in the banner. They see what any visit to a website shows: your IP address, browser and the page you asked for. Both are listed in section 8.
Some product update emails contain a small image and tracked links, which tell us whether the email was opened, which links were clicked and the kind of device it was read on. Switching product updates off in Settings stops those emails. Sign in codes, receipts and the short notes our founder writes to you do not track opening.
To change your choice, use Cookie settings at the bottom of any public page and the banner returns. Turning a cookie off reloads the page, so nothing keeps running. Your browser settings can also block cookies, although the service will not stay signed in without the essential ones.
8. Service providers
We use other companies to run parts of the service. They handle data only for the purpose listed, on our instructions, and under confidentiality and security obligations.
| Provider | What it does for us |
|---|---|
| Razorpay | Takes subscription payments in Indian rupees. We never see your full card or UPI details. |
| Supabase | Hosts our database and the files stored with it, in Mumbai, India. |
| Vercel | Serves the website. Its Web Analytics counts visits to pages without cookies and without storing anything on your device. |
| Redis Cloud | Holds sign in sessions and short lived copies of data, in Mumbai, India, so the product stays fast. |
| Cloudflare | Runs our domain and sits in front of the website and servers, routing traffic and blocking attacks, so it sees your IP address and the pages you ask for. Its Web Analytics counts visits to pages without cookies and without storing anything on your device. |
| Render | Runs the servers behind the product, in the United States, where reports are made and connected tools are read. |
| Resend, with Gmail as a fallback | Sends sign in codes, receipts, support replies and other service emails. |
| Anthropic | Turns a validation request, a Founder OS answer or a support question into an answer with its Claude models. It is tried first for every AI request. Only the text a request needs is sent, and under Anthropic's commercial terms it is not used to train its models. |
| OpenRouter and the AI models behind it | Answer a request when Anthropic cannot, for example during an outage. Only the text a request needs is sent. Section 5 says what each kind of request allows the provider to keep. |
| Tavily | Runs the web searches a validation report makes before the AI model is asked. The idea's title, industry and location are sent, and sometimes a few single words from its description. Your name, email and account are not. |
| NewsAPI | Searched for recent news about an idea's market when a validation report is made. Words that describe the idea's industry and location are sent. Your name, email and account are not. |
| Hacker News Search (run by Algolia) and GitHub | Searched for stories and open source projects on an idea's subject when a validation report is made. A few single words that describe the idea are sent. Your name, email and account are not. |
| Voyage AI | Turns the text of documents you add to Founder OS into the numbers that let us search it by meaning. Only that text is sent. |
| Google Analytics | Shows us which pages and features are used. Runs only if you accept analytics cookies. |
| Google AdSense | Shows advertising on public pages. Runs only if you accept advertising cookies. |
| Google Fonts | Delivers the typefaces used on some pages, so your browser contacts Google when they load. |
| Logo.dev, Simple Icons and Unavatar | Supply the logos shown next to connected tools, so your browser contacts them when logos load. |
| StartupBase, Uneed, Findly.tools, Wired Business and PeerPush | Directories that list StartupDeckAI. Their "Featured on" badges on our public pages are images served by the directories, so your browser contacts them when the badges load. Nothing about your account is sent. |
| Sentry | Receives crash and error reports from the website and servers so we can fix faults. Email addresses, passwords, keys and the text of ideas and reports are removed before a report is sent. |
Razorpay
- What it does for us
- Takes subscription payments in Indian rupees. We never see your full card or UPI details.
Supabase
- What it does for us
- Hosts our database and the files stored with it, in Mumbai, India.
Vercel
- What it does for us
- Serves the website. Its Web Analytics counts visits to pages without cookies and without storing anything on your device.
Redis Cloud
- What it does for us
- Holds sign in sessions and short lived copies of data, in Mumbai, India, so the product stays fast.
Cloudflare
- What it does for us
- Runs our domain and sits in front of the website and servers, routing traffic and blocking attacks, so it sees your IP address and the pages you ask for. Its Web Analytics counts visits to pages without cookies and without storing anything on your device.
Render
- What it does for us
- Runs the servers behind the product, in the United States, where reports are made and connected tools are read.
Resend, with Gmail as a fallback
- What it does for us
- Sends sign in codes, receipts, support replies and other service emails.
Anthropic
- What it does for us
- Turns a validation request, a Founder OS answer or a support question into an answer with its Claude models. It is tried first for every AI request. Only the text a request needs is sent, and under Anthropic's commercial terms it is not used to train its models.
OpenRouter and the AI models behind it
- What it does for us
- Answer a request when Anthropic cannot, for example during an outage. Only the text a request needs is sent. Section 5 says what each kind of request allows the provider to keep.
Tavily
- What it does for us
- Runs the web searches a validation report makes before the AI model is asked. The idea's title, industry and location are sent, and sometimes a few single words from its description. Your name, email and account are not.
NewsAPI
- What it does for us
- Searched for recent news about an idea's market when a validation report is made. Words that describe the idea's industry and location are sent. Your name, email and account are not.
Hacker News Search (run by Algolia) and GitHub
- What it does for us
- Searched for stories and open source projects on an idea's subject when a validation report is made. A few single words that describe the idea are sent. Your name, email and account are not.
Voyage AI
- What it does for us
- Turns the text of documents you add to Founder OS into the numbers that let us search it by meaning. Only that text is sent.
Google Analytics
- What it does for us
- Shows us which pages and features are used. Runs only if you accept analytics cookies.
Google AdSense
- What it does for us
- Shows advertising on public pages. Runs only if you accept advertising cookies.
Google Fonts
- What it does for us
- Delivers the typefaces used on some pages, so your browser contacts Google when they load.
Logo.dev, Simple Icons and Unavatar
- What it does for us
- Supply the logos shown next to connected tools, so your browser contacts them when logos load.
StartupBase, Uneed, Findly.tools, Wired Business and PeerPush
- What it does for us
- Directories that list StartupDeckAI. Their "Featured on" badges on our public pages are images served by the directories, so your browser contacts them when the badges load. Nothing about your account is sent.
Sentry
- What it does for us
- Receives crash and error reports from the website and servers so we can fix faults. Email addresses, passwords, keys and the text of ideas and reports are removed before a report is sent.
We may change providers as the product grows, and we will keep this list current. Businesses doing procurement can ask for the current list and our security answers at support@startupdeck.in.
9. Where data is processed
StartupDeckAI is run from India. Our database is in Mumbai, India, and the servers that run the product are in the United States, so your data travels there whenever you use it. AI processing and analytics also happen in the United States, and other providers in section 8 may process data where they operate. When data crosses a border we rely on contracts and the security controls described in section 10. India's law allows transfers except to countries the government restricts, and we will follow any such restriction.
10. How we protect data
No service is perfectly secure, so we describe what we actually do rather than promise the impossible.
Accounts
- Passwords are never stored. We keep only a salted hash made with scrypt.
- Two step sign in is available, by email code or authenticator app, with backup codes that we store hashed.
- Sessions use cookies that scripts cannot read, that travel only over HTTPS in production, and that are not sent with cross site requests.
- Forms that change data are protected against forgery, and sign in and sensitive actions are rate limited.
- Sensitive changes, such as a new password, ask you to sign in again first.
Your workspace
- Every request is checked on the server against the account and company it belongs to. One customer cannot reach another's workspace, and hiding a button is never the only check.
- Access to Founder OS is decided on the server from your plan, not by the page you are looking at.
- Inside our team, only people whose role needs it can open the full text of an idea or report, to answer a support request, investigate a fault or stop abuse. Others see summaries. Staff opening an account is recorded in an audit log, and so is every export of its data.
- Keys for connected tools are encrypted before storage, and connections are read only as described in section 4.
Our systems
- All traffic uses HTTPS, with strict transport security and browser protections such as a content security policy.
- Payment webhooks are accepted only with a valid signature from the payment provider.
- Security events are logged, and secrets are kept out of logs.
- Every code change is scanned for accidentally committed keys before it is saved, and again in our automated checks.
- We review known vulnerabilities in the software we depend on and update it.
Reporting a problem
If you find a security problem, please tell us before you tell anyone else. Email support@startupdeck.in with the subject "[Security]". Our security.txt says the same. Describe the steps to reproduce it and do not include real customer data. We will not take action against people who report in good faith and do not harm others' data.
11. Keeping and deleting data
| Data | How long we keep it |
|---|---|
| Account details | While your account is open, then removed within the deletion period below. |
| Ideas, reports and Founder OS records | While your account is open, then removed within the deletion period below. |
| Keys and access tokens for connected tools | Until you disconnect the tool or delete your account. Disconnecting deletes them straight away. |
| Records imported from connected tools | Until you disconnect the tool or delete your account. Disconnecting deletes them straight away. |
| Invoices and payment references | For as long as tax and accounting law requires us to keep them. |
| Security and audit logs | For a limited period, to investigate abuse and incidents. |
| Backups | Held by our database provider and removed as they expire, which we aim to be within 90 days. |
Account details
- How long we keep it
- While your account is open, then removed within the deletion period below.
Ideas, reports and Founder OS records
- How long we keep it
- While your account is open, then removed within the deletion period below.
Keys and access tokens for connected tools
- How long we keep it
- Until you disconnect the tool or delete your account. Disconnecting deletes them straight away.
Records imported from connected tools
- How long we keep it
- Until you disconnect the tool or delete your account. Disconnecting deletes them straight away.
Invoices and payment references
- How long we keep it
- For as long as tax and accounting law requires us to keep them.
Security and audit logs
- How long we keep it
- For a limited period, to investigate abuse and incidents.
Backups
- How long we keep it
- Held by our database provider and removed as they expire, which we aim to be within 90 days.
Deleting your account
Email support@startupdeck.in from the address on your account. We will confirm it is you, then aim to remove your account and workspace content from our live systems within 30 days. We keep only what the law requires, such as invoices. Anything left in backups is removed as the backups expire.
Cancelling a plan
Cancelling stops future charges and keeps your access until the end of the period you paid for. It does not delete your data. See Refunds and cancellation.
12. Your rights
Depending on where you live, you can ask us to:
- Tell you what personal data we hold about you and give you a copy.
- Correct what is wrong. You can fix your name and sign in details yourself in Settings.
- Delete your data, as described in section 11.
- Stop using your data for a purpose you agreed to, by withdrawing consent. You can switch off optional emails in Settings and optional cookies through the banner.
- Limit or object to some uses, where the law gives you that right.
- Nominate someone to exercise your rights for you if you die or cannot act, as India's law allows.
To use a right, email support@startupdeck.in from your account address and say what you want. We will reply within the time the law sets. We do not charge for ordinary requests, and we will tell you if we cannot do something and why. You may also complain to your local data protection authority.
13. If something goes wrong
If we learn of a security incident that affects your personal data, we will investigate, contain it, and tell the people and authorities the law requires us to tell. We aim to do that without unnecessary delay, and to say what happened, what data was involved and what you can do.
14. Children
StartupDeckAI is for people aged 18 and over. We do not knowingly collect personal data from anyone younger. If you think a child has given us data, email us and we will delete it.
15. Changes to this policy
When we change this policy we update the date at the top. If a change matters to you, for example a new use of your data, we will email you or show a notice in the product before it takes effect. Older versions are available on request.
16. Complaints and the Grievance Officer
If you are unhappy with how we handled your data or a request, write to our Grievance Officer first.
Grievance Officer, StartupDeckAI
Yash Suthar. Email support@startupdeck.in with the subject "Grievance". Mumbai, Maharashtra, India.
We acknowledge a complaint within 24 hours and aim to resolve it within 15 days. If it needs longer, we will tell you why and when to expect an answer.
If we do not resolve it, you can complain to the Data Protection Board of India or to the authority where you live.
17. Contact
Questions about this policy or your data: support@startupdeck.in. We usually reply within one business day. You can also use the contact page.
Read next
- Terms of Service The rules for accounts, plans and connected tools.
- Documentation How connections work and what each tool is read for.
- Copyright and trademarks Who owns what, and how to send a takedown notice.
- Refunds and cancellation How to cancel and when you can get money back.
- Help and support Get a person to look at your account or bill.
- Contact us Questions about these documents or your data.