Pinqr Privacy Policy

EIRENX LLC, a Michigan limited liability company, operates Pinqr. This policy covers personal information handled through the site, account services, public pages, QR redirects and support. Contact our privacy contact at support@pinqr.link or EIRENX LLC, 27733 John R Rd, Unit #365, Madison Heights, MI 48071. Telephone: +1 586-303-6281. We route privacy requests to the person responsible for privacy at EIRENX LLC.

For company-controlled information, your organization determines how it uses its workspace and employee data. When acting on its instructions, EIRENX handles that information under the data processing terms agreed with that organization. EIRENX separately determines its own account administration, billing, security and legal-compliance processing. Company features apply only when enabled for your workspace; describing them here does not make them generally available.

Stripe receives payment details directly; Pinqr does not store complete payment-card numbers. The application's analytics database does not store raw visitor IP addresses or full user-agent strings. Request processing and hosting/security providers can receive those details. Rate limiting uses one-way fingerprints; these and event records should not be treated as necessarily anonymous.

Company directory access, where enabled and authorized, is scoped to approved work-profile functions. It is not permission to read employee email, personal accounts or unrelated files; section 6 lists the Google and Microsoft information involved. We do not request precise device location for map links: the page owner supplies the destination. Choosing a map preview or link can send that destination and request information to Google Maps or Apple Maps.

Published pages, their links and contact-card details are available to people who open them. Public media is accessible to anyone with its direct URL, even when the associated page is unpublished. Do not upload confidential material as public media. Unpublishing alone does not remove the stored image; contact support about removal.

Search engines, visitors and third parties may copy public information. Downloaded vCards, exported signatures, screenshots and printed codes are outside our control. We cannot remotely recall those copies. External destinations have their own privacy practices. Your organization can manage company data according to its role; that does not give it access to your separate personal Pinqr account.

Authentication uses cookies and session information. Security tools process browser and request information to distinguish legitimate activity from abuse. Pinqr sets only the cookies below. They keep you signed in, protect sign-in steps or remember a display choice. None is used for advertising or cross-site tracking, so Pinqr does not ask for cookie consent. Clearing cookies may sign you out or reset preferences.

Pinqr does not keep information in your browser's local or session storage. The security check on sign-in, sign-up and report forms is Cloudflare Turnstile. It runs in a Cloudflare frame and may use browser storage under Cloudflare's own notice; Pinqr does not use it to track you.

Pinqr's own page/link/QR analytics count activity without building a cross-site advertising profile. We do not sell personal information or share it for cross-context behavioral advertising, and Pinqr contains no advertising pixels. Some providers also process information for their own purposes under their own notices, as section 5 describes.

The application does not currently change its first-party analytics in response to the legacy Do Not Track browser setting. It does not represent that Global Privacy Control handling has been implemented. Where an applicable law requires an opt-out signal or other choice to be honored for a covered activity, that obligation applies; contact us about your choices. We will provide notice and obtain consent where required before introducing optional tracking for new purposes.

We disclose information as needed to deliver the requested service, to providers performing relevant functions, to people you authorize, and as required or permitted by law for legitimate security, legal and business purposes. Our providers are:

• Supabase: authentication, database and file storage, in the United States.
• Vercel: hosting. Our application runs in the United States; requests reach it through the nearest location of Vercel's global network.
• Resend: service email, including sign-in and account messages.
• Zoho: support and business email, in its United States data center.
• Stripe: payment processing, subscriptions and billing.
• Cloudflare Turnstile: browser security checks. Its Turnstile privacy notice also describes processing for its own security-service purposes.
• Google: optional sign-in and authorized Google Workspace connections, where enabled (section 6). A linked map or other destination can separately receive a visitor's request.
• Microsoft: authorized Microsoft Entra company connections, where enabled (section 6).

Email providers process recipients, message content and delivery information. Our service email does not use open or click tracking. We send operational messages needed for your service. Promotional email, if introduced, requires the applicable consent, identification and unsubscribe arrangements; account creation is not blanket consent to marketing.

Authorized personnel may access information needed for support, maintenance, security, abuse investigations or legal obligations. We limit access to the task, never ask for your password and never sign in as you. Pinqr does not yet offer in-app support access grants or a customer-visible access history; if we introduce them, we will update this policy first.

We may disclose information in response to a valid legal requirement or to protect rights and safety where legally permitted. A corporate transaction may require protected disclosure to advisers or a successor, subject to applicable restrictions and any required notices or consent; it is not unrestricted permission to reuse data.

This section describes the information Pinqr receives from Google and Microsoft and how we use it. Pinqr's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Continue with Google. If you sign in with Google, Google shares your Google account ID, name, email address and profile picture link with our authentication provider. We use them only to create your account, sign you in and show your account details to you.

Company Google Workspace connection. This is available only when your organization enables it. An administrator of your organization connects Pinqr with Google's read-only directory permission. For the people your organization connects, Pinqr reads their Google account and organization IDs, whether the account is active, suspended or archived, their name, work email addresses, work phone numbers, organization name, job title, department and profile photo. An employee who verifies their identity with Google shares their Google account ID for that check.

Company Microsoft Entra connection. This is available only when your organization enables it. Pinqr uses Microsoft Graph with delegated permissions to read the signed-in user's profile, read directory users and read directory roles. It reads the organization (tenant) ID, user object IDs, whether an account is enabled, whether it is a member or guest, sign-in names used to match accounts, name, company, job title, department, work email and business phone numbers, and whether the person connecting holds the Global Administrator role.

How we use, store and share it. We use this information only to verify the people and organizations involved, link employees to their company workspace, fill in and refresh the work profiles, cards and signatures your organization approves, and remove access when someone leaves. We store the identifiers, a dated copy of the approved work-profile fields, approved photos and the connection's credentials, which are encrypted. We do not read email, calendars, files or other account data. We do not use this information for advertising or to train AI models, we do not sell it, and people do not read it except as needed for security, legal obligations or a support request you authorize. We share it only where your organization chooses to publish it, such as a published card or signature, and with the providers in section 5 that run the service.

How long we keep it and how to remove it. We keep this information while the connection is active. When an administrator disconnects, we ask Google or Microsoft to revoke our access and stop using the stored credentials. Copies of work profiles then follow your organization's workspace retention, and you or your organization can ask us to delete them (section 9). You can remove Pinqr's sign-in access in your Google Account settings; your organization's administrator can remove the company connection in the Google Admin console or Microsoft Entra.

EIRENX operates in the United States. Our main providers store Pinqr's account, content and database information in the United States. Request delivery, security checks, email delivery and payment processing can involve other countries where those providers operate, and local authorities there may have lawful access. We do not offer Canada-only data residency.

We use technical and organizational safeguards appropriate to the information and risks, including access restrictions. No system is perfectly secure. Provider certifications are not certifications of Pinqr. We notify affected parties when required by applicable breach-notification law.

We consider the service purpose, account status, security, payment reconciliation, legal obligations and disputes when deciding how long information is needed. Downgrading preserves content. Unpublishing or removing content can leave recoverable records and public media; it is not complete erasure.

We keep account information, content, usage analytics, payment-event records and pending checkout or invitation records while your account exists. Deletion requests are handled through support (section 9). We verify authority using information proportionate to the request, explain the scope, and address any lawful exceptions. A recovery option cannot extend a statutory deadline. Necessary billing, security, request-handling or legal records may be retained separately with restricted use; we explain applicable exceptions. Retired QR identifiers and published-handle reservations prevent reassignment and impersonation without keeping public-page content. A reservation is not a promise that the old destination will still work.

After personal account erasure, we retain a separate minimal record of the exact 18+ and Terms declaration, its server time, language/version and internal account references for six calendar years from row erasure. We use it only to assess, respond to or defend claims about that account's eligibility. This is a bounded risk-management period, not a statement that law requires six years in every case. Access is restricted, the purpose is reviewed periodically, and a longer hold requires a separately documented lawful reason.

Records of staff actions on accounts, such as lookups, changes and staff permission changes, contain identifiers, times and outcomes, not the content staff viewed. We keep each record for 24 months and then delete it, unless a documented investigation or legal hold about that account or workspace requires us to keep it until the hold is released. Support case notes and attachments are kept for 3 months after the case closes, subject to the same holds. Billing references are kept for seven years for accounting and tax purposes.

Our database provider's current plan keeps no restorable backups of our production database. Before planned maintenance, we take a private backup copy, keep it with restricted access and delete it within 30 days after the maintenance is complete. Copies independently retained by recipients and external services remain outside our control.

Edit or unpublish your content in the dashboard. To get a copy of your account information, email support@pinqr.link from the email address on your account. We send it in a structured, commonly used format.

For access to other information, correction, deletion, consent withdrawal, an applicable opt-out or a complaint, contact support@pinqr.link. Include enough context to locate the information, not passwords or card numbers. An authorized representative may contact us; we may verify that authority. We explain a refusal or limitation and available review routes as required by law. You may also complain to the relevant privacy regulator.

Rights and response periods depend on the law that applies to your request. Where required, we provide portable information, honor applicable choices and permit an appeal. We will not unlawfully discriminate against you for exercising rights. Essential processing may still be needed to provide a feature you request. An organization may need to handle requests about the company records it controls; we assist as appropriate and remain responsible for our own obligations.

Accounts are limited to people aged 18 or older based on their declaration; signup does not require ID documents. Contact us if you believe an underage person has an account or we hold a child's information. We assess the report and take the action required by applicable law; a false declaration does not eliminate our duties.

The version and effective date of this policy appear at its top. We give notice of material changes and obtain consent for changed processing where required. A revised notice does not retroactively authorize an incompatible use of information.