Privacy Notice

Who operates ProtoxTap

ProtoxTap is the trading name of Kaizan Coverley, an individual business operator. ProtoxTap is not an incorporated limited company. The operator is responsible for deciding why and how personal information is used for the purposes described in this notice.

For a privacy request or question, email protoxbusinesses@gmail.com or call 07923 910153. Please say what information or account your request concerns; do not send passwords or session tokens.

Information handled

Business and enquiry records

The administration database can hold a business name, contact name, email address, phone number, administrator-entered notes and a Google Place ID. The public website has no order form, customer account or automated checkout. If you contact the operator, your email or phone service will also handle the message you send.

Cards and tap events

For each card, the database stores its card code, associated business record, configured redirect URL, status and creation, activation and deactivation times. Card events store a card identifier, event type and timestamp, including a tap event for an active card. The tap-event table does not store a visitor's name, email address, IP address, precise location or device fingerprint. An active card's event is recorded before the browser is redirected; an inactive card is sent to the inactive-card page.

Administrator accounts, sessions and audit records

Administrator records contain a username and a password hash. Passwords are hashed with scrypt and a random salt; the password itself is not stored by this application. A successful sign-in creates a random session token. The browser holds that token in the protoxtap_session cookie, while the database stores a hash of the token, the administrator ID, creation time and expiry time. Sessions expire after seven days; expired database records are removed when the application checks them. Signing out removes a valid session from the database and expires the cookie.

Administrative audit records are stored for selected card actions. They can contain the administrator ID, action, target type and ID, card code or other target label, event time and action-specific details such as a business ID or name. These records are distinct from temporary diagnostic logs and are not routinely deleted by the application.

Technical request information

The tap-event database does not record visitor IP addresses or browser details. The active Express application does not log request URLs, request bodies or cookie values; its console output is limited to startup and generic operation-failure messages. Like other internet services, the hosting provider, reverse proxy or network infrastructure may process IP addresses, request paths, timestamps and technical headers to deliver and secure requests. The application and server configuration in this project do not identify those providers or establish their logging and retention settings.

Purposes and lawful bases

• Business contact and enquiry information is used to respond to requests and discuss service suitability. Depending on the circumstances, the basis may be steps requested before a contract or legitimate interests in responding to business enquiries.
• Business, card and destination configuration is used to provide an agreed service. The likely basis is contract where the information relates to the contracting individual; contact details for staff at a business may instead rely on legitimate interests.
• Tap and card-lifecycle events are used to operate the redirect service, investigate service issues and maintain service history. The basis may be performance of the service agreement and, where appropriate, legitimate interests in operating and protecting the service.
• Administrator account, session and audit information is used to restrict and review access to the administration system. The likely basis is legitimate interests in secure administration and, where relevant, a legal obligation.
• Information may also be used where necessary to meet a legal obligation or establish, exercise or defend legal claims.

The operator has not documented a legitimate-interests assessment. The precise lawful basis and whether ProtoxTap acts as controller or processor for each category of a business customer's information must be confirmed for the actual service and contract.

Service providers and destinations

The application connects to a PostgreSQL database using a DATABASE_URL setting. The database host, provider, processing location, contract and backup arrangements are not identified in this project. The website hosting, reverse proxy and their data-processing terms also need to be confirmed by the operator.

When an administrator creates or updates a business, the backend sends the business name in a search request to Google's Places API to obtain a Place ID. The code does not send card tap events to that API. When a customer taps an active card configured for a Google review destination, the customer's browser is redirected to Google; Google receives the resulting request directly from the customer's device and handles it under its own privacy information. The ProtoxTap public pages do not embed a Google interface.

The public pages load their own local fonts and script. The separate admin interface loads DM Sans and Manrope through Google Fonts; opening the admin pages causes the browser to request font resources from Google, which may receive ordinary connection information such as an IP address and browser details. The project does not establish Google's processing terms for this use. These font requests are not an analytics or advertising tracker. Email, telephone, WhatsApp and Protox Webpages links contact those services only if you choose to use them; those providers have their own privacy practices.

Cookies and similar technologies

The public homepage and legal pages do not set cookies or use local storage, session storage, analytics trackers or advertising cookies in the code inspected. The admin sign-in uses a seven-day protoxtap_session authentication cookie with HttpOnly and SameSite=Lax attributes. It is used to keep an administrator signed in, not to track public visitors. Production sessions are configured with Secure; local HTTP development does not use that attribute.

The cookie is limited to administration authentication, but whether its purpose and seven-day persistence qualify for an exemption from consent requirements under PECR should be confirmed by the operator. No cookie banner is currently implemented. Hosting or proxy cookies and infrastructure logs cannot be confirmed from this repository.

Retention

The application does not have a complete, automatic retention schedule. Business and card configuration can remain in the database until changed or deleted. Tap events can remain after a subscription ends; they are removed when an administrator force-deletes the associated card, but cancellation does not automatically delete them. Administrative audit records have no routine deletion process. Expired session records are removed when checked by the application. Hosting, proxy, diagnostic-log and backup retention is controlled outside this project and has not been confirmed.

You can ask the operator to erase or restrict information. Requests are handled manually and will be assessed against applicable rights and any need to retain information for legal obligations or legal claims. A request does not trigger an automatic system deletion.

Security

The application uses scrypt password hashing, random session tokens, hashed database session tokens, an HttpOnly authentication cookie and restricted admin routes. These measures do not guarantee that a system is secure. Production hosting, HTTPS termination, database permissions, backups, incident response and provider safeguards must be checked by the operator.

Your rights and complaints

Depending on the circumstances, UK data protection law may give you the right to ask for a copy of your personal information, have inaccurate information corrected, request erasure or restricted use, object to certain processing, or receive information you provided in a portable format. Some rights are subject to exceptions. Contact protoxbusinesses@gmail.com or call 07923 910153 to make a request. The operator may need to verify your identity and will respond within the time required by law; this notice does not promise that every deletion request can override a legal retention requirement.

You may complain to the Information Commissioner's Office if you are concerned about how your information is handled.

Changes and contact

This notice will be reviewed if the service, providers or data practices change. Privacy contact: protoxbusinesses@gmail.com or 07923 910153.