Privacy Policy

Last updated

Summary

We keep as little as we can. When you sign in with GitHub we store your GitHub id, username, account creation date and, if GitHub gives us one, your email address, all taken from your GitHub account. Your pods are public: their names, your GitHub username, where they point and when you claimed them are published in the public register. We don't run ads, analytics or tracking, we don't sell data, and we only use sign-in cookies plus Google reCAPTCHA on the claim and report forms. Some checks on names and pods are automatic, and a person reviews any appeal. Logs, closed reports and decided requests are deleted after 30 days. You can delete your pods and then your account yourself in My Pods, or write to privacy@podu.dev to see, fix or delete your data, free of charge.

Who is responsible

Podu is run by Instructorium, based in Dhaka, Bangladesh. We decide how your data is used (we are the “controller”). For any privacy question or request, write to privacy@podu.dev. Our postal address is Suite 501, Level 4, Mahabub Plaza, Indira Road, Farmgate C/A, Tejgaon, Dhaka-1215, Bangladesh.

What we collect

When you sign in with GitHub, we store these details, which come from your GitHub account each time you sign in:

  • your GitHub numeric id and username (login);
  • the date your GitHub account was created, to check the 30-day rule;
  • the email address on your GitHub profile, or your primary GitHub email if your profile shows none;
  • the time you last signed in.

We also keep a few fields about your account: whether you are an admin, whether and why your account is banned, and any personal pod limit we set for you, with the reason.

For each pod, we store its name, where it points (the host), its DNS records, the description you give it, its status, the results of our scans and the dates it was claimed and changed. We also keep a journal of the DNS records Podu created, so we only ever change our own records.

If you add host verification values, we store each value, its pod and when it is removed.

An audit log of changes: who made the change (GitHub username and id), what they did, which pod, the records before and after, and when.

For rate limits, a keyed hash (HMAC) of your IP address. Podu does not store your raw IP address.

If you report a pod: the pod name, the reason, the details you write and, if you choose to give it, your email address.

If you send a request, we store it with its status, when it was sent and decided, and our decision note:

  • NS delegation: the pod, the nameservers you asked for and your reason;
  • email (MX) records: the pod, the mail servers with their priorities, the name of your email provider and your reason;
  • a special name: the name, the host and target you asked for and your reason.

Pod details and requests come from you. Scan results come from our own checks. A report about a pod comes from the person who sends it.

Podu itself collects nothing else about you: no location, no device fingerprint, no browsing history.

What is public

Podu is open by design, to keep the service transparent and abuse easy to spot:

  • The public register at github.com/podu-dev/register has one file per pod with the pod name, the owner’s GitHub username, the host, the records and the claim date.
  • The pod lookup page and its public API show a pod’s owner (GitHub username), its history and, unless it was taken down, its records and the result of its latest safety scan (clean or flagged). The history shows when the pod was claimed and changed, with the owner’s GitHub username, and when it was taken down, shown as “Podu”.
  • DNS records are public by nature. Anyone can look them up.
  • If you add a host verification value, it is published in a shared DNS record at _vercel.podu.dev, next to other users’ values. It is public in DNS and in the public register, listed with your pod, until it is removed after 14 days or sooner if you remove it.
  • Email authentication records (SPF, DMARC and DKIM) are public DNS data, like any other pod record.

The text of your reports and requests, your email address and the email provider you name are never published. An approved name request becomes a public pod, and the records added by an approved NS or email request are public like any other pod record.

Why we use it

  • To provide the service you asked for: sign-in, claiming and managing pods, and emails about your pods. This is needed to perform our agreement with you (the Terms).
  • For security and to prevent abuse: the account age check, rate limits, the Google Safe Browsing checks and weekly scans, handling reports, the audit log and the public register. We rely on legitimate interests: ours, our users’ and those of people who visit pods, in keeping podu.dev safe and trusted. We have weighed these against your interests. We use as little data as we can, scans look at the pod and where it points, not at you, and the register shows only your GitHub username, which is already public, and DNS data, which is public by nature.
  • To meet legal obligations, for example answering a valid legal request.

We email you only about the service, for example claims, scan warnings, releases, takedowns, decisions on your requests, appeals and changes to these policies. No newsletters and no marketing. We do not use your data for advertising, analytics or profiling, and we never sell it.

Automatic decisions

Some decisions about names and pods are made by software, without a person:

  • the name check, which refuses names our rules don’t allow, such as reserved, technical or offensive names, when you claim one;
  • the Google Safe Browsing check, which refuses a target Google lists, and suspends a pod at once if a scan finds it listed;
  • the scans, which release a pod that points at nothing for 14 days, or whose site does not answer for 90 days and still does not answer 14 days after our warning email.

Every automatic suspension can be appealed and is reviewed by a person: see Appeals. If a name is refused, write to support@podu.dev, or ask for it with a name request where the claim page offers one. A released name is free again, so you can claim it again. The Terms explain these checks.

How long we keep it

  • Audit log, including what our scans did: 30 days. A pod keeps only the result of its latest scan.
  • Hashed IP addresses for rate limits: 48 hours.
  • Abuse reports: 30 days after the report is closed. A report that led to a takedown is kept while the pod stays taken down.
  • NS and email (MX) requests: 30 days after the decision, or sooner if you delete the pod.
  • Special name requests: 30 days after the decision, or sooner if your account is deleted.
  • Host verification values: 14 days after you add them, or sooner if you remove them or the pod goes.
  • Your account: until you delete it in My Pods, or while you have pods or open requests. If you have neither, we delete it 12 months after your last sign-in.
  • Pods: when you delete a pod or it is released, we remove its row at once, or within minutes if removing its DNS records has to be retried. Its history stays in the audit log for 30 days. Its file is removed from the public register at the next nightly export, but the register’s git history keeps earlier versions.
  • Suspended (taken-down) pods stay as evidence until we release them. Takedown and ban details are kept on the pod and the account for as long as the takedown or ban lasts.
  • Backups: a backup provider keeps a copy of accounts, pods with their records, open and approved requests, takedown and ban details, and a record of the DNS entries Podu created, made every night. We keep the last 14 nightly copies; older copies are deleted, so deleted data leaves the backups once 14 newer copies exist. Backups hold no logs and no IP addresses of visitors or of people signing in. They do include the IPv4 addresses you put in your pods’ records, because those are part of the pods’ public DNS records.

Who we share it with

We use a small number of service providers to run Podu. They process data for us, and only what they need:

  • A hosting provider runs the website and app. Its request logs include IP addresses, kept under its own retention.
  • A database provider stores our Postgres database.
  • A backup provider stores the nightly copies of our database described under How long we keep it. They hold no logs and no IP addresses of visitors or of people signing in.
  • A DNS provider publishes the DNS records for podu.dev.
  • An email provider sends our emails.
  • GitHub: sign-in, and hosting the public register.
  • Google: reCAPTCHA (bot checks on the claim and report forms) and Safe Browsing. With reCAPTCHA, Google receives your IP address and browser information. Safe Browsing receives where a pod points when you claim or change it or ask for a name, and the pod’s address and where it points during scans.
  • A scheduling service starts our scheduled jobs. It receives no personal data.
  • A public DNS-over-HTTPS resolver looks up pod names during scans and the nameservers you ask for in an NS request. It receives no personal data.

We may share data when the law requires it, or to protect people from harm, for example by reporting child sexual abuse material to the authorities.

International transfers

Podu is operated from Bangladesh, outside the EU and the UK. Bangladesh has no adequacy decision from the EU or the UK, which means neither has found that its law protects personal data to their standard. We protect your data as this policy describes.

Our providers process data outside Bangladesh and outside the EU and UK, mainly in the USA. Where a provider offers them, we rely on standard contractual clauses or the EU-US Data Privacy Framework to protect your data.

Cookies

We use only cookies that are strictly needed for what you ask Podu to do:

  • Sign-in cookies from Auth.js: a session token that keeps you signed in, a CSRF token that protects forms, and a callback URL that returns you to the right page after sign-in. They are set only on dash.podu.dev, where you sign in and manage your pods, and are never sent to www.podu.dev or to any pod.
  • Google reCAPTCHA loads only after you start filling in the claim form or the report form, not when a page opens. Google sets its own cookies to tell people from bots. reCAPTCHA is subject to Google’s Privacy Policy and Terms of Service.

The public site at www.podu.dev sets no cookies at all.

There are no analytics, advertising or tracking cookies, so there is no cookie banner. You can block cookies in your browser, but then you cannot sign in, and the claim and report forms will not work.

Your rights

Under the GDPR, the UK GDPR, Bangladesh’s personal data protection law and similar laws, you can ask us to:

  • give you a copy of your data (access);
  • correct it;
  • delete it;
  • restrict how we use it, or object to our use based on legitimate interests;
  • export your pods in a machine-readable format (portability).

Which of these rights you have depends on the law that applies to you. Email privacy@podu.dev from the address on your GitHub account. Requests are free of charge. We may ask you to confirm your identity, so we can tell the request is yours. We answer within 30 days. Some data we may need to keep, for example a suspended pod held as evidence. If so, we tell you why.

You can also delete your data yourself. In My Pods, delete your pods first: a pod that was taken down can’t be deleted by its owner. With no pods left, choose Delete my account and type your GitHub username. Your account and your open requests are deleted at once. A banned account can’t be deleted this way, so that a ban can’t be avoided by signing up again: write to privacy@podu.dev instead, as you can for a taken-down pod.

You can also complain to a data protection authority, for example the one where you live.

Security

All traffic to Podu uses HTTPS. Podu stores only a keyed hash of IP addresses, never the raw address. No system is perfectly secure. If a personal data breach affects you, we will tell you and the relevant authorities where the law requires. If you find a problem, see our Security policy.

Age

Podu is not for anyone under 16. If you believe someone under 16 is using Podu, tell us at privacy@podu.dev and we will delete their account and pods.

Changes to this policy

We will post changes on this page at least 14 days before they apply, and email you about material changes, unless a change is needed urgently for legal or security reasons.