TAPACONTACT
Contact TapAContact
Use the appropriate TapAContact channel for sales, product support, billing, security or privacy questions. Providing the relevant account, organisation and page details helps the team route an enquiry without asking for passwords, full payment-card details or other unnecessary sensitive information.
Product and sales enquiries
Professionals comparing digital business cards can review the personal product page and pricing information before contacting the team. Organisations planning a team rollout, event programme or CRM workflow should use the enterprise enquiry form. Include the approximate team size, intended countries, expected use case and desired launch window. These details make an initial conversation more useful and do not commit the organisation to a purchase.
For an event or field-marketing project, explain how many staff members, booths or locations will use NFC or QR touchpoints and what should happen after a visitor engages. TapAContact can then assess profile setup, attribution, consent language and export or integration requirements. Avoid sending real customer lists during an initial enquiry.
Account, billing and technical support
For account support, include the email address associated with the account, the organisation name if applicable, the affected page URL and a concise description of what happened. Screenshots are useful when they do not reveal passwords, one-time codes, private keys or full payment details. For billing questions, provide the TapAContact order number or invoice reference rather than complete bank or card information.
Technical reports should include the device type, browser version, approximate time of the issue and steps that reproduce it. If an NFC card opens the wrong destination, include the public URL or activation code printed for the card. The team may request additional diagnostic information through an authenticated channel after the initial report is reviewed.
Privacy and security requests
A person may contact TapAContact about access, correction, deletion, restriction, portability or objection rights where applicable. Enterprise-managed users may need to contact their organisation first because that organisation can control the relevant profile or lead data. TapAContact may verify identity before acting on a request so that information is not disclosed to an unauthorised person.
Potential security issues should be reported privately and should include enough detail to reproduce the concern safely. Do not access another person’s data, disrupt the service or publish sensitive evidence. A responsible report will be acknowledged and routed for assessment. Response and resolution times depend on severity, reproducibility and any third-party service involved.
Which contact route should I use?
| Need | Recommended route | Helpful information |
|---|---|---|
| Personal product question | service@tapacontact.com | Use case and country |
| Enterprise or event project | Enterprise enquiry form | Team size, locations and timing |
| Billing support | Authenticated support request | Order or invoice reference |
| Privacy request | service@tapacontact.com | Account, organisation and request type |
Frequently asked questions
What should I include in a support request?
Include the account email, affected URL, device and browser, approximate time and reproducible steps.
Should I send my password or card number?
No. Never send passwords, one-time codes, private keys or a complete payment-card number.
How do I request an enterprise demonstration?
Use the enquiry form on the Products page and describe the team size, use case and intended launch window.