Legal

Privacy policy

Last updated: 8 November 2026

This policy explains how TapX (“we”, “us”) collects, uses, discloses and protects personal data when you use tapx.sg, the TapX web app at app.tapx.sg, the TapX mobile app, or a TapX card, in line with Singapore’s Personal Data Protection Act 2012 (PDPA).

What we collect

Early-access, demo and order requests on tapx.sg: your name, email, company, team size, phone number (if given), profession, and the plan, card or CRM you mention. If you join early access from a TapX card you were given, the code of that card, so we can link it to your account.
Your consent choices: whether you agreed to be contacted about your request, and whether you opted in to product updates, with the date and time.
TapX accounts: when you become a member, your sign-in email, your profile (name, job title, company, short bio, photo, the links you add), how you sign in (an emailed code, a password you set, or your Google or Apple account), and the cards linked to you.
Signing in with Google or Apple: if you connect one, we receive that account’s ID and email, and your name when the provider sends it. Google also sends the address of your profile picture. We use these only to sign you in and to show you which account is connected. If you connect Apple and choose to hide your email, we receive the private address Apple makes for you instead of your own. We keep sending TapX emails to your sign-in email. When you connect Apple, we may also keep a key from Apple. We use it only to ask Apple to disconnect TapX when you disconnect Apple or delete your account.
Leads shared with a member: when someone taps a member’s card and fills in the “share my details” form, we store what they type (name, mobile number, email, company, note), the consent wording they were shown and when they agreed. We hold this on the member’s behalf so they can follow up. The member can also give the lead a stage (New, Contacted, Meeting, Won or Lost) and set a reminder date; we keep these with the lead, use the reminder only to remind the member, and don’t send either to the tools a member connects. If the member has connected a tool such as Google Sheets, we also send the lead to the member’s own account there, or to a web address the member gave us, on the member’s instruction.
Tools a member connects: if a member connects Google Sheets, we keep which tool, the email of the Google account they connected (until they disconnect), the address of the sheet we made for them, a key that lets us add to it (stored encrypted), the dates they connected and disconnected, and, for each lead, whether and when it reached the sheet. We use the Google account’s email only to show the member which account is connected. For Google Sheets, TapX can see only the files it made itself. If a member connects HubSpot, we keep which tool, the id and web address of their HubSpot account, and, until they disconnect, its domain and the email and owner id of the HubSpot user who connected, a key that lets us add to it (stored encrypted), the dates they connected and disconnected, and, for each lead, whether and when it reached HubSpot, with the ids of the contact and the note we wrote. We use that user’s email only to show the member which account is connected and to find their owner id. If a member uses Zapier, we keep a scrambled copy of each TapX key they make, which can’t be turned back into the key (never the key itself), with its last four characters and when it was made, last used and revoked. For each Zap that gets their leads, we keep which key turned it on, the web address Zapier gave us for it (stored encrypted), whether it gets new leads or changes, and the dates it started and stopped. For each lead, we keep whether and when it reached each Zap. If a member gives us a webhook address, we keep that address and the secret that signs what we send there (both stored encrypted), the name of the server in that address, the dates they added and removed it, and, for each lead, whether and when it reached the address. We don’t receive the member’s Zapier password, and we don’t copy anything from their Zapier account into TapX. Zapier’s developer pages show TapX, as the developer of its app on Zapier, a log of the app’s requests, which may name the Zapier account that made them.
Photos, videos and files on a profile: the pictures and documents a member adds to their profile, and the video links they choose to show. Location and camera details are removed from photos before they are stored.
TapX teams: if your company has a TapX team, its admin chooses how your profile looks and the company name on it, and can see your name and whether your profile is live. They cannot see your leads.
Reports about a profile: if you report a profile, we keep what you wrote and, if you gave it, your email address, so we can look into the report and reply to you. We don’t share either with the profile’s owner.
Blocked senders: if a member blocks someone who shared their details with them, we keep a scrambled form of that person’s email and mobile number, so their details don’t reach that member again. It is made with a secret key that only TapX holds, so it can’t be turned back into the email or number without that key. So the member can see whom they blocked, we also keep the name the person gave and a short hint, such as j***@gmail.com or the last digits of the number.
Wallet passes: if you add your TapX card to Apple Wallet or Google Wallet, a record of the pass and the token Wallet uses to check for updates.
The TapX mobile app: if you allow notifications, the phone’s notification token, so we can send you a “new lead” alert and the reminders you set on your leads. A new-lead alert carries the lead’s name, company and the first line of their note; a reminder carries the name and company of the lead that is due, or how many are due with the first few names. Neither carries their phone number or email. “Save to phone” opens your phone’s own contacts form and sends nothing to our servers.
Card taps: when someone taps a TapX card or stand, we record the time, and the city and country that their internet connection points to, so its owner can see how often and where it is tapped. The record holds no IP address and nothing that names the person who tapped.
Cookies: app.tapx.sg and the TapX app use cookies to keep you signed in. When a member connects a tool such as Google Sheets, a cookie that lasts 10 minutes checks that the tool’s answer comes back to the member who asked. When a member presses Send a test for a webhook address, a cookie that lasts one minute carries the answer to the next page. We don’t use tracking cookies.

Why we use it

To reply to your request, send your early-access invite, or fulfil an order.
To run your TapX account: show your profile when your card is tapped, deliver leads to you, and sign you in.
To send product updates, but only if you ticked the optional updates box.
To alert you to a new lead by email and, if you allowed it, by notification in the app.
To remind you about a lead on the day you chose, by email and, if you allowed it, by notification in the app.
To send leads on to a tool the member connected, when they ask us to: each new lead who agreed to be contacted; once, if the member chooses, up to 500 earlier leads who agreed, to Google Sheets or HubSpot; and, to a Zap that asks for changes instead, the member’s later changes to such a lead.
To look into reports about a profile.
To show the owner of a card or stand how often, and roughly where, it is tapped.

Who we share it with

We don’t sell personal data. We use trusted service providers, who process data only on our instructions: Supabase (database and sign-in, hosted in Singapore), Cloudflare (hosting), Resend (email), Google and Apple (wallet passes, and “Continue with Google” or “Continue with Apple” if you use them), and Expo (app notifications). Some providers may store data outside Singapore, and where they do, we require protection comparable to the PDPA. A member sees the leads shared with them and can send them on to tools they connect; TapX staff can see leads only to run the service and help with a request.

Tools a member connects. A member can connect Google Sheets and, as TapX opens each one to them, HubSpot, Zapier and a webhook address of their own choosing. When a member connects Google Sheets, we send each new lead who agreed to be contacted to a sheet in the member’s own Google account, on the member’s instruction and as their data intermediary, and once, if the member chooses, up to 500 of their earlier leads who agreed. Google then holds that data under the member’s account and its own terms, which may be outside Singapore. While the member is connected, TapX can open only the sheet it made: to make it, to add rows to its first tab (the Leads tab TapX made, as long as the member keeps it first), to check that the sheet is still there and not in the bin, and, so that no lead is added twice, to read back the column on that tab where TapX puts each lead’s link. TapX doesn’t read or change anything else in the sheet, and doesn’t take leads back out of it. The member can disconnect at any time: TapX then deletes its key and can no longer reach the sheet, and what was already sent stays where they sent it.

HubSpot. When a member connects HubSpot, we send each new lead who agreed to be contacted to the member’s own HubSpot account, on the member’s instruction and as their data intermediary, and once, if the member chooses, up to 500 of their earlier leads who agreed. HubSpot then holds that data under the member’s account and its own terms, which may be outside Singapore. HubSpot gives an app like TapX access to all the contacts in that HubSpot account, not only the member’s; TapX uses it only for the member’s own leads. For each lead, TapX looks up whether the person is already a contact, by email or, without an email, by phone number. If they are, TapX reads that contact’s name, phone numbers, company, owner, lifecycle stage and TapX marketing consent field only to see which are empty, and fills in only those; it never changes what is there, except that a no about marketing updates is always recorded in the TapX marketing consent field. If they aren’t, TapX creates the contact. TapX then adds one note to the contact (if a try is cut off, TapX looks only for that same note before trying again, so it is added once) and sets a yes/no field, TapX marketing consent, which it adds to the account once (and again if it is deleted for good): on a contact TapX creates, to the person’s answer about marketing updates; on a contact that was already there, only to record a no or to fill the field while it is empty, so a yes typed into TapX’s form never replaces a no. When the member connects, TapX reads the account’s id, web address and domain, the email of the HubSpot user who connected, and, from the account’s list of users, that user’s owner id, so that what TapX adds can be assigned to them. TapX uses nothing else from HubSpot, and keeps nothing it reads there beyond those details of the account and the user and the ids of the contacts and notes it wrote. TapX doesn’t take leads back out of HubSpot. The member can disconnect at any time: TapX then deletes its own copy of the key and, where it can, asks HubSpot to cancel it, and can no longer reach the account through that member’s connection. TapX stays installed in the HubSpot account, where others there may use it, until an admin uninstalls it there, under Settings, Integrations, Connected Apps; what was already sent stays where they sent it.

Zapier and webhook addresses. To use Zapier, a member makes a TapX key in Settings and pastes it into their own Zapier account. Zapier checks the key with TapX, and TapX answers with the member’s name, profile address and profile id, so Zapier can name the connection after them. Each Zap the member then turns on gives TapX a web address at Zapier and asks for one of two things. A Zap for new leads gets each new lead who agreed to be contacted, sent on the member’s instruction and as their data intermediary: the time, what the person shared, both consent answers, the consent wording they saw and when they agreed, which card or page the lead came from and the event, the member’s name and profile address, and a link to the lead in TapX. A Zap for changes gets no new leads: each time the member marks a lead who agreed to be contacted followed up or not, moves it to or out of an event, or changes their own private note on it, that Zap gets the lead with the same details, plus whether and when the member followed up, that private note, and when the change was made. A member can also give TapX a webhook address of their own choosing, such as one from Make or n8n or their company’s own system. TapX sends each new lead who agreed to be contacted there, with the same details a Zap for new leads gets, signed with a secret that TapX shows the member once, so that their system can check it came from TapX. TapX doesn’t send earlier leads to a Zap or a webhook address, except that a Zap for changes gets a lead the member already had when they change it. From there, the member chooses where their leads go: Zapier and the tools each Zap passes them on to, or whoever runs the webhook address, then hold that data under the member’s accounts and their own terms, which may be outside Singapore. TapX doesn’t follow what happens to a lead once it is sent, and doesn’t take leads back. Zapier keeps a technical log of the requests that TapX’s app on Zapier makes and receives, which TapX can open to find and fix a fault, and which may include the details of a lead. Anyone who holds a member’s key can get their new leads, and their later changes with their private notes, through their own Zapier account until the member revokes it, so TapX shows each key only once and keeps only a scrambled copy. The member can stop at any time: turning a Zap off in Zapier stops that Zap; revoking a key in Settings stops every Zap turned on with it, at once; removing the webhook address stops it, and TapX deletes the address and its secret. Deleting their TapX account does all of this at once. Download my data in Settings lists the member’s keys, Zaps and webhook address, but never a key, a Zap’s address, the full webhook address or its secret. What was already sent stays where it was sent.

A member can show a video from YouTube, Vimeo, TikTok or Instagram (Meta) on their profile. Nothing is loaded from those services until you tap play. When you do, the video comes from that service, which then receives your IP address and may set its own cookies under its own privacy policy.

How long we keep it

Requests from tapx.sg: for as long as needed to respond and to run early access, then deleted, or earlier when you ask.
Your account and profile: until you delete your account or ask us to.
Leads shared with you: while your account exists, or until you delete them.
Photos and files on your profile: until you remove them or delete your account.
The key from Apple: until Apple is disconnected or your account is deleted.
Keys for tools you connect: until you disconnect them or delete your account.
A scrambled copy of each TapX key you make for Zapier, with its last four characters and its dates: until you delete your account. A key you revoke stops working at once.
The address of each Zap, and your webhook address with its secret: until the Zap is turned off, you revoke the key it was turned on with, you remove the address (or it tells us it no longer exists), or you delete your account.
The email of the Google account or HubSpot user you connected, and your HubSpot account’s domain and that user’s owner id: until you disconnect the tool or delete your account.
A record that you connected and disconnected a tool, with the dates, and the address of the sheet we made (so connecting again uses the same sheet), the id and web address of your HubSpot account, which of your keys turned a Zap on and what the Zap gets, or the name of the server in your webhook address: until you delete your account.
Whether each lead reached a tool you connected, and in HubSpot the ids of the contact and note we wrote: as long as the lead.
Notification tokens: deleted when you sign out of the app, when your account is deleted, or after 60 days unused.
Reports: we delete your email address 90 days after the report is closed. We keep the rest of the report as a record of what we decided.
Blocked senders: until the member unblocks them or deletes their account.
Take-downs: if we take something down on your profile, we keep a record of what and why until you delete your account. Our staff log keeps that we acted, with no name or email.
Order and invoice records: at least five years, as Singapore’s tax rules require, even after an account is deleted.
When an account is deleted: we keep one line in our staff log that a deletion happened, with no name or email, and your card codes stay switched off so a printed card never opens to a stranger.

Your choices and rights

Withdraw consent or unsubscribe from updates at any time.
Ask to access or correct the personal data we hold about you.
Ask us to delete your data. Members can also download their data and delete their account themselves, from Settings in the app.
If you shared your details with a member and want them removed, ask the member or email us and we will help. If the member sent your details to a tool they connected (such as Google Sheets), removing them there is the member’s to do; we will tell them.

Email hello@tapx.sg and we’ll respond within 30 days.

Data Protection Officer

Questions or complaints about how we handle personal data can be sent to our Data Protection Officer at hello@tapx.sg.

Changes

We’ll update this page if our practices change, and show the date of the latest update above.