Privacy Policy

1. Information We Collect

We collect information you provide directly to us, such as when you create an account, make a purchase, subscribe to our newsletter, or contact us for support. This may include your name, email address, phone number, company information, and payment details.

We also automatically collect certain information about your device and usage of our services, including your IP address, browser type, operating system, and pages visited.

2. How We Use Your Information

We use the information we collect to:

• Provide, maintain, and improve our services
• Process transactions and send related information
• Send technical notices, updates, and support messages
• Respond to your comments and questions
• Communicate with you about products, services, and events
• Analyze usage patterns and trends

3. Parties We Share Your Information With

We do not sell, trade, or rent your personal information. We share it only with the following categories of recipient, only to the extent each one needs it, and only under a written contract that requires them to protect it and to use it solely on our instructions:

Payments are processed by Stripe, who act as an independent controller of the payment data you submit. Your full card number, expiry and security code are entered directly into the processor's secure fields and are never received or stored on our servers. We retain only the transaction reference, the amount, the currency, the payment status and the last four digits and brand of the card, so that we can issue receipts, provide support and handle refunds and disputes.

• Payment processors (Stripe) — to take payment, issue receipts and handle refunds and disputes.
• Cloud hosting and infrastructure providers (Microsoft Azure and our website hosting provider) — to run our websites, databases and backups.
• AI and model providers (such as Azure OpenAI and OpenAI) — to process the prompts you send to Dewiride AI and return a response.
• Speech providers (Microsoft Azure AI Speech) — to turn what you say into text when you speak to the assistant, and to turn its reply into a voice.
• Push notification delivery (Google Firebase Cloud Messaging) — to deliver notifications to the Dewiride AI mobile app on your device.
• The WhatsApp Business Platform (Meta Platforms) — to connect a business's own WhatsApp number to Dewiride AI, receive the messages its customers send to it and send the business's replies, as section 11 describes.
• Chat apps you link to your account (Microsoft Teams, from Microsoft; WhatsApp, from Meta Platforms) — to deliver your conversations with the assistant, and anything it asks you to approve, to the chat you linked. Each app keeps what it delivers under its own terms.
• Email, forms and communication providers (Microsoft 365) — to send transactional email and receive enquiries.
• Analytics providers (Google Analytics) — to understand aggregate website usage, and only where you have consented to analytics cookies.
• Professional advisers (accountants, auditors and lawyers) — where needed for tax, audit or legal purposes.
• Government authorities, regulators, courts and law enforcement — where we are legally required to disclose, or where disclosure is necessary to establish, exercise or defend legal claims or to protect the rights, safety or property of any person.
• An acquirer or successor entity — if we are ever involved in a merger, acquisition or sale of assets. We would notify you before your information became subject to a different privacy policy.

Two things can leave our systems for someone not listed above, and only when the assistant looks something up online for you. When it searches the web, the words it searches for are sent to Microsoft's Bing search service so that it can find pages to read. When it opens a link to read the file behind it — a link you gave it, one in an account you connected, or one it found while searching — our servers ask the website the link points to for the file. That website receives the link and our servers' network address, never yours, and nothing else from your conversation. The file is read on our own systems, and what it says becomes part of that conversation, kept and deleted with it as section 17 describes. You can switch both off in a chat, for an agent, or for everything you start.

4. How and When We Disclose Information

Disclosure to the parties listed above happens in these ways only:

Every processor is bound by a written data processing agreement, is prohibited from using your data for its own purposes, and must delete or return it when our contract ends. We do not disclose your personal information for advertising or for sale to data brokers under any circumstances.

• Automated, encrypted transmission — data passes to service providers over authenticated API calls encrypted in transit with TLS 1.2 or higher. This is the method used for payments, hosting, AI processing, transactional email and analytics.
• Access by authorised personnel — a small number of our staff and contractors can access your data through access-controlled administrative tools, only where needed to deliver or support the service.
• On your instruction — for example when you connect a third-party account to Dewiride AI or ask us to share information with someone.
• Formal written disclosure — to advisers, authorities or courts, in response to a valid legal request. We review every request, limit what we disclose to what is legally required, and tell you unless we are prohibited from doing so.

5. Security Practices

We maintain technical and organisational measures designed to protect your personal information against unauthorised access, alteration, disclosure or destruction. These include:

No method of transmission or storage is completely secure, so we cannot guarantee absolute security. If you believe your account has been compromised, contact us at support@dewiride.com immediately.

• Encryption in transit — every page and API call is served over HTTPS using TLS 1.2 or higher.
• Encryption at rest — databases, file storage and backups are encrypted on disk, and Dewiride AI conversations are encrypted in storage.
• Card data isolation — full card details are captured by our PCI-DSS compliant payment processor and never traverse or rest on our systems.
• Access control — role-based, least-privilege access, multi-factor authentication on all administrative and cloud accounts, and secrets held in a managed key vault rather than in code.
• Network and platform hardening — managed cloud infrastructure with vendor security patching, firewalling and activity logging.
• Monitoring, logging and backups — access and system logs are retained for review, and backups are taken regularly and tested.
• People and process — confidentiality obligations for staff and contractors, periodic access reviews, and vendor due diligence before we share data with a new processor.
• Incident response — we investigate suspected breaches immediately and, where a breach is likely to affect you, notify you and the relevant authority without undue delay and in line with applicable law.

6. Support Conversations

When you ask us for help — from the Help Center inside Dewiride AI, or from the contact form on this website — we open a support conversation and keep it until it is deleted under section 17. It is read and answered by people. Nothing you write to support is answered automatically.

• What we hold: your name and email address, the subject you gave, every message on the conversation, any files you attach, and the rating and comment you leave afterwards.
• What the app tells us about your session: the build you were running, the language and time zone you were using, your window size, the page you were on, and your browser's user-agent string. The Help Center shows you exactly what is attached before you send it. The contact form collects none of this beyond your browser's user-agent string.
• How it is protected: message bodies, our internal notes, attached file names and the session details above are encrypted in our database. The subject line and your email address are not, so that the support queue can be searched and sorted.
• Who can read it: our support team, while they are handling your conversation. It is not shown to other customers and it is not shared outside the recipients listed in section 3.
• Where AI is involved: our support team can ask an AI assistant to summarise a conversation or draft a reply, which sends the messages on that conversation to the model provider named in section 3. A draft is only ever a suggestion — a person edits it and sends it. Our internal notes are never sent, and nothing reaches you without a person choosing to send it.

If you start a conversation without an account, we email you a private link to it. That link expires, is reissued each time we reply, and stops working once the conversation is closed. Treat it like a password: anyone holding it can read and reply to that conversation.

7. Speaking to the Assistant

You can talk to Dewiride AI instead of typing, in the browser or in the mobile app. Your microphone is only ever opened when you start a spoken conversation, and it is released the moment you end one.

• What leaves your device: while a spoken conversation is open, the audio from your microphone is streamed to us over an encrypted connection and passed to the speech provider named in section 3, which turns it into text. The assistant's reply is turned back into a voice the same way.
• What we keep: the text. The words you spoke and the assistant's answer are saved as an ordinary conversation, encrypted in our database and deleted with it on the timetable in section 17. We do not record, store or replay the audio itself, and neither the recording nor a voiceprint is retained by us once the text exists.
• Silence is not sent as speech: your side of the conversation is only transcribed while you are speaking. The rest of the time the stream carries nothing that could be turned into words.
• You are in control of when: nothing is captured unless you have granted the microphone permission and opened a spoken conversation, and both the browser and the phone show that the microphone is open the whole time it is.

8. The Dewiride AI Mobile App

The mobile app signs into the same account and shows the same conversations as the website. A few things are true of it that are not true of a browser, and this section covers each.

• Notifications: to send one, we hold an identifier your device's copy of the app is issued by Google Firebase Cloud Messaging, together with the word "android". We store that identifier encrypted, use it for nothing but delivering your own notifications, and delete it when you sign out, when you turn notifications off, when your device stops accepting them, or with your account.
• What a notification contains: what we send to your phone is the kind of event and the names involved — an agent's name, a reminder's title, the name of a WhatsApp number or account your business connected (or the business's own phone number, when Meta has not approved a name to show for it) — never the text of a message and never a link that would let the holder approve anything. Your phone writes the sentence itself, in your language, and shows it under your lock screen's rules. One kind of notification is written by the app alone, without anything being sent: when you ask the assistant something from the phone — or open a conversation that is still being answered — and leave before the answer arrives, the answer can appear as a message you can reply to. Its text comes from the reply the app already holds; it is kept in memory only, marked private so a lock screen set to hide sensitive content shows only that the assistant replied until you unlock, and cleared when you open the conversation, mark it read or sign out. You can switch this off in the app's notification settings. Approving something always happens inside the app, behind your sign-in.
• In a car: if your phone is connected to a car through Android Auto, that reply can be read aloud by the car and answered by speaking, so anyone in the car can hear it. Your spoken answer is turned into text by Google's assistant in Android Auto, under Google's own privacy terms — not by us, and not by the speech provider in section 7. What reaches us is the written message it produces, sent the same way as one you typed. The car is shown nothing else — no reminders, results or approvals — and nothing can be approved from it. The same switch in the app's notification settings turns this off.
• Your fingerprint or face: if you lock the app to biometrics, the check is performed by Android and the result is all the app ever sees. Your fingerprint and face never leave your device and are never sent to us.
• Customer chats on the phone: a business's customer chats are shown in the app, never stored on the phone. A file a customer sent is copied into the app's own cache only so another app on the phone can show it; copies fetched more than a week ago are cleared the next time a file is opened, and all of them when you sign out.
• What the app does not do: it carries no advertising identifier, no advertising or analytics SDK, and no third-party tracker. It does not ask for your location, your contacts, your photos or your files. It reads nothing on your device that you have not handed to it.

9. Connected Accounts

Dewiride AI can connect to accounts you already hold elsewhere — Google, Microsoft 365, GitHub, LinkedIn, Azure and others — so that the assistant can look things up and act for you in those services. A connection is made only when you start one, and only with the permissions you tick on the connect screen before you are sent to the provider to sign in.

We hold an access token and a refresh token for each connected account, encrypted in our database, and we use them for nothing except carrying out the requests you make in Dewiride AI. Disconnecting an account in Integrations deletes those tokens immediately, and you can also withdraw the app's access from the provider's own account settings.

10. Documents You Add to Knowledge

You can give the assistant documents to answer from, by uploading files or by choosing SharePoint sites, libraries or folders from a connected Microsoft 365 account. Nothing is read unless you add it.

• What we keep: a file you upload is stored for you, encrypted, until you remove it, remove its collection, or close your account. For documents in SharePoint we keep no copy of the file itself.
• Safety checks: every uploaded file is checked for malware by Microsoft Defender for Storage before it is read or can be opened. A file found to be unsafe is deleted and never used.
• How they are read: the text of each document is turned into searchable passages kept in our database, so the assistant can quote the right part. Your documents are only ever searched for you, and are never used to train AI models.
• Removing: removing a file or collection deletes its passages, and for an upload the file itself. Closing your account deletes all of them on the timetable in section 17.

11. WhatsApp Business

A business can connect its own WhatsApp number to Dewiride AI to receive the messages its customers send to it and send the business's replies. We handle those customers' information on that business's behalf and on its instructions: the business decides which number to connect, how long its chats are kept and when to disconnect it, and it answers to its own customers for those choices.

• What we receive: the messages customers send to the connected number, the files they attach, and the delivery and account information that comes with them, such as a customer's WhatsApp profile name and phone number, and the number's own standing with WhatsApp. It reaches us from Meta Platforms, which provides the WhatsApp Business Platform under its own terms.
• How it is protected: message content and customers' phone numbers are encrypted in our database, and every file a customer sends is checked for malware before the business can open it. A file found to be unsafe can't be opened.
• Who can read it: the business, in its own Dewiride AI account, on the web or in the Dewiride AI app, and — when it asks its assistant about its customers in Microsoft Teams or on WhatsApp — in that chat, as described below. It is not shown to anyone else, it is never sold, it is never used for advertising or to train AI models, and it is not shared outside the recipients listed in section 3.
• Where AI is involved: a business can have AI read a message from one of its customers that matches none of its number's keywords, to recognise a request to talk to a person or to stop getting messages, which sends that message to the model provider named in section 3.
• The business's own assistant: when the business asks its Dewiride AI assistant who is waiting, the assistant is told each waiting customer's WhatsApp profile name (or, for a customer without one, their WhatsApp username, or else only the country code and last four digits of their phone number), why they are waiting, since when, and whether a reply can be sent now and until when (for example, not when a customer has asked to stop getting messages) — never what they wrote. That answer goes to the model provider named in section 3, and in a spoken conversation also to the speech provider named there, which turns it into a voice as section 7 describes. It is kept in the business's conversation with its assistant until the business deletes it; if the business asked in Microsoft Teams or on WhatsApp, the answer is also delivered there, and that app keeps it under its own terms even after the conversation is deleted here. A reply the business asks its assistant to send is shown to the business first, with the customer it goes to and its exact words, and sent as the business's own reply only once it approves it.
• How long it is kept: a chat is deleted, with its messages and files, once nothing new has happened in it for the period the business chooses, which is 6 months unless it chooses otherwise. When a number is disconnected, its chats are deleted 30 days later, or at once if the business asks. When the business closes its Dewiride AI account, its numbers are disconnected and their chats are deleted with the account. When a customer asks to stop getting messages, a one-way fingerprint of their phone number or WhatsApp ID is kept after their chat is deleted, until the business's number is removed from Dewiride AI, so their request keeps being honoured.
• Connecting through Facebook: a business connects its number by signing in to Facebook in Meta's own window. We keep no personal information from the Facebook account used to do that. If you ask Facebook to delete the information an app holds about you, Meta sends us your request and gives you a link to a page that shows its status.

If you have written to a business that uses Dewiride AI and want to see or delete what it holds, ask that business first, because it decides what happens to its chats. You can also write to us at support@dewiride.com, and we will help you or pass your request on to the business.

12. Google User Data and Limited Use

When you connect a Google account, Dewiride AI receives data from Google APIs. This section sets out exactly what we access, why, and what happens to it.

• Gmail (gmail.modify, gmail.send) — we list your inbox, sent items or drafts with each message's sender, subject, date, read state and short preview; and, when you point us at one, we open a message or a whole conversation and read its recipients, its body as plain text, and the names and sizes of anything attached to it — never the contents of an attachment. That is what lets the assistant tell you what has arrived, find a message you describe, and summarise or answer questions about it.
• Gmail, continued — when you ask, or an agent you set up calls for it, and — unless you have let that chat or agent act on its own — only after you approve it, we also mark messages read or unread, star them or take the star off, mark them important or not important, apply or remove your own labels, archive a message or put it back in your inbox, report one as spam or take it back out of your spam folder, file one under an inbox tab such as Promotions or Updates, move one to the bin or restore it from it, and save a draft reply on the original conversation for you to read before you send it. We send a message on the same terms: a new email, or a reply to one you received that goes to its sender, or to everyone on it, and stays in the same conversation. We never delete mail permanently and we never change your Gmail settings: the permission we hold does not allow either, so neither is possible even by mistake.
• Google Calendar (calendar.events) — we read the events on your calendars, including who was invited, how each person replied and any meeting link, to answer questions about your day. When you ask, or an agent you set up calls for it, and — unless you have let that chat or agent act on its own — only after you approve it, we create an event, change or reschedule one, cancel one, or reply to an invitation on your behalf.
• Google Tasks (tasks) — we read your task lists and what is on them to tell you what is outstanding. When you ask, or an agent you set up calls for it, and — unless you have let that chat or agent act on its own — only after you approve it, we add a task, rename it, change its notes or its due date, tick it off or put it back, or delete it.
• Google Analytics (analytics.readonly) — we list your GA4 properties, look up which metrics and dimensions each property supports so a report is built from fields that exist, and run the reports you ask for on traffic, engagement and conversions.
• Google Search Console (webmasters.readonly) — we read your verified sites, search performance, sitemaps and URL index status.
• Google Business Profile (business.manage) — we read your business accounts, locations, daily performance metrics, and the reviews customers have left you along with their star ratings, so the assistant can tell you how each location is doing and what people are saying. Google publishes no read-only Business Profile permission, so this is the only one that returns that data, and we use it to read and nothing else. We do not edit a listing, publish a post, reply to a review, or change your opening hours.

How it is used: only to produce the answer or carry out the action you asked for, in the conversation where you asked for it. To do that, the relevant content is sent to the AI model provider named in section 3, which processes it under a written contract, solely on our instructions, and not for its own purposes.

How it is stored: your request, the result, and the conversation they belong to are encrypted in our database, as are the tokens for the connection. They are kept while the conversation exists and are deleted with it, with your account, or when you disconnect the Google account, on the timetable in section 17.

What we never do: we do not sell Google user data, we do not use it for advertising or to build advertising profiles, and we do not use it to create, train or improve any general-purpose artificial intelligence or machine-learning model. No member of our staff reads it — except with your explicit permission, where it is necessary to investigate a security incident or abuse, or where the law requires it.

Dewiride AI's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

You can review and remove Dewiride AI's access to your Google Account at any time at myaccount.google.com/permissions, and you can disconnect it from Integrations inside Dewiride AI.

13. LinkedIn Data and How Long We Keep It

When you connect a LinkedIn account, Dewiride AI receives information from LinkedIn. LinkedIn places strict limits on how long information about its members may be held, and those limits decide how this part of the product is built, so this section sets out exactly what we read, where it is shown, and what is and is not kept.

• Your own LinkedIn profile — your name, your headline, your public profile address, and the identifier LinkedIn knows you by. We read it when you connect, so that we can label the account and publish as you.
• Your own posts — when you ask, and only after you have approved the wording, we publish a post to your LinkedIn feed, correct one you have already published, or delete one. A post can carry a link, or a file the assistant has made for you, such as a set of slides.
• The LinkedIn Pages you run — we list them and read their names so that you can choose one, and we publish, correct and delete posts on a Page in the same way, again only when you ask and approve. A Page's post can also carry a photograph, which we find in a library of free-to-use pictures and credit underneath the post.
• Comments and reactions — when you ask and approve it, we reply to a comment, react to a post or a comment, and take a comment down, either as you or as the Page.
• What people have said under your Page's posts — the comments themselves, together with each commenter's name, headline and public profile address. That is other people's information, and it is handled differently from everything else here; see below.
• How your Pages and posts are doing — how often they were shown, clicks, reactions, comments, shares, follower and visitor counts, and the same figures for your own posts and your own followers.

Other people's information is never stored, and never reaches the assistant. Comments left by other LinkedIn members appear on one screen inside Dewiride AI — "What people are saying" — which reads them from LinkedIn each time you open it and keeps nothing. LinkedIn does not tell us who wrote a comment: it gives us only an internal reference number, so the screen shows the words and when they were written, and says plainly that it cannot show the person's name. Where the comment came from a company page rather than a person, the page's name is shown. We do not write any of it to our database, we never put it into a conversation with the assistant, we never send it to the AI model provider named in section 3, and we never email it to you, put it into a file, or deliver it to Microsoft Teams or WhatsApp. If you copy something from that screen into a message yourself, it is then part of your conversation and is treated like anything else you write there. Close the screen and nothing about those people stays with us. Only you see them: the screen reads through your own connection, so a Page's comments are shown only to someone LinkedIn says runs that Page.

Your own information is kept like the rest of your account. Your LinkedIn profile details, your Page's own posts, and the figures for your Pages and posts can appear in a conversation with the assistant. They are then encrypted in our database and deleted with that conversation, with your account, or when you disconnect the LinkedIn account, on the timetable in section 17.

What we never do: we do not use LinkedIn information for advertising, for selling, or for recruiting; we do not use it to build a list of prospects or to add to any customer record; we do not combine it with information from anywhere else; we do not export it, sell it, or pass it on; we do not show anyone's LinkedIn information anywhere but inside Dewiride AI; and we do not use it to create, train or improve any artificial-intelligence model.

You can withdraw Dewiride AI's access at any time in your LinkedIn account settings, and you can disconnect the account from Integrations inside Dewiride AI, which immediately deletes what we hold for that connection.

14. Your Rights

You have the right to:

• Access and update your personal information
• Request deletion of your personal information
• Object to or restrict certain processing of your information
• Withdraw consent where processing is based on consent
• Data portability

15. Cookies and Tracking

We use cookies and similar tracking technologies to collect information about your browsing activities. You can control cookies through your browser settings, but disabling them may affect your experience on our website.

16. International Transfers

Your information may be transferred to and processed in countries other than your own. We ensure appropriate safeguards are in place to protect your personal information in accordance with applicable data protection laws.

17. Data Retention

We keep personal information only for as long as we need it. Account and Dewiride AI conversation data is kept while your account is open and deleted within 90 days of closure, unless you ask us to delete it sooner. Order, invoice and payment records are kept for 8 years, as required by Indian tax and company law. Analytics data is retained in aggregated form only.

Support conversations follow whoever opened them. One opened from your account — with its messages, files and session details — is deleted with your account, on the same timetable. One opened without an account, from the contact form, is deleted 180 days after it is closed. Ratings and product feedback you leave are kept after your account goes, with you no longer attached to them, so that the aggregate scores they feed stay correct.

Chats that a business's customers send to a WhatsApp number it connected are kept for the period the business chooses, by default 6 months after the last message, and a disconnected number's chats are deleted 30 days later. A one-way fingerprint of the phone number or WhatsApp ID of a customer who asked to stop getting messages is kept until the business's number is removed from Dewiride AI, so the request keeps being honoured.

A mobile device's notification registration is shorter-lived than any of that. It is deleted the moment you sign out on that device, as soon as Google tells us the device has stopped accepting notifications, after nine months without one being delivered, and with your account.

18. Children's Privacy

Our products are not directed at children. We do not knowingly collect personal information from anyone under 18. If you believe a child has provided us with personal information, contact us and we will delete it.

19. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any significant changes by posting the new policy on our website and updating the "Last updated" date.

20. Contact Us

If you have any questions about this Privacy Policy, or wish to exercise any of your rights, please contact us — by email, or from the contact form on this website, which opens a conversation with the same team. We respond within 1 business day. If you are not satisfied with our response, you may escalate to our grievance officer, who will acknowledge within 48 hours and resolve within 15 days.

Dewiride Technologies Private Limited

Privacy & data requests: support@dewiride.com

Grievance officer: grievance@dewiride.com

Phone: +91 8955643412 (Monday to Friday, 9:00 AM – 6:00 PM IST)

Address: C/o Jagdish Kumawat, Village Tena, Tehsil Shergarh, Jodhpur – 342028, Rajasthan, India