the information this site currently receives
What we collect, how personal Substack updates work, and how to request removal.
01what the email form sends
When you explicitly agree, we store your email, consent wording version and server-recorded consent time for personal opportunity updates from Manav via Substack. Manav and team handle the export and Substack workflow. This form does not send email or subscribe you on Substack. Deadline reminders are separate and optional (see 05).
After capture, you may add a first name, interests and a short note about what you are looking for. These are optional team context; leave out sensitive information. We also store selected shortlist preferences, the form source and approved channel/campaign categories. We do not store raw referral URLs or arbitrary tracking parameters with your signup. Profile updates use a one-time random token, valid for 30 minutes, held in this page's memory; only its hash is stored.
An earlier signup is not overwritten by a new form submission. Legacy interest-list records are kept separate and are not inferred to have consented to these updates. Browsing, the personalized shortlist and the deadline calendar work without an address.
02what review forms send
Listing submissions include the listing fields, direct URL and contact email entered in the form. Correction reports include the title, host, source or listing URL, correction detail and contact email.
Operators use those records to review, publish or reject a listing, check a correction and follow up when needed. A contact email is not published as part of a public listing.
03technical request data
The submission and email endpoints process network information such as an IP address to rate-limit abuse. Hosting and data infrastructure also process requests and stored records to operate the site.
Cloudflare Web Analytics measures aggregate visits and page performance without cookies or cross-site tracking. Cloudflare, which also hosts the site, receives technical request, browser and performance data under Cloudflare's privacy policy.
Some listings show the organizer's logo, loaded directly from the source platform's image server (for example Devfolio, Luma, MLH, Unstop, Eventbrite, HackerEarth or the host's own server). Your browser fetches it without a referrer, but that server receives your IP address and browser details, as with any image on the web.
When you click through to apply or register at a listing's source, the page sends one anonymous count: the listing and its section, the source site, and, if you arrived through one of our short /r/ links or a tagged campaign link, that link's code and its source and campaign tags. The code is kept in this browser tab's session storage until the tab closes. Following a /r/ link records the same kind of count.
These counts are stored in Cloudflare Workers Analytics Engine with no cookie, IP address, email, name or other identifier, and are used only to see which listings and channels bring applicants. Saving a listing, opening a calendar reminder link, pressing a share button and completing a signup each add the same kind of count: the action, the page's section and listing, and which button or form, never what you typed.
This notice does not claim a fixed legal retention period or a self-service privacy dashboard; neither is implemented today.
04leave the list or ask about a record
Use the unsubscribe link in any personal Substack update to stop those messages. Before receiving an update, or to remove site signup data, a submission contact or understand a record, email manav@tensorboy.com. Requests are handled manually, within 30 days. The team must reconcile Substack unsubscribes before each import. Site suppression removes the email and optional profile from the new capture table and keeps a hashed email marker to prevent re-import from a repeat signup. That marker is pseudonymous, not anonymous. Suppression does not itself change an existing Substack subscription; the team handles both systems.
For submission rules, read the terms.
05saved hackathons and calendar feeds
Saved hackathons stay in this browser's local storage. Opening your saved list or a calendar reminder feed sends those listing ids in the request, so the page can show the current dates; the ids are not tied to a name or email. Your calendar app fetches a subscribed feed on its own schedule.
Deadline reminders are optional browser notifications. If you turn them on, we store this browser's push address and the ids of the hackathons you save, nothing else: no name, email or account. Reminders reach you end-to-end encrypted through your browser maker's push service. Both are deleted when you turn reminders off, when your browser cancels the subscription, or 120 days after your last update.
Signing in is optional and uses your Google account. Supabase Auth stores the name, email address, profile picture URL and account id that Google shares with us, plus the ids of the hackathons you save. We use them only to keep you signed in, sync your saves across devices and tie your team posts to you so only you can withdraw them. Sign-in cookies do nothing else. We do not sell this data, use it for ads or share it beyond Cloudflare and Supabase, which run the site.
TensorHack's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Sign out on the shortlist page. To delete your account, email manav@tensorboy.com from the address you signed in with; within 30 days we delete the account, its saves and its team posts.
Team posts are optional too. A post on a hackathon's find-teammates board stores your roles, skills, timezone, note and the one profile link or Discord username you choose, with your account id so only you can withdraw it. Anyone can read the post, without your name or email, until the hackathon closes. A report stores the reporting account's id, so each person reports a post once.
Notice reviewed on .