Privacy Policy

1. Who is responsible

Seqora is a personal project, not a company. It is built and run by one individual, Ayushman Gupta, based in Hyderabad, Telangana, India (“I”, “me”). This policy covers the website at seqora.dev, the news and updates email list, email sent to or from seqora.dev addresses, the Seqora desktop app, and the online services the app talks to.

For the personal data described here, I am the “Data Fiduciary” under India's Digital Personal Data Protection Act, 2023, and the “controller” under the EU and UK General Data Protection Regulation (GDPR). You can reach me about anything in this policy at privacy at seqora dot dev.

2. The website

Hosting

The website is hosted on Cloudflare. Like any web host, Cloudflare handles the technical details of each request, including your IP address, browser and the page you asked for, so it can deliver the page and protect the site from attacks. I don't keep my own server logs of your visits.

Visit statistics

I use Umami (Umami Cloud) to count visits. Umami doesn't use cookies, and as Umami describes it, it doesn't store your IP address or build a profile of you across sites. It records things like the page you viewed, the site that linked you here, your browser, operating system, device type, screen size, language and approximate country. It also counts a few things done on the site, such as which sections were viewed and for roughly how long, which download or pricing button was used, whether a trial or buy button was clicked and a checkout was completed, how far someone got with the demos, and whether an email sign-up went through. I also count which Guide articles are opened, read for at least 30 seconds in a visible tab, or read to the end, which Guide links and questions are opened, which install method is chosen, whether copying an install command succeeds, and whether the checkout handoff needs a retry. These are recorded as labels only, such as which plan a button was for. They never include your email address, your payment details, your licence key or anything you type. I only see totals. I use them to learn which parts of the site are useful.

Cookies

The site sets no advertising or tracking cookies. Cloudflare and Turnstile (see below) may use strictly necessary technical data to keep the site secure and tell people from bots.

3. News and updates by email

When you sign up for news and updates, I store the following. If you signed up before Seqora's release, your address is on this same list and is handled the same way.

• your email address;
• which sign-up form you used, where the page has more than one;
• the website that sent you here, as its host name only (for example “news.ycombinator.com”, never the full address);
• the campaign tags in the link you followed, if any (utm_source, utm_medium, utm_campaign);
• your country, which Cloudflare estimates from your IP address (I don't store the IP address itself);
• the date and time you signed up.

Bot protection. When you start filling in the form, Cloudflare Turnstile checks that you are a person. It looks at signals from your browser and your IP address, and my server sends your IP address to Cloudflare with the check. Cloudflare handles this data under its own privacy policy.

What I use it for. To send you one welcome email (through Resend), to send you news and updates about Seqora, such as new releases and news about Pro, and to see which links bring people to the site. I don't send email about anything else, and I never give or sell your address to anyone for their own marketing. To leave the list, reply to any email or write to the privacy address above.

4. Email

Email sent to a seqora.dev address passes through Cloudflare Email Routing and lands in my personal Gmail inbox, provided by Google. Replies are sent from Gmail, and automated messages such as the sign-up welcome are sent through Resend. I keep your message, your address and whatever you choose to include so I can reply and follow up.

5. The desktop app

What stays on your computer

Seqora has no account and no cloud sync. Connection details, databases and their contents, queries, query history, schema designs and settings are stored only on your computer. Passwords and other secrets are kept in an encrypted database on your computer, and the key that unlocks it is kept in your operating system's credential store (the Windows Credential Manager or the macOS Keychain). None of this is sent to me.

What the app connects to

Apart from the databases you connect it to, Seqora goes online only for the things described below: update checks, crash reports if you switch them on, feedback when you send it, an Ollama server you choose for AI features, and, if you use Pro, the licence checks in section 6. On Free, Seqora makes no licence checks at all.

AI assistance

Seqora's AI features use a model running on your own computer through Ollama. Your prompts and the schema details they include go to that local model, not to me or to a cloud AI service. If you point Seqora at an Ollama server somewhere else, that data goes to the server you chose, under your control.

Crash reports (only if you opt in)

Crash reports are off until you say yes, and you can turn them off at any time in Settings › Privacy › Send crash reports. When they are on, Seqora sends a report to Sentry if the app crashes or hits an unexpected error. A report contains the error message and stack trace, the Seqora version, and your operating system and CPU architecture.

Before a report leaves your computer, Seqora removes your computer name and user identity, and redacts connection strings, passwords, IP addresses, email addresses and the user name in file paths. It never includes your queries, query results, connection details or files. Sentry sees the IP address of the connection that delivers the report; Seqora tells Sentry not to store or use it.

Feedback (only when you send it)

If you use “Send feedback” or “Report a problem”, Seqora sends what you write, the area of the app it concerns and, if the report came from an error, the error's code. Unless you remove the diagnostics before sending, it also sends the Seqora version and release channel, your operating system family and major version, CPU architecture, web view version, and the time to the minute. The feedback service doesn't currently accept screenshots; if that changes, I'll update this policy first.

Feedback is anonymous: it carries no name, email or account. It goes to my feedback service on Cloudflare, which files it as an issue in a private GitHub repository that only I can read. Cloudflare sees your IP address while delivering the report, but the service doesn't store it. Because reports are anonymous, I can only find yours if you give me the receipt ID Seqora shows after sending (a short code starting with ELR-). Please don't put passwords, customer data or other people's personal data in feedback.

Update checks

Unless you set Updates to “Off” in Settings, Seqora checks once a day by downloading a small file describing the latest release from my release hosting on Cloudflare, and downloads the update itself when you install one. The Releases list in Settings › About is fetched the same way. As with any download, the host sees your IP address and the request reveals your app version and platform. I don't use this to identify you.

6. Pro: payment and licence checks

Everything in this section happens only if you start the Pro trial or buy Pro. On Free, Seqora sends none of it.

Polar, the merchant of record

Pro is sold by Polar Software Inc. (“Polar”), which acts as the merchant of record: it runs the checkout, takes your payment, works out and pays tax, sends your receipts, processes refunds and runs the customer portal where you manage your subscription. At checkout Polar collects your email address, your payment details and your billing country (and, where tax rules need it, your address), and handles them under its own privacy policy. Polar's card processor handles your card. Seqora never sees your card number.

Through Polar's dashboard I can see what I need to run your subscription and help you with it: your email address, your country, your plan, and your payments and refunds. I use it only for that, such as answering a support or refund request.

Your licence key

Each trial and subscription comes with a licence key, which Polar emails to you. When you activate Pro on a computer, the app sends Polar's licence service the key, Seqora's organisation id at Polar, and a label for the computer: its name, so you can tell your computers apart in Polar's customer portal. Polar answers with an activation id for that computer.

After that, the app checks the key again when it is online, about once each time you open Seqora, by sending the key, the activation id and Seqora's organisation id. It remembers the result on your computer, in its encrypted settings database, so Pro keeps working offline for up to 30 days between checks. When you deactivate Pro on a computer, the app tells Polar the same way. As with any request, Polar sees your IP address. These checks never include your databases, queries, connection details or files.

seqora.dev's licence service

The app may also contact my licence service at seqora.dev for two things:

• Finishing a purchase started in the app, so you don't have to copy the key. The app makes a random one-time code, puts a scrambled form of it (a hash) on the checkout link, and once the checkout is done, sends the code to seqora.dev to collect your key. The checkout confirmation page on the website asks the same service for the key of the checkout you just finished.
• Reading your subscription details for the app's Licence page and notices: your plan, the trial end, renewal and end dates, and whether a payment is due or has failed. To prove it holds the key, the app sends the key, its licence-key id and the activation id.

To answer these, Polar tells my server when a checkout, subscription or licence key changes. The server stores only Polar's identifiers (the checkout, customer, subscription and licence-key ids), with the plan, its status and dates, the masked form of the key Polar shows (its last few characters), and the hash of the one-time code. It never stores your email address, your name, your payment details or your full licence key. Cloudflare, which hosts the service, sees your IP address while delivering a request; the service doesn't keep it.

Pro never depends on this service being up. If it is unavailable, Pro keeps working and you can paste your key instead.

7. Why I'm allowed to use it

• Your consent: signing up for news and updates, switching on crash reports, and sending feedback. You can withdraw consent at any time; it doesn't affect what happened before you withdrew it.
• A contract with you: selling you Pro, checking your licence so Pro keeps working, and showing your subscription details in the app.
• Legitimate uses (GDPR “legitimate interests”): counting visits without identifying anyone, stopping bots and abuse, keeping the site and update service working, and answering email you send me.
• Legal obligations: keeping or disclosing data when a law or a valid legal order requires it.

8. Who else handles it

I don't sell or rent personal data, and I don't share it for advertising. These service providers process it on my behalf, only to run the parts of Seqora listed:

I may also disclose data if the law or a valid legal order requires it, or to protect Seqora, its users or the public from fraud or abuse. If I move Seqora into a company I form, or hand the project to someone else, the data described here would move with it and this policy would keep applying to it until you are told otherwise.

9. Where it's processed

I'm in India. The providers above may process data in the United States, the European Union and other countries where they operate. Where a provider offers safeguards for international transfers, such as the EU Standard Contractual Clauses, I rely on them.

10. How long I keep it

11. Security

I collect as little as I can, scrub crash reports before they leave your computer, keep secrets in the operating system's credential store, use encrypted connections, sign app updates, and limit access to the accounts that hold this data to myself. No system is perfectly secure. If a breach affects your personal data, I will notify you and the authorities as the law requires.

12. Your rights

Wherever you live, you can ask me to:

• tell you what personal data I hold about you and how I use it;
• correct, complete or update it;
• delete it;
• stop using it, or withdraw consent you gave;
• give you a copy in a common format.

Under India's DPDP Act you may also nominate someone to exercise these rights for you if you die or become unable to. Under the GDPR you may also object to processing based on legitimate interests and ask me to restrict it.

Write to the privacy address below. I may ask you to confirm that you control the email address concerned. I aim to answer within 30 days. It's free.

13. Children

Seqora is a professional tool for people aged 18 and over. I don't knowingly collect data from anyone younger. If you believe a child has given me their data, tell me and I will delete it.

14. Changes to this policy

When Seqora starts collecting something new, or uses data in a new way, I'll update this page and its date before the change takes effect. If the change is significant, I'll also tell people on the email list or show a notice in the app. Earlier versions are available on request.

15. Contact and complaints

Ayushman Gupta handles all privacy questions, requests and complaints (the grievance officer under the DPDP Act). Write to privacy at seqora dot dev.

If you're not satisfied with my answer, you can complain to the Data Protection Board of India or, in the EU or UK, to your local data protection authority.