SERVICE INFORMATION
Privacy policy
Updated October 12, 2026. This notice covers NFC Pass at nfcpass.app: tools for businesses to create, deliver and manage digital passes, and services for people receiving those passes.
NFC Ticketings is published by PARTH SURENDRABHAI PATEL. Questions and privacy requests can be sent to support@nfcplate.com. The event organizer is responsible for the attendee information it asks us to process for its event.
Information used to provide your pass
We process account and recipient details, such as your email address and name; information requested by the pass issuer; pass designs, validity, membership or offer details; and the records needed to issue, recover, transfer, update or validate a pass. A coupon may be available without an NFC Pass account. Email verification still protects access to that coupon.
Business owners and authorized staff can access records for their workspace. The business that issues your pass decides which information it requests and how its program works. Its own privacy notice may also apply. NFC Pass keeps operational and security records needed to run the service and investigate abuse.
Wallet, email and scanning
When you choose to add a pass, its content is provided to Apple Wallet or Google Wallet. These providers process information under their own policies. We may send requested verification, pass delivery and ticket-transfer emails. Issuer messages and available communication preferences are separate from optional analytics.
The scanner uses the camera with permission to read pass codes. Scanning sends the decoded credential and the requested validation action to NFC Pass. Pass, staff, time and configured validation-place records support admission or redemption and prevent repeat use. A configured venue or validation place is not continuous tracking of your phone’s location.
Service providers
NFC Pass uses Supabase for authentication, data and storage, Vercel for hosting and server processing, and Resend for transactional email. Apple and Google provide optional Wallet services. An issuer may configure webhooks or other integrations that send its program’s events to a destination it controls.
NFC Membership and NFC Coupons & Offers in ChatGPT
These separate connections are published by PARTH SURENDRABHAI PATEL and manage their corresponding pass types in NFC Pass. The business issuing a membership or coupon is responsible for the recipient information and program rules it asks us to process.
When you connect, we process the account identifier, authorization token and tool requests needed for the operations you request. Membership requests and results may include programs, tiers, expiry rules, designs, artwork, member names and email addresses, external member identifiers, points, status, manual activity and reports. Coupon requests and results may include offers, validity windows, designs, artwork, signup configuration, recipient names and email addresses, pass status and reports. Both connections can process welcome-email configuration and Google Wallet message text, audiences, schedules and delivery status.
Relevant results are returned to ChatGPT. Private profile values, member photos, completed signup or redemption answers, live barcodes and credentials are excluded from these tools. Those workflows open the secure NFC Pass workspace. Artwork attachments follow the image-processing rules below. Request contents are processed in memory, while saved program records, artwork and retry records remain in NFC Pass under the retention rules below. These connections do not provide NFC activation, payment processing or automatic installation on a phone.
Email and offline-access identity scopes may be requested by ChatGPT. Offline access permits session refresh until access is revoked; it does not enable offline scanning. You can revoke Membership access or revoke Coupons & Offers access. Revocation stops future requests; an operation already in progress may finish. It does not erase existing passes or earlier ChatGPT messages and results. Configured issuance, lifecycle changes or scheduled messages may trigger email, Wallet updates or workspace webhooks.
When you connect NFC Ticketings to ChatGPT
Holder operations can return your ticket summaries and transfer invitations. Recovery uses your verified account email. Starting a transfer queues an invitation email to the recipient you confirm; acceptance replaces the original ticket. Owner-requested team operations process the teammate’s email, role and access state. Staff permissions apply across the workspace, including its other pass types. Creating a staff invitation sends no email; the invited person must accept with the matching verified account. Private invitation tokens are not returned to ChatGPT. Webhook controls return destination hostnames, subscriptions and limited delivery statuses, withholding signing secrets and secret URL paths.
Connecting authorizes supported ticketing operations in the workspaces you manage. We receive the tool requests ChatGPT sends to carry out your instructions, a connection token and an account identifier. Depending on the action, requests contain event names, schedules, ticket designs, capacities, enrollment configuration, recipient names and email addresses, ticket search criteria, management reasons, report options, or message text and schedules. Requested results can include ticket recipients, status, activity, reports and message delivery results. We do not receive your entire ChatGPT conversation through this connection.
We return the relevant project or operation result to ChatGPT. The connection excludes account passwords, API secrets and live ticket-admission codes from tool results. The connection server processes request contents in memory and does not create a separate chat-history database. Saved event and ticket records remain in NFC Pass. Hosting and authentication providers process connection and diagnostic metadata to operate and protect the service.
Saved proximity-library operations return entry names, identifiers and revisions to ChatGPT. If you ask ChatGPT to create or edit a project-owned location or beacon, the request includes the public event-venue coordinates or venue beacon configuration you provide; NFC Pass stores those values but omits them from the returned summary. Do not provide a person's private address or current whereabouts. Applying a saved entry copies its values into the selected design. Archiving a shared library entry changes its availability for future use across that workspace; it does not change values already copied into pass designs.
The protected webhook form lets you enter or view a supported destination URL, whose path may contain a secret. NFC Pass and the ChatGPT host process that URL as form data; it is excluded from model-visible tool results. Signing secrets are not returned to the form. Saving creates or edits a paused endpoint and sends no event. Enabling, testing and retrying delivery are separate requested actions. Retry protection stores a digest of the save request, its identifiers and a summary without the destination path until the related project or requesting account is deleted.
If you ask us to upload artwork attached in ChatGPT, we use the temporary file link supplied for that action to download the image. We validate it, remove embedded image metadata and save resized versions in your NFC Pass workspace. The temporary link and original file are processed in memory; we do not save them as a separate attachment archive. Saved artwork follows the workspace-record retention described below.
Wallet inspection returns selected layout information from generated Apple and Google ticket data. Private registration answers, barcode contents, precise locations, beacon identifiers and signing material are omitted. Wallet status returns recorded registration and recent update outcomes, not device identifiers or private provider error messages. An installation link identifies a ticket and requires its holder to sign in; it does not grant access by itself.
The protected ticket-details form loads registration answers or consent receipts only when you choose a section. These values are returned as component metadata, which the ChatGPT host delivers to the form without including them in model-visible conversation content. OpenAI still processes the form and its data. Reviewed edits are saved to NFC Pass using the existing access, encryption and audit controls. Do not use this form for passwords, payment information, government identity documents or health information.
OpenAI processes the information you share in ChatGPT and the returned tool results under its own privacy policy and your account settings. Workspace Wallet providers and configured webhooks may receive ticket events when you issue a ticket. We use connection data to provide your requested service, maintain security and resolve support issues. We do not use this integration to sell personal data, target advertising or build behavioral profiles.
You can revoke NFC Ticketings access or disconnect the plugin in ChatGPT. Revocation stops future requests through that connection; an operation already underway may finish. Revocation does not delete saved tickets or data already returned to ChatGPT. Manage ChatGPT conversations in your OpenAI account, and contact us about NFC Pass records.
Retention
| Information | How long it is kept |
|---|---|
| Connection request contents | Processed for the request; no separate conversation archive is stored by the NFC Ticketings server. Changes you request become the records described below. Retry records for message drafts and webhook tests or retries retain submitted details and identifiers until the related project or requesting account is deleted. Staff-invitation retry records retain submitted details until the invitation, workspace or requesting account is deleted. |
| Account, workspace, program designs and pass records | Kept while the account or issuing workspace maintains them. Pass records do not automatically disappear when an event ends or a pass expires. A verified account or workspace deletion removes the associated records through our deletion process, subject to the exceptions below. |
| Authorization and session records | Kept while the connection or account is active. Revoking the connection invalidates its sessions and refresh tokens. A record of the revoked permission can remain until account deletion. |
| Admission, audit and operational records | Kept with the issuing workspace to support security, event operation and disputes. Membership check and verification records follow any retention period selected by the issuer. Ticketing currently has no automatic event-age purge; request deletion through support. |
| Optional coupon analytics delivery records | 30 days. The issuer’s Google Analytics property has its own retention settings. |
| Support requests | Kept while resolving the request and for up to 12 months after resolution to handle follow-up and document the response. We review and remove older correspondence unless a specific dispute or legal obligation requires retention. |
We aim to complete verified deletion requests within 30 days. If we need more time or must retain particular information for a legal obligation, security investigation, unresolved transaction or another person’s rights, we will explain the reason and applicable period. Provider logs and backup copies have separate expiry cycles; these must expire or be removed through the provider’s supported process. Deleting a pass from Wallet or disconnecting ChatGPT does not itself start account deletion.
Security and international processing
Access controls, encrypted connections and account permissions help protect information. No service can guarantee absolute security. Our providers may process data outside your country under their applicable contractual protections. Do not enter passwords, payment-card information, government identifiers, health information or other sensitive data in ticket fields or send them to support.
Optional coupon analytics
If an issuer enables Google Analytics on its public coupon signup form, you choose whether to allow measurement for that form visit. It is off until you opt in. Declining does not prevent signup or coupon access.
After opt-in, NFC Pass sends form-view and successful coupon-access events, their times, a random session identifier and the pass category to the issuer’s Google Analytics property. The integration does not send your name, email, form answers, IP address, verification code, barcode or private pass link. It does not install a Google script or analytics cookie and does not enable advertising personalization.
This choice lasts for the current form visit, up to 30 minutes. Turn it off on that form to cancel events that have not yet been sent. The switch cannot recall events already sent to Google. NFC Pass keeps analytics delivery records for 30 days; Google’s retention follows the receiving property’s settings and Google’s policies. These events measure coupon access, not proof that a pass was installed in Wallet.
How Google uses information from sites and apps.
Your choices and requests
You can decline optional analytics, manage communication preferences where offered, and remove a pass from your Wallet. Removing a Wallet pass does not delete the issuer’s underlying ticket, membership or coupon record. Contact the issuer about program details, corrections or cancellation.
For questions or requests about access, correction or deletion of NFC Pass account information, email support@nfcplate.com from your registered address. We verify ownership before making account changes. Do not send your password, verification code or private pass link. Some operational records may need to remain to protect other users or address unresolved transactions and disputes.