Privacy Policy

What we collect

Three kinds of data, kept deliberately separate.

Sign-in identity. You sign in with Google. Google returns your name, email address and profile picture to our authentication provider (Supabase Auth), which holds your account record and issues your session. Our own application database has no email or phone column at all — it stores only the account identifier the auth provider gives it. Practically, this means an ordinary query against Junto's data cannot list your email address.

What you write. Your handle, display name, city, bio, skills, external links, profile photo and cover images, the projects and roles you post, your applications, your messages, and the agreements you sign. This is data you provide knowingly, and most of it is meant to be read by other people.

What the product records as you use it. Your swipes and saves, which projects you applied to and what was decided, your notifications, and — where you allow it — a precise home location (latitude and longitude) used to compute proximity, plus a device push token if you enable notifications on a phone.

What is public, and what is not

This is the section worth reading twice, because the split is not obvious from the interface.

• PUBLIC — your profile page at /u/your-handle: display name, handle, city, bio, skills, links, profile photo, and the projects and ventures you are part of. Anyone with the link can read it, signed in or not.
• PUBLIC — projects and roles you publish, including the equity or fee attached to each open seat, and the public venture pages you appear on.
• PRIVATE — your messages, your applications and their outcomes, your saved projects, your notifications, your payment records, and your project workspaces.
• PRIVATE AND INVISIBLE TO YOU — an internal reliability score derived from whether you follow through on what you commit to. It is used to order what people see. It is never returned by any API, so it is not shown to you or to anyone else, and it is not a credit score or a public rating.
• NEVER SHOWN TO THE PERSON IT IS ABOUT — a pass. If you swipe past someone or some project, that is not disclosed. Only a mutual decision opens a conversation.

Search engines, and how to say no

Public profiles are indexable by Google and other search engines by default, because being findable is the point of the product — a profile nobody can find does not get you a cofounder.

We also recognise that a real name, photograph, city and biography appearing in Google is a significant thing to do to a person, and that you may not want it. Every account has a discoverability setting. Turn it off and two things happen together: your profile page is served with a `noindex` directive, and it is removed from our sitemap so crawlers stop being pointed at it. The page stays reachable by direct link — turning off indexing is not the same as making the page private — and search engines can take days to weeks to drop a page they have already crawled.

If you want the page gone entirely rather than merely unindexed, delete your account.

Why we process it, and on what basis

Under the DPDP Act we process personal data on the basis of your consent, given when you create an account and when you enable a specific feature, and for the legitimate uses the Act permits — chiefly providing the service you asked for.

• To operate your account, authenticate you, and keep your session alive.
• To show you relevant people and projects — this is what location, skills and city are for.
• To deliver messages, applications and notifications between members.
• To record agreements, which requires retaining who signed what and when.
• To take payments where you buy something, and to reconcile them.
• To keep the platform safe: rate limits, abuse reports, moderation, and preventing fraud.
• To comply with law, and to establish or defend legal claims.

Who else processes your data

We do not sell your personal data, and we do not share it with advertisers. We do use service providers, each for one job:

• Supabase — database and authentication. Holds your account record, including the email address Google returns.
• Vercel — application hosting and delivery. Processes request metadata such as IP address in the ordinary course of serving pages.
• Cloudflare R2 — image storage for profile photos and project covers. Uploaded images are served from publicly addressable URLs; treat anything you upload as public.
• Razorpay — payment processing, where you pay for something. Card and bank details are entered with Razorpay and never reach our servers; we retain only the order and payment identifiers, the amount and the status.
• Mapbox — geocoding. When you type a location while setting up your profile, that text is sent to Mapbox to turn into coordinates.
• Expo — push notification delivery to mobile devices, if you enable notifications.
• Google — sign-in. Your use of Google Sign-In is also governed by Google’s own privacy policy.

What we do not do

We think the absences are as informative as the inclusions, so they are stated rather than omitted.

• Junto runs no third-party analytics, advertising or tracking scripts today. If that changes, this policy will be updated before it ships and the change will be disclosed here.
• We set no advertising cookies. The cookies we set are the ones that keep you signed in and the short-lived one that secures the sign-in exchange itself.
• Fonts are self-hosted at build time, so loading a page does not call out to a font provider.
• We do not read your private messages for advertising or model training.

Cross-border transfers

Our database is hosted in India (Mumbai). Some providers listed above operate globally and may process data — principally request metadata and delivery infrastructure — outside India. Where that happens we rely on the provider’s contractual protections. The DPDP Act permits transfers except to countries the Government of India restricts, and we will comply with any such restriction.

How long we keep it

Your profile and content stay for as long as your account exists.

Signed agreements are retained after account deletion. An agreement is a record of what two people committed to, and deleting one side of it would destroy the other party’s copy of their own arrangement. We keep the typed legal name, the signature hash, the terms and the timestamp — the minimum that keeps the record meaningful.

Payment records are retained as long as tax and accounting law requires.

Messages in a conversation persist for the other participant. Deleting your account removes your profile and unlinks you, but does not erase your side of someone else’s conversation history.

Backups roll off on their own schedule, so deletion is not instantaneous everywhere at once.

Your rights

Under the DPDP Act you may ask us to:

• Confirm what personal data we process about you, and get a summary of it.
• Correct anything inaccurate, or complete anything incomplete — most of this you can do yourself from your account page.
• Erase your personal data, subject to the retention exceptions above.
• Withdraw consent, including by deleting your account. Withdrawal does not undo processing already carried out.
• Nominate someone to exercise these rights on your behalf if you die or become incapacitated.

Children

Junto is not for anyone under 18. We do not knowingly process the data of a child, and we will delete an account we learn belongs to one. If you believe a minor has an account, tell us at grievance@letsjunto.com.

Security

Data is encrypted in transit. Access to production data is restricted. Sessions are cookie-based and scoped to the site. Passwords are not something we hold at all, because sign-in is delegated to Google.

No system is perfectly secure. If a breach occurs that is likely to affect you, we will notify you and the Data Protection Board as the DPDP Act requires.

Grievance Officer

Write to grievance@letsjunto.com and we will acknowledge within 72 hours and respond substantively within 30 days. For anything else about your data — access, correction, erasure, nomination — privacy@letsjunto.com reaches the same team.

Junto, Hyderabad, Telangana, India.

If you are not satisfied with our response, you may complain to the Data Protection Board of India.

Changes

We will update this page when the product changes, and change the date at the top. Material changes will be signalled in the product rather than left to be discovered.