Pulsar remembers the people and meetings you chose to keep. The formal notice below is what we process, not a certification.
Navidad Infotech Pvt. Ltd. operates Pulsar Cards. Contact contact@pulsar.cards. Hardware is quoted by the same operator — there is no public shop.
When you store notes about people you met, you are the controller of that book. Pulsar hosts it on your instructions.
This notice covers pulsar.cards, the Pulsar mobile app, public profiles, exchange, the contact book, team workspaces, privacy tickets, invoices we issue, and hardware enquiries we take by email. It does not cover WhatsApp, Zoom, Teams, or Meet.
We collect only what the product needs to run the surfaces you use.
We use personal data to create and secure your account, host the public card you publish, run exchange and follow-up offers you start, keep your book, apply team brand rules, issue invoices, detect abuse, and respond to rights tickets. We do not sell personal data. We do not build a stranger-who-glanced dossier.
The following is our current operating view. It is not a signed lawful-basis register and not a GDPR or DPDP certificate. Counsel should confirm bases for a given deployment.
We do not sell lists. We use processors to host and send transactional mail. People you share a card with see what you published.
Owner dashboards show aggregates. Identity-linked activity appears only when the other person exchanged, inquired, or tapped while signed in and the action is meant to notify you. We do not show “opened 19 times from this city on this phone.” Raw analytics events default to a 30-day retention (minimum 7, maximum 365).
See the cookie notice. Strictly necessary cookies run the session. Measurement loads only if operations set a Google Analytics ID.
Account data stays until you close the account or we must keep a subset for law, dispute, or security. Nightly jobs expire analytics events, login attempts, used reset codes, revoked tokens, and old audit rows. A litigation hold is not implemented in product. Export and erase are available to the signed-in owner in Settings.
Depending on where you live, you may ask for access, correction, erasure, restriction, portability, objection, withdrawal of consent, nomination, or a grievance. India DPDP and EU GDPR list those families. Use the privacy request (30-day clock) or Settings export and close.
Completing a ticket does not automatically export or erase. We will verify the requester before we act. We may refuse a request that the law allows us to refuse, and we will say why.
Operations has recorded hosting as: Operator-declared DigitalOcean Droplet. Mailgun may process transactional addresses outside your country. We do not claim EU-US Data Privacy Framework participation unless operations turns that flag on in the Trust Center. Counsel must name the transfer mechanism that applies to a given customer. The DPA draft is not execution.
Signup requires confirmation that you are 18 or older. Organisation-provisioned accounts are not age-gated in product. If you believe a child created an account, write to contact@pulsar.cards.
Rate limits, captcha, and honeypots are automated abuse controls. They do not produce a legal or similarly significant decision about you as a person. No cloud model writes a relationship note.
Passwords are hashed. Sessions are HttpOnly. Uploads are re-encoded. Transit is HTTPS. This is not a Type II audit report and not “bank-grade” advertising.
A DPDP grievance officer has not been appointed in product settings. Use contact@pulsar.cards or the privacy request until operations records a named officer. We will not invent a name on this page.
A data protection officer has not been published in product settings.
We will post updates on this page and change the effective date. Material changes that need a new consent will be asked at the point of use.
Navidad Infotech Pvt. Ltd.. contact@pulsar.cards. Privacy request. Terms of Use.
Rights tickets take 30 days. Hardware questions go to contact@pulsar.cards.
Effective 12 September 2026 · Version 2026-09-12. This is the operator notice. It is not a certificate.
Navidad Infotech Pvt. Ltd. operates Pulsar Cards. Contact contact@pulsar.cards. Hardware is quoted by the same operator — there is no public shop.
When you store notes about people you met, you are the controller of that book. Pulsar hosts it on your instructions.
This notice covers pulsar.cards, the Pulsar mobile app, public profiles, exchange, the contact book, team workspaces, privacy tickets, invoices we issue, and hardware enquiries we take by email. It does not cover WhatsApp, Zoom, Teams, or Meet.
We collect only what the product needs to run the surfaces you use.
We use personal data to create and secure your account, host the public card you publish, run exchange and follow-up offers you start, keep your book, apply team brand rules, issue invoices, detect abuse, and respond to rights tickets. We do not sell personal data. We do not build a stranger-who-glanced dossier.
The following is our current operating view. It is not a signed lawful-basis register and not a GDPR or DPDP certificate. Counsel should confirm bases for a given deployment.
We do not sell lists. We use processors to host and send transactional mail. People you share a card with see what you published.
Owner dashboards show aggregates. Identity-linked activity appears only when the other person exchanged, inquired, or tapped while signed in and the action is meant to notify you. We do not show “opened 19 times from this city on this phone.” Raw analytics events default to a 30-day retention (minimum 7, maximum 365).
See the cookie notice. Strictly necessary cookies run the session. Measurement loads only if operations set a Google Analytics ID.
Account data stays until you close the account or we must keep a subset for law, dispute, or security. Nightly jobs expire analytics events, login attempts, used reset codes, revoked tokens, and old audit rows. A litigation hold is not implemented in product. Export and erase are available to the signed-in owner in Settings.
Depending on where you live, you may ask for access, correction, erasure, restriction, portability, objection, withdrawal of consent, nomination, or a grievance. India DPDP and EU GDPR list those families. Use the privacy request (30-day clock) or Settings export and close.
Completing a ticket does not automatically export or erase. We will verify the requester before we act. We may refuse a request that the law allows us to refuse, and we will say why.
Operations has recorded hosting as: Operator-declared DigitalOcean Droplet. Mailgun may process transactional addresses outside your country. We do not claim EU-US Data Privacy Framework participation unless operations turns that flag on in the Trust Center. Counsel must name the transfer mechanism that applies to a given customer. The DPA draft is not execution.
Signup requires confirmation that you are 18 or older. Organisation-provisioned accounts are not age-gated in product. If you believe a child created an account, write to contact@pulsar.cards.
Rate limits, captcha, and honeypots are automated abuse controls. They do not produce a legal or similarly significant decision about you as a person. No cloud model writes a relationship note.
Passwords are hashed. Sessions are HttpOnly. Uploads are re-encoded. Transit is HTTPS. This is not a Type II audit report and not “bank-grade” advertising.
A DPDP grievance officer has not been appointed in product settings. Use contact@pulsar.cards or the privacy request until operations records a named officer. We will not invent a name on this page.
A data protection officer has not been published in product settings.
We will post updates on this page and change the effective date. Material changes that need a new consent will be asked at the point of use.
Navidad Infotech Pvt. Ltd.. contact@pulsar.cards. Privacy request. Terms of Use.
