Privacy policy
Last updated 20 July 2026
Setu sends email from your own Gmail account. This page sets out exactly what it can see, what it stores, and how to remove it.
The short version
- Setu can send email as you. It cannot read your inbox.
- It never sees or stores your Google password.
- It stores no Google tokens at rest.
- Your data is never sold, and never used for advertising.
- You can revoke access and request deletion at any time.
What Setu accesses in your Google account
When you connect Setu, Google asks you to grant these permissions and nothing else:
| Permission | Why |
|---|---|
gmail.send | To send the emails you approve, from your account. |
userinfo.email | To know which account you are, so your data is yours. |
openid | Standard sign-in identifier. |
Setu cannot read your inbox. Reading mail requires a separate permission (gmail.readonly or similar) that Setu never requests and could not use. This is not a policy choice we could quietly reverse — it is the boundary Google enforces on the permission you granted. Replies from the people you email go to your inbox only.
What Setu stores
| Data | Why it exists |
|---|---|
| Your Google account ID, email address, and name | To identify you across sessions and clients. |
| Your role, saved links and their descriptions | To attach the right resume or portfolio to your emails. |
| Files you upload | So the document can be linked in the emails you send. |
| A record of each email sent: recipient, company, subject, time, and whether it succeeded | To show your history, enforce sending limits, and avoid emailing the same person twice. |
| Link-open counts and timestamps | To tell you when a follow-up is worth making. |
| Plan and subscription dates | To apply the free allowance and any paid plan. |
Setu does not store Google access or refresh tokens. The OAuth layer supplies a short-lived token per request, so there is no credential of yours sitting in the database.
Email bodies are not stored. Setu keeps the subject line and the recipient for your history, not the text you sent.
Link tracking, and the people you email
When Setu attaches your resume link, it wraps it in a redirect so it can count opens. If the recipient clicks it, Setu records that a click happened and when, then sends them straight on to your document.
This is worth being plain about, because it affects someone who never signed up for Setu: recipients are not individually identified. Setu records a count and a timestamp against the email you sent. It does not build a profile of the recipient, and does not sell or share this with anyone.
An open is also only a signal, not proof — automated link scanners exist, and a person can read your email without clicking anything.
Website visitors
When you visit this site, Setu records your IP address, an approximate location derived from it (city, region, country, network), your browser user agent, and which page you opened. Repeat visits from the same IP increment a counter rather than creating new records.
This is used to understand traffic. It is visible only to the site operator, and is not used for advertising or shared with advertisers.
Who else is involved
Setu relies on these services to operate:
| Service | Role |
|---|---|
| Sign-in and the Gmail API that delivers your email. | |
| Neon | The database where the data above is stored. |
| Render | Hosting for the Setu server. |
| Vercel | Hosting for this website. |
| ip-api.com | Turns a visitor IP into an approximate location. |
Your data is not sold, rented, or shared with anyone beyond what these services need to do their job.
Google API Services Limited Use
Setu's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, data obtained through Google APIs is used only to provide the features described here, is not transferred to others except as required to operate the service or by law, is not used for advertising, and is not read by humans except with your explicit permission, for security purposes, or where required by law.
Deleting your data
Two independent steps, both available to you at any time:
- Revoke access at myaccount.google.com/permissions. Setu immediately loses the ability to send anything. You do not need our cooperation for this.
- Request deletion by emailing himanshuyada70@gmail.com from your Setu account address. Your record, saved links, uploaded files, and send history are removed.
Emails already delivered cannot be recalled — they are in the recipient's mailbox, outside Setu's reach.
Reading the code
Setu is open source. If a claim on this page matters to you, you can check it against the implementation rather than take our word for it: github.com/gitmanhimanshu/Email_automation.
Changes and contact
If this policy changes in a way that affects what is collected or how it is used, the date at the top will change. Questions, corrections, or deletion requests: himanshuyada70@gmail.com.