Privacy Policy

Quegent, Inc. ("Quegent", "we", "us") runs quegent.com and the Quegent workflow automation platform, from Gujarat, India.

This policy explains what we collect when you use Quegent, why we collect it, who we share it with, and what you can do about it. If anything here is unclear, write to us at the address at the bottom of this page.

• Account details: your name, email address, and either a password (stored only as a one-way hash) or your Google sign-in identity. Also your workspace name, the teammates you invite, and any onboarding answers you give us.
• Your workflows and runs: the workflows you build, the variables you save, and the inputs, outputs, status and logs of each run. If a workflow handles your own customers’ details, such as leads from a web form, that data passes through Quegent while the workflow runs.
• Connected accounts: the API keys, tokens and passwords you give us so a workflow can act on your behalf, for example Slack, Salesforce, an AI provider or an SMTP mailbox. These are encrypted before they are stored and are never shown again once saved.
• Billing: your plan and payment status. Card and UPI details go straight to our payment provider, Razorpay, and are never stored by us.
• Messages you send us: anything you write through the contact form or by email.
• Technical data: your IP address, browser and device details, sign-in sessions, security and audit logs, and error reports.

You can connect a Google account, for example Gmail, Google Sheets, Google Calendar or Google Ads, so your workflows can use it. Quegent asks Google only for the permission each connector needs to do its job. For Gmail that is the permission to read, send and manage mail, and we use it only to run the workflows you build.

• We use Google data only to provide the features you asked for. We do not sell it, and we do not use it for advertising.
• We do not use it to develop, improve or train generalised AI or machine-learning models.
• We do not let people read it, except when you ask us to for support, when it is needed to keep the service secure or to obey the law, or when the data has been aggregated and anonymised.
• The tokens Google gives us are stored encrypted, and you can remove them at any time by deleting the credential in Quegent.

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

You can also take Quegent’s access away from your Google account whenever you like. Manage Google permissions

• To run the service: build, save and execute your workflows, and show you the results.
• To keep it safe: sign you in, limit abuse, detect fraud and keep an audit trail of changes.
• To bill you and to tell you about your account, such as sign-in codes, invitations and receipts.
• To fix and improve the product, mainly through error reports and support conversations.
• To meet our legal obligations.

We do not sell your personal data, and we do not run advertising.

Only with the companies that help us run Quegent, and only what each one needs:

• Razorpay, to take payments and manage subscriptions.
• Google, when you sign in with Google or connect a Google account.
• Sentry, which receives error reports so we can find and fix faults.
• Our hosting and email delivery providers, which store our data and send our emails.

Two things are worth being clear about. First, when you build a workflow that talks to another service, such as Slack, Salesforce or an AI provider, Quegent sends data to that service because you told it to, and that service’s own privacy policy applies to what it receives. Second, AI features run on the AI account you connect, so the text a workflow sends to the model goes to your provider under your own key.

We may also disclose information where the law requires it, or to protect the rights and safety of our users and of Quegent, and it may transfer to a successor if Quegent is ever merged or sold. We will tell you before that happens if it changes how your data is handled.

Quegent uses a small number of cookies, all of them necessary for the site to work:

• quegent.session keeps you signed in. It is not readable by scripts on the page. Unless you tick "remember me" it disappears when you close the browser, and if you do tick it, it lasts up to 30 days.
• A theme cookie remembers whether you chose the light or dark look.
• A notice cookie remembers that you dismissed the announcement bar.

We do not use advertising or cross-site tracking cookies, and we do not run third-party analytics.

Connected-account secrets are encrypted before they reach our database. Sign-in sessions live in cookies that scripts cannot read, traffic is served over HTTPS, and access to a workspace is limited to the people in it, by role.

No system is perfectly secure. If we learn of a breach that affects your data, we will tell you and the authorities as the law requires.

We keep your data while your account is open. You can delete your account from Profile, then Delete account, inside the dashboard. When you do, we delete or anonymise your personal data and workflows, except for what we must keep for legal, tax or security reasons, such as payment records.

You can also delete a single credential or workflow at any time, which removes it from Quegent.

You can see and correct your details in Profile. Depending on where you live, and including under India’s Digital Personal Data Protection Act, 2023, you may also have the right to ask for a copy of your data, to have it corrected or erased, to withdraw consent, and to complain about how it is handled.

To use any of these rights, or to raise a concern, email us. We will answer within a reasonable time.

Quegent is built for businesses and is not meant for anyone under 18. We do not knowingly collect data from children, and if we learn that we have, we will delete it.

When we change this policy we will update the date at the top. If the change is significant, we will also tell you by email or inside the product before it takes effect.