PyfinexusCRM Sign in

Privacy

Last updated 14 November 2026

This page says, in plain words, what this CRM keeps about the people and businesses we work with, who can see it, and exactly which outside services receive any of it. It describes how the software really behaves, including the places where our protections have limits.

Who runs this

This CRM is run by Pyfinexus Technologies Private Limited for its own sales, support and marketing work. It is not a public service: only people we have added can sign in. Questions about your information go to [email protected].

What is stored

  • Accounts and contacts: business names, contact names, phone and WhatsApp numbers, emails, city, industry, GSTIN, and which product or plan they use.
  • History: calls, meetings and messages we log on each client's product timelines, subscriptions and trials, renewal dates, tasks and follow-ups, and free-text notes.
  • Files and marketing material: images and videos we upload, posts and campaigns, and the knowledge documents the team writes.
  • Team data: staff logins (a hashed password, never the password itself), roles, and an audit log of who changed what.
  • Phone app notifications: short alerts addressed to one person (for example a new lead, a task assigned to them or a meeting reminder), which may contain a client or lead name or an event title.
  • Assistant data: Nexa and Rex chat history, saved memories, and a log of the tools they used.
  • Leads from our websites: the details someone typed into a sign-up, waitlist or demo form, with where they came from.

Who can see it inside the CRM

  • The MD and managers see every account. Employees see only the accounts they own or work on.
  • Each person's own to-dos, calendar, ideas and notes are private to them. Not even the MD sees them in the CRM. (They are still sent to the AI provider when you ask Nexa to plan your day or read your list. See below.)
  • Only the MD sees the team list and audit log. Pending accounts see nothing until approved.

Outside services, and what each one receives

Anthropic (the AI behind Nexa and Rex)

Used only for people we have switched the assistant on for, and only when they use it (and for the optional morning plan). Before anything is sent, every client is replaced by a made-up nickname, and phone numbers, emails and GSTINs are replaced by placeholders. Anthropic therefore sees the product, the history, the subscription amounts and end dates and what was said, but not the client's name, phone number or email.

Also sent: the signed-in employee's own name and the names of colleagues who own accounts or tasks, our product and price information, goals, and the knowledge documents the assistant looks up.

Anthropic handles that data under its own terms and privacy policy.

Voyage AI (optional knowledge search)

Only if a Voyage key has been set up. The title and text of knowledge documents, and the words used to search them, are sent to turn them into search vectors. Client records are not sent, but nothing scrubs these documents, so they should hold company material only.

Instagram / Meta

Only if Instagram is connected. Meta receives the posts we publish (caption, image or video) and the access token that lets us publish, and returns post statistics. Meta downloads the images from our server's public address. No client records are sent.

Email (our SMTP provider)

If email is set up, the service that carries our mail sees whatever the email contains. The optional morning digest, when switched on, is sent to each employee's own address and lists their tasks with the real client names. This is not scrubbed because it goes to the employee, not to an AI.

Phone app notifications (no outside service)

The Android app's alerts are not sent through Google or any other push service. The CRM server creates each notification as a row in its own database and keeps it for the retention period below. The app fetches new ones directly from the CRM every ~15 minutes and shows them on the phone, so nothing about them reaches an outside company. A notification's text can include client or lead names and calendar event titles, and it appears on the phone's lock screen according to the phone's own notification settings.

We do not use advertising or analytics trackers. Pages load fonts, icons and scripts from our own server.

Where our protections have limits

The nickname system is a safety net with limits, so please read these:

  • Names the CRM does not know. It can only swap names it has stored. A new lead typed into the chat, or a name inside a note or message that is not yet a contact, is sent as typed. The same goes for different spellings, short or shared first names, and relatives or other people mentioned in free text.
  • Numbers and IDs it does not recognise. Indian mobile numbers, emails and GSTINs are caught. Landlines, foreign numbers, PAN, Aadhaar, bank details and street addresses typed into free text are not.
  • Business facts are sent as they are. City, industry, product and service names, amounts, dates and what a client wants all reach the AI. A log summary that contains a name the CRM does not know goes through unchanged.
  • Staff names. Employees' own names are not hidden from the AI.
  • Private items. Your private to-dos, calendar and ideas are private from other people, but if you ask Nexa to plan your day or read them, their text is sent to the AI provider, with the same name-swapping applied.
  • The AI's drafts. What the AI writes back is translated to real names only for the person reading it.

How long we keep it

CRM records stay until someone with access deletes them or you ask us to. The assistant's tool logs, saved briefings and phone-app notifications are deleted automatically after 90 days. Chat history, the audit log and database backups are kept until removed. Backups hold all CRM data, so a deleted record can remain in an older backup until that backup is rotated out.

How it is protected

  • Every page needs a sign-in, and staff can only open what their role allows. Wrong-password guessing is limited.
  • The site runs over HTTPS with secure cookies and a strict content policy. Secrets such as API keys live only on the server and are never shown on screen.
  • Staff can switch on two-step login with an authenticator app under More, then Security.
  • Changes to client data are written to an audit log.

Seeing, correcting or deleting your information

Write to [email protected] from the address we have for you. Tell us who you are and what you want: a copy of what we hold, a correction, or deletion. We will check it is really you, and reply. Deleting a record removes it from the CRM; it also stops it being sent to the services above. We cannot recall what an outside service has already received. Each of them keeps data under its own terms.

© 2026 Pyfinexus Technologies Private Limited