| Document | Privacy Policy (Privacy Notice) |
| Version | v0.4 (draft; website forms, AI calls and consent records added) |
| Effective date | 25 October 2026 |
| Last updated | 31 October 2026 |
| Data Fiduciary | SALESSHURU SOFTWARE SOLUTIONS (OPC) PRIVATE LIMITED, CIN U62099ME2026OPC474283 |
| Registered office | DL/229 Etape Layout, Sundarkhed Prabhankur, Buldana, Buldhana - 443001, Maharashtra, India |
| Grievance Officer / privacy contact | Mayuri Deshmukh, Director · grievance@salesshuru.com · +91 7775917507 |
1. Summary
- Who we are: SALESSHURU SOFTWARE SOLUTIONS (OPC) PRIVATE LIMITED ("SalesShuru", "we", "us", "our") runs GrowthOS and https://www.salesshuru.com/. For the personal data described here, we are the Data Fiduciary under the Digital Personal Data Protection Act, 2023 ("DPDP Act").
- What we collect: the data you give us (name, email, mobile number, account and workspace content, billing details), recordings and transcripts of calls you ask our AI assistant to make to you, a record of what you consented to, data generated when you use the Service (usage, device and log data), and limited data from our service providers (for example, payment status from Razorpay).
- Why: to run the Founding List, the AgentOS waitlist and GrowthOS, answer your enquiries, place the demo calls you request, generate AI-assisted plans for you, process payments, keep the Service secure, meet legal obligations, and (only with your separate consent) send the Builder Brief and product news.
- Stop anytime: unsubscribe from any marketing email in one click, or stop emails and calls at Privacy choices.
- We do not sell your personal data. We do not store your card details. SalesShuru does not use your Customer Content to train or fine-tune AI models.
- Your rights: access, correction, completion, updating, erasure, withdrawal of consent, grievance redressal and nomination. Write to grievance@salesshuru.com.
- Complaints: contact our Grievance Officer first; you may then complain to the Data Protection Board of India.
Capitalised terms not defined here (such as Service, Account, Customer Content, AI Features, Founding List, Builder Brief and Payment Processor) have the meanings given in the Terms of Service.
2. Scope and legal framework
2.1 This Privacy Policy applies to personal data we process about individuals ("you", the Data Principal) who visit our website, join the Founding List, subscribe to the Builder Brief, use GrowthOS, pay for a Paid Plan, or contact us.
2.2 We process personal data in accordance with Indian law, including:
- the Information Technology Act, 2000 and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 ("SPDI Rules"), which continue to apply until the relevant provisions of the DPDP Act commence;
- the DPDP Act and the Digital Personal Data Protection Rules, 2025 ("DPDP Rules"), notified on 13 November 2025 and coming into force in phases: provisions on the Data Protection Board took effect on 13 November 2025; Consent Manager provisions take effect on 13 November 2026; and most obligations of Data Fiduciaries (notice, consent, rights, security, breach intimation, children's data) take effect on 13 May 2027;
- the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 (as amended), to the extent GrowthOS acts as an intermediary for content you store in it;
- the CERT-In Directions of 28 April 2022 under section 70B of the IT Act; and
- the Consumer Protection Act, 2019 and Consumer Protection (E-Commerce) Rules, 2020, where applicable.
2.3 We are applying the DPDP standard now. Although many DPDP obligations commence only on 13 May 2027, we have written this notice to meet those standards from launch so that you get the same protections throughout.
2.4 Customer Content about other people. If a Customer uploads personal data of others into a Workspace (for example, names of team members or end-users in a PRD), we process that data on the Customer's behalf and according to its instructions, and the Customer is responsible for having a lawful basis and giving any required notice. Our Data Processing Agreement (coming soon) for business Customers sets out how we act as Data Processor for that data.
3. Personal data we process and why (itemised notice)
The table below lists each category of personal data, the specific purpose for which we use it, and the legal ground we rely on. "Consent" means consent under section 6 of the DPDP Act; "Legitimate use" means a use permitted under section 7 of the DPDP Act (see Section 5).
| # | Personal data | Source | Specific purpose(s) | Legal ground | Is it required? |
|---|---|---|---|---|---|
| 1 | Founding List details: name, email address, and optional details you choose to give (e.g., role, company name, team size, what you are building) | You (sign-up form) | Reserve your place, contact you about onboarding and invitation to GrowthOS, prioritise invitations, send service updates about the launch | Consent (given at sign-up) | Email is required to join; other fields optional |
| 2 | Account details: name, email address, password (stored in hashed form, never in plain text) or a sign-in identifier if you sign in with Google or your organisation's single sign-on (SSO), two-factor authentication settings if you turn them on, profile photo (optional), time zone, language | You / sign-in provider | Create and secure your Account, authenticate you, provide the Service | Consent; legitimate use (s.7(a), data voluntarily provided for a specified purpose) | Yes, to use the Service |
| 3 | Workspace and Customer Content: ideas, PRDs, backlogs, user stories, sprint plans, comments, files, and names/emails of Authorised Users you invite | You and your Authorised Users | Store, display and sync your content; collaboration; enable invitations to your team | Consent; legitimate use (s.7(a)) | Yes, to use the Service |
| 4 | AI Inputs and Outputs: prompts and content you submit to AI Features, and generated Output | You / generated by AI Features | Generate PRDs, plans and suggestions you request; abuse and safety monitoring; troubleshooting | Consent | Only if you use AI Features |
| 5 | Billing and transaction details: billing name, email, billing address, phone number (if required by the Payment Processor), plan, amount, transaction ID, payment status, last 4 digits/type of card or UPI handle as shared by the Payment Processor, e-mandate/subscription reference. Payments are accepted only by card or UPI AutoPay, in INR. We do not collect or store full card numbers, CVV or UPI PIN; these are entered directly with Razorpay | You / Razorpay | Process payments and recurring billing, issue receipts, handle refunds and chargebacks, prevent fraud, maintain accounting and tax records | Consent (contract you request); legitimate use (s.7(a)); compliance with law (s.7(b)–(d)) | Yes, for Paid Plans |
| 6 | Usage data: pages and features used, clicks, timestamps, session information, feature settings | Automatically, via the Service | Operate and improve the Service, understand which features are used, fix bugs | Legitimate use (s.7(a)) for strictly necessary processing; Consent for any non-essential identifiers (see Cookie Policy) | Strictly necessary data: yes; non-essential identifiers: optional |
| 7 | Device and log data: IP address, browser type, operating system, device identifiers, referral URL, error logs, security and access logs | Automatically | Security, fraud and abuse prevention, debugging, compliance with CERT-In log-retention directions and DPDP Rules log requirements | Legitimate use (compliance with law, s.7); Consent | Yes |
| 8 | Cookies and similar technologies | Automatically | See Cookie Policy | Essential: legitimate use; non-essential: Consent | Essential only |
| 12 | Website visit data: page path, referring page, campaign source (UTM source) and a first-party visitor identifier, sent to our own server at api.salesshuru.com/events | Automatically, on www.salesshuru.com | Understand which pages and campaigns bring visitors | No consent needed: the identifier is session-only, held in sessionStorage or in memory, never linked to your name or email and never shared (see Section 3.1 and the Cookie Policy) | Collected automatically while you browse; it expires when your tab or session closes |
| 13 | Website enquiries and bookings: name, email, mobile number, company, topic, message and the other details you type into a website form (contact, demo booking, Founding List, AgentOS waitlist) or the meeting-booking widget, and the time you book. We also keep the page you were on and the campaign that brought you (UTM source, medium and campaign; never the full link) | You | Reply to your enquiry, contact you about the demo you booked by email, phone or WhatsApp, send you an email confirmation, and hold the meeting you booked | Consent (the required box on each form) | Only if you submit a form or book a meeting |
| 14 | AI demo calls you request ("Call me now"): name, mobile number, email, the call language and industry you choose, the call recording, the transcript, and the outcome (for example, a meeting booked) | You; generated during the call | Place one demo call from our AI assistant to the number you give, run the conversation, book a follow-up if you ask, and keep a record of the call | Consent (a separate box that also confirms the number is yours and that the call is recorded) | Only if you ask for a call |
| 15 | Consent records: which box you ticked, its exact wording, the version of this notice, the date and time, the page, your IP address and browser type; and any withdrawal or opt-out | Automatically, when you submit a form, unsubscribe or use Privacy choices | Prove what you agreed to and when (section 6(10) of the DPDP Act), and make sure we never contact you after you opt out | Compliance with law (s.7); legitimate use | Yes, whenever you give or withdraw consent |
| 9 | Builder Brief and product news: email address, name (optional), subscription preferences, open/click data (if enabled) | You | Send the Builder Brief newsletter, short follow-up emails about our products, and measure engagement | Consent (a separate, unticked box on our forms; not a condition of anything else) | No, optional |
| 10 | Support and communications: your messages, emails, feedback, survey responses, grievance records | You | Respond to queries, resolve grievances, improve the Service, keep records of complaints | Consent; legitimate use; compliance with law | Only if you contact us |
| 11 | Service and transactional emails: email address | You | Send essential notices (security alerts, billing notices, pre-debit and renewal reminders, changes to Terms) | Legitimate use (s.7(a)); compliance with law | Yes, while you have an Account |
3.1 Website visitors: what runs on www.salesshuru.com
| Tool | What it does | Personal data | Consent |
|---|---|---|---|
| Plausible Analytics | Counts page views and traffic sources | None. Plausible is cookieless, privacy-friendly analytics. It does not set cookies, does not collect personal data and does not track you across sites | Not needed. It is cookieless and aggregate, and runs without a consent prompt |
First-visit record (localStorage key ss_visitor) |
Remembers when you first visited and the campaign tags in that first link (UTM tags and any Google or Meta ad click ID) | Stays in your browser. Only the UTM source, medium and campaign are sent to us, and only when you submit a form; the ad click IDs are added only to sign-up links to our GrowthOS app | Not needed for India; clear it anytime by clearing site data |
| First-party events (api.salesshuru.com/events) | Records the page path, referring page, UTM source and a session-only visitor identifier | The identifier is held in sessionStorage or in memory (no cookie, no localStorage) and expires when your browser tab or session closes. It is sent only to our own /events endpoint, never attached to sign-up or lead data, never linked to your name or email, and never shared with third parties | Not needed |
| Cloudflare Turnstile (when enabled on a form) | Checks that a form is being submitted by a person, not a bot | Browser and device signals and IP address, processed by Cloudflare | Not needed: strictly necessary for security |
| Cal.id booking widget | Lets you book a meeting with us | The details you enter in the widget | Only when you use the widget |
| Amazon SES | Sends us your website enquiry and sends you any email confirmation | Name, email and your message | Only when you submit a form |
| OutboundOS, our own AI calling system, with Plivo (telephone calls), Sarvam AI (speech recognition and voice) and Anthropic (the language model that runs the conversation and summarises it) | Places the demo call you ask for | Name, mobile number, email, call language and industry; the audio of the call and its transcript | Only when you tick the call box and ask for a call |
AI demo calls. When you ask for a call, our AI assistant calls the number you gave, only between 9 AM and 9 PM IST (later requests are called the next morning). It says at the start that it is an AI assistant and that the call is recorded. Say "stop calling me" at any time and it ends the call and adds your number to our do-not-call list; you can also stop calls at Privacy choices. If an unanswered call needs a retry, we try at most three times in total. We accept at most two call requests a day for any one number.
We do not use YouTube embeds today. If we add one, it will use YouTube's privacy-enhanced (youtube-nocookie.com) mode and load only when you click to play. We do not use the Meta Pixel, the LinkedIn Insight Tag, website visitor identification services or contact-enrichment services. If we ever add any of these, we will update this Policy and the Cookie Policy first and use them only with your consent.
What we do not intend to collect: government ID numbers, biometric data, health data, financial account credentials, or information about children. Please do not upload such data into the Service.
4. Consent
4.1 How we ask. Where we rely on consent, we ask for it through a clear affirmative action (an unticked checkbox) presented with a short-form notice linking to this notice. Consent requests are in clear and plain language, are specific to the purposes listed, and are not bundled. On our website forms:
- each form has one required box for that form's purpose (for example, "I'm 18 or older and agree to emails about my Founding 1000 seat"), which also confirms you are 18 or older;
- the call form's box also confirms the number is yours and that the call is recorded;
- marketing email (the Builder Brief and product news) is always a separate, optional, unticked box. Leaving it unticked never stops you from using the form.
We keep a record of each box you tick, as described in row 15 of Section 3. Our website analytics (Plausible) is cookieless and aggregate and runs without a consent prompt.
4.2 Withdrawing consent is as easy as giving it. You can withdraw consent at any time, using a method as easy as the one you used to give it:
| Consent | How to withdraw |
|---|---|
| Founding List or AgentOS waitlist | Reply "leave" to any email about it, or email admin@salesshuru.com |
| Builder Brief and product news | The one-click "Unsubscribe" link in every email, or Privacy choices |
| AI calls and phone contact | Say "stop calling me" during a call, or enter your number at Privacy choices. This stops all calls to that number, including requests made from our website |
| AI Features / Account processing | Stop using the feature, delete specific content, or ask us to delete your Account (see Section 8.2) |
| Any other consent | Email grievance@salesshuru.com |
4.3 Effect of withdrawal. Withdrawal does not affect processing done before it. After you withdraw, we (and our processors) will stop processing the relevant personal data within a reasonable time unless processing is required or permitted by law. If you withdraw consent needed to provide the Service (for example, account data), we may not be able to continue providing the Service and will tell you the consequences.
4.4 Consent Managers. The DPDP Act allows you to give, manage, review and withdraw consent through a Consent Manager registered with the Data Protection Board of India. Registration of Consent Managers begins under the DPDP Rules from 13 November 2026. We do not currently integrate with a Consent Manager. If we do, we will list it here, and consents given through it will be honoured as if given to us directly.
5. Legitimate uses (processing without consent)
The DPDP Act (section 7) permits processing without consent for certain legitimate uses. We rely on these only where they apply, mainly:
- Voluntarily provided data for a specified purpose (s.7(a)): for example, when you give us your email and payment details to buy a Paid Plan and have not indicated that you do not consent, we use them to complete that transaction.
- Compliance with law (s.7(b)–(d)): processing needed to meet legal obligations, such as tax and accounting records, CERT-In incident reporting and log retention, responding to lawful requests from courts or government agencies, and intermediary obligations under the IT Rules.
- Medical emergency, disaster or public order (s.7(f)–(h)): in the rare event that processing is needed to respond to a threat to life or health or during a disaster or breakdown of public order.
6. Who we share personal data with
6.1 We do not sell or rent your personal data. We share it only as follows:
| Recipient | What | Why |
|---|---|---|
| Razorpay (Payment Processor) | Name, email, phone, amount, plan, transaction and mandate data | Collect payments, manage e-mandates and refunds. Razorpay processes card and bank data under its own PCI-DSS and RBI obligations and its own privacy policy |
| Amazon Web Services (AWS), our hosting and cloud infrastructure provider. We use AWS in the Asia Pacific (Mumbai) region | All Service data | Host and run the Service |
| Amazon Simple Email Service (Amazon SES), part of AWS | Email address, name, message content | Send transactional emails and deliver website enquiries to us |
| Anthropic (Claude API) | AI Inputs and relevant Customer Content, Outputs | Generate Output you request in GrowthOS. Under its commercial terms, Anthropic does not use API Inputs or Outputs to train its models, and keeps them for a limited period (currently up to 30 days) unless a request is flagged for a usage-policy review or the law requires longer |
| Amazon SES (part of AWS), for our own emails | Email address, name, preferences | Send Founding List emails, product news and the Builder Brief. If we start using a separate newsletter tool, we will list it here before it receives any data |
| Plausible Analytics | No personal data (cookieless, aggregate page statistics) | Count website visits and traffic sources |
| Cloudflare (Turnstile), where enabled on a form | Browser and device signals, IP address | Protect forms from bots and abuse |
| Cal.id | Details you enter when booking a meeting | Schedule meetings you book |
| Plivo (telephony) | Your mobile number and the call audio | Place and connect the AI demo call you request |
| Sarvam AI (speech recognition and text-to-speech) | Call audio | Understand what you say on the call and speak the assistant's replies |
| Anthropic (AI model) | Call transcript, your name and the details you gave on the form | Run the conversation and summarise the call. Under its business terms, Anthropic does not train its models on this data |
| Google, only if you choose Google sign-in | Your Google account name, email and identifier | Sign you in |
| Sentry (error monitoring), when enabled | Error details and the account identifier of the User who hit the error; text on screen is masked | Find and fix errors in GrowthOS |
| Tools you connect yourself: Linear, Jira, GitLab, or your organisation's single sign-on provider | The data you choose to sync, and your sign-in identifier | Only if you or your Workspace admin connect them |
| Other members of your Workspace | Your name, email, profile and content you share in that Workspace | Collaboration you choose |
| Government agencies, courts, CERT-In, Data Protection Board | As legally required | Comply with law, lawful orders and reporting obligations |
| A buyer or successor entity | Relevant data | Merger, acquisition or restructuring, subject to this Policy |
| Professional advisers (lawyers, auditors, chartered accountants) | As needed | Legal, audit and tax compliance, under confidentiality |
6.2 Our service providers act as Data Processors on our behalf under written contracts that require them to process data only on our instructions and to protect it. Our current sub-processors are listed in the Sub-processor List (coming soon), which we keep up to date.
7. Cross-border transfer
7.1 GrowthOS is currently offered only to customers in India, and payments are in INR. Razorpay is an Indian payment aggregator regulated by the Reserve Bank of India (RBI). Payment data is handled under Razorpay's terms and the RBI's data-localisation rules for payment system data. We use Amazon Web Services in the Asia Pacific (Mumbai) region to host the Service and our website forms. For AI demo calls, Anthropic processes call transcripts in the United States, and Plivo may route call data outside India. AI Features in GrowthOS use Anthropic's Claude API, which processes AI Inputs and Outputs in the United States. Only the content you send to an AI Feature leaves India, for that request; your stored data stays in Mumbai. Some of our other service providers may also store or process personal data outside India.
7.2 Under section 16 of the DPDP Act, personal data may be transferred outside India except to countries or territories that the Central Government restricts by notification, and subject to any requirements set by the DPDP Rules. We will not transfer personal data to any restricted country and will comply with any conditions the Government specifies. We require recipients to protect personal data to a standard consistent with this Policy.
8. Retention
8.1 We keep personal data only as long as needed for the purposes in Section 3, or as required by law, and then erase it (or anonymise it so it no longer identifies you).
| Data | Retention period |
|---|---|
| Founding List and AgentOS waitlist details | Until you join GrowthOS (then treated as Account data) or withdraw; otherwise deleted automatically 18 months after you sign up |
| Website enquiries, demo bookings and call requests | Deleted automatically 12 months after your latest request |
| AI call recordings | 90 days, then deleted automatically |
| AI call transcripts and call notes | Kept with your enquiry record and deleted with it (12 months) |
| Consent records and opt-outs | For as long as we rely on the consent, and 3 years after it ends or you withdraw, so we can prove it. An opt-out (your email or number on our do-not-contact list) is kept so we never contact you again |
| Website visit statistics | About 13 months, then deleted automatically |
| Account data and Customer Content | For as long as your Account is active; deleted by our team within 30 days of your deletion or erasure request (see Section 8.2) |
| Backups (where kept) | Removed on a rolling 35-day cycle |
| Billing and transaction records | 8 years (as required by tax, company and accounting laws) |
| Security, access and processing logs | 1 year. The law requires at least 1 year under the DPDP Rules (once in force) and 180 days within India under the CERT-In Directions |
| Builder Brief data | Until you unsubscribe, plus a suppression record (email only) so we do not email you again |
| Support and grievance records | 3 years after closure of the request |
8.2 How deletion works today. Deletion and erasure requests are currently handled manually by our team. To ask for deletion, email grievance@salesshuru.com or use the in-app deletion request. We will confirm your identity, delete the data within 30 days of your request, and email you when it is done. We may keep data we are required by law to keep (for example, billing records), and copies in backups are removed as backups expire.
8.3 Before erasing data because a purpose is no longer served (for example, after long inactivity), we will, where practical, notify you in advance so you can log in or export your data.
9. Children's data
9.1 GrowthOS is a business tool not directed at children. Under the DPDP Act a "child" is anyone under 18. You must be 18 or older to use the Service, join the Founding List or subscribe to the Builder Brief.
9.2 We do not knowingly process children's personal data, track or behaviourally monitor children, or target advertising at them. If we learn that we have collected a child's personal data without verifiable consent of a parent or lawful guardian as required by section 9 of the DPDP Act and the DPDP Rules, we will delete it promptly. If you believe a child has given us data, contact grievance@salesshuru.com.
9.3 The same applies to persons with disability who have a lawful guardian: we do not knowingly process their data without verifiable consent of the lawful guardian.
10. Your rights as a Data Principal
You have the following rights. To exercise any of them, email grievance@salesshuru.com (or use an in-app request where available) and identify yourself using the email address or other identifier linked to your Account. We may need to verify your identity before acting.
| Right | What it means |
|---|---|
| Access / summary (s.11) | Get a summary of the personal data we process about you and the processing activities, the identities of Data Fiduciaries and Data Processors with whom we have shared it (and a description of the data shared), and other information as prescribed |
| Correction (s.12) | Correct inaccurate or misleading personal data |
| Completion (s.12) | Complete incomplete personal data |
| Updating (s.12) | Update your personal data |
| Erasure (s.12) | Ask us to erase personal data that is no longer needed for the purpose, unless we must keep it to comply with law. Erasure is handled manually by our team within 30 days (see Section 8.2) |
| Withdraw consent (s.6) | See Section 4.2 |
| Grievance redressal (s.13) | Have a readily available means of grievance redressal; see Section 13 |
| Nomination (s.14) | Nominate another individual to exercise your rights if you die or become incapable. Email us with the nominee's name and contact details, and we will confirm the next steps by email |
Response time. We aim to respond to rights requests within 30 days, and in any case within the period prescribed by law (the DPDP Rules require grievances to be responded to within a period not exceeding 90 days).
Your duties (s.15). When exercising your rights you must comply with applicable law, not impersonate anyone, not suppress material information, not register false or frivolous grievances, and give only verifiably authentic information when requesting correction or erasure. Breach of these duties may attract a penalty under the DPDP Act.
11. Security safeguards
We take reasonable security measures appropriate to the risk, consistent with the SPDI Rules and DPDP Rules. We use industry-standard safeguards, including encryption in transit. Other measures include:
- passwords stored in hashed form, and optional two-factor authentication for your Account;
- access to personal data limited to people who need it to run the Service;
- contractual security obligations on our Data Processors;
- payment card data handled only by Razorpay (we never see or store full card details).
We are an early-stage company and do not currently hold security certifications.
No system is completely secure. Please use a strong, unique password and tell us immediately if you suspect unauthorised access to your Account. More detail is in our Security Overview (coming soon).
12. Personal data breach notification
If a personal data breach occurs, we will:
- inform affected Data Principals without delay, in plain language, describing the nature, extent, timing and likely consequences of the breach, the steps we have taken and you can take to reduce risk, and a contact for questions;
- intimate the Data Protection Board of India without delay, and provide a detailed report within 72 hours of becoming aware of the breach (or such longer period as the Board allows), as required by the DPDP Rules once in force; and
- report cyber security incidents to CERT-In within 6 hours of noticing them, where required by the CERT-In Directions, 2022.
13. Grievance Officer and complaints
13.1 Grievance Officer (appointed under the SPDI Rules, 2011, the IT (Intermediary Guidelines) Rules, 2021 and the Consumer Protection (E-Commerce) Rules, 2020, and acting as the person able to answer questions about processing under section 8(9) of the DPDP Act):
Mayuri Deshmukh, Director SALESSHURU SOFTWARE SOLUTIONS (OPC) PRIVATE LIMITED DL/229 Etape Layout, Sundarkhed Prabhankur, Buldana, Buldhana - 443001, Maharashtra, India Email: grievance@salesshuru.com Phone: +91 7775917507 Working hours: 10:00 AM to 6:00 PM IST, Monday to Saturday (excluding public holidays)
13.2 Timelines. We will acknowledge your grievance within 24 hours and resolve it as follows:
| Type of grievance | Resolution timeline |
|---|---|
| Complaints about content hosted on the Service or violations of the IT Rules (Rule 3(2), IT Rules 2021 as amended w.e.f. 20 February 2026) | Within 7 days of receipt; requests to remove certain categories of content within 36 hours; complaints about content exposing private areas, nudity, sexual acts or impersonation (including morphed images) within 2 hours |
| Privacy, personal data and data-principal rights grievances | Within 30 days of receipt (within the one-month period under the SPDI Rules and well within the maximum of 90 days under the DPDP Rules) |
| Consumer complaints (billing, refunds, service) | Within 30 days of receipt (Consumer Protection (E-Commerce) Rules, 2020 require acknowledgement within 48 hours and redressal within one month) |
More details are in Contact and Grievance Redressal.
13.3 Data Protection Board of India. If you are not satisfied with our response, or we do not respond within the timelines above, you may complain to the Data Protection Board of India under the DPDP Act (you must first exhaust our grievance redressal process, as required by section 13(3)). You can do this through the Data Protection Board of India's official website or app, once available.
13.4 Data Protection Officer. SalesShuru has not been notified as a Significant Data Fiduciary. A Data Protection Officer based in India, independent audits and data protection impact assessments are mandatory only for Significant Data Fiduciaries notified by the Central Government under section 10 of the DPDP Act. If we are notified, we will appoint a DPO and publish their contact details here.
14. Builder Brief and marketing communications
We send the Builder Brief newsletter and other marketing emails only if you opt in separately. Each email contains an unsubscribe link, and unsubscribing does not affect your Account or transactional emails. Details are in our Builder Brief and Marketing Email Consent and Unsubscribe Terms (coming soon).
15. Cookies
We use essential cookies and similar technologies to run the Service and keep it secure. Our website analytics (Plausible) is cookieless and aggregate, and runs without a consent prompt. Our first-party visitor identifier is session-only and not linked to you, and a small first-visit record in your browser remembers which campaign brought you (see Section 3.1). We do not use advertising or marketing pixels or tracking cookies, so we do not show a cookie banner. See our Cookie Policy.
16. Language of this notice
This notice is available in English. In line with the DPDP Act, which gives you the option to access a consent notice in English or any language specified in the Eighth Schedule to the Constitution of India, you may ask for this notice in another Eighth Schedule language. To request this, email admin@salesshuru.com.
17. Changes to this Policy
We may update this Policy. We will post the updated version with a new "Last updated" date and, for material changes (especially new purposes requiring consent), notify you by email or in-app and ask for fresh consent where required.
18. Contact
General queries: admin@salesshuru.com Privacy queries and rights requests: grievance@salesshuru.com Post: SALESSHURU SOFTWARE SOLUTIONS (OPC) PRIVATE LIMITED, DL/229 Etape Layout, Sundarkhed Prabhankur, Buldana, Buldhana - 443001, Maharashtra, India
GrowthOS is a product of SALESSHURU SOFTWARE SOLUTIONS (OPC) PRIVATE LIMITED (CIN U62099ME2026OPC474283). Privacy Policy v0.4 draft, last updated 31 October 2026.