Privacy

Pairon is not registered as a company. The stated operator country is India. The responsible person’s legal name has not been supplied for publication. A serviceable postal address has not been supplied for publication. This notice does not yet identify its data controller completely.

Published operator

Not provided

Postal address

Not provided

Country

India

Privacy contact

contact@pairon.dev

Grievance contact

contact@pairon.dev

This notice was updated on 28 September 2026. It covers the Pairon public website and beta access request. Product use after sign-in also involves account and collaboration data; see Security. The service provider list, data locations and retention schedule still need to be confirmed before a wider launch.

The beta form sends only your email address, your confirmation that you are at least 18, the privacy notice version shown to you, and the server time when you agreed. Name, role, team size and free text are no longer requested for new entries. Older waitlist records may still contain those fields until they are removed.

We use the email to handle your beta request and send the related access message. These are service messages, not a marketing subscription. No newsletter or promotional email is currently sent.

Optional site analytics is off until you allow it in the consent banner. If allowed, the site sends page paths and selected button or demo events to Pairon’s first-party API. A new beta request may add a coarse count with no email address or visit id. Other events may include a random tab visit id, the referring site hostname, UTM campaign fields and a fixed interaction label. We do not send form contents, page query strings, prompts or repository files. The browser’s IP address is used for API abuse limits and is not included in the analytics event row.

The site has no third-party analytics SDK, advertising pixel, iframe or embedded social player. Product videos and posters are served from Pairon’s own site. Sign-in buttons open Google or GitHub on the separate app; those services have their own privacy terms. The site’s fonts are bundled with the build.

If you use the beta product, account data includes your email, display name and sign-in identity. Password accounts store a password hash, not the password itself. Google or GitHub may provide profile details such as a name or avatar when you choose that sign-in method. Pairon also stores collaboration records such as chat, instructions, agent replies and tool names. File contents and terminal output are relayed to conversation members; a stored diff event keeps file paths and line counts. Optional recovery, code graph and memory uploads remain off unless the project setting and computer owner allow them. Details and limits are on the Security page.

The backend also records limited account-linked milestones such as account creation, invite-code redemption and onboarding start to measure product use. The sign-up page view is not recorded. Resend sends transactional access and account messages. The product uses a managed PostgreSQL database; exact hosting and database providers, processing locations, and any international transfer safeguards still need to be confirmed and published before the service opens more broadly. If you sign in with Google or GitHub, those providers process data under their own terms.

A browser setting remembers your analytics choice for up to 180 days. The random tab visit id and duplicate-event markers are held in session storage while analytics is allowed; rejecting or withdrawing analytics clears them where browser storage permits. See the Cookie and tracking policy.

The beta waitlist and analytics event records, including account-linked milestone rows, do not currently have an automatic expiry job. A verified deletion request is handled manually, and data may remain in backups for their ordinary backup cycle. Pairon needs a documented retention period and a working deletion process before wider launch. No fixed deletion deadline is promised here.

• Reject optional analytics in the banner or change your choice at any time from Cookie settings. Do Not Track and Global Privacy Control keep analytics off.
• To withdraw a beta request or ask for access, correction or deletion of waitlist information, email contact@pairon.dev from the address on the request. We may ask you to verify control of that address.
• For an account or product data request, contact the same address and identify the account. The product does not yet have a self-service privacy-request workflow.
• Depending on where you live, local law may give you additional rights, such as objection, portability, restriction or a right to complain to a regulator.

The beta request form is limited to people aged 18 or older. Do not submit a child’s personal information. If you believe a child’s information was sent to Pairon, contact us so it can be reviewed and removed.

The operator has identified India as its country. Intended customer regions have not been supplied, and the operator’s legal name and postal address are still missing, so this notice does not claim that one country’s law governs every visitor. The current site uses opt-in analytics to avoid relying on an opt-out model for browser storage.