Privacy Policy

A QR code made with PMC QR Track opens a short link that counts the scan and forwards you to the destination the business chose. For each scan we record:

• the date and time;
• the type of device (phone/tablet or computer), worked out from your browser's user-agent, which itself isn't stored;
• an approximate location: country and city, worked out from your IP address;
• an anonymous visitor code: a one-way fingerprint made from your IP address and browser type, so repeat scans by the same device can be counted once;
• the page that linked to the code, if your browser sends one, and any campaign tags in the link (for example “utm_source=flyer”).

We don't store your IP address, don't set cookies, don't ask for your name, email or phone number, and don't use advertising or cross-site trackers on the scan link. We can't tell who you are from a scan. The business that made the code sees counts and charts (for example “120 scans, mostly phones, mostly in Whittier”), not individual people. Automated visits (link previews in chat apps, search engine crawlers) aren't counted.

After the destination opens, that website's own privacy policy applies. Questions about a specific QR code are best sent to the business or school that shared it; you can also contact us (section 9).

Reporting a QR code. If a code leads somewhere harmful, you can tell us on the Report a QR code form. We receive the link you enter, the reason you pick, anything you write and, only if you give it, your email address, so we can answer you. The report goes to us, not to the business that made the code. We also keep a scrambled (keyed hash) form of your network and browser, never your IP address, to stop floods of automated reports. We use the report only to review the code and, if you asked, to reply.

PMC pages and “Get updates”. Some codes open a short page made with PMC QR Track (for example a game-day schedule or a menu). Opening one sets no cookies and stores nothing about you: we only count visits and taps on its buttons as daily numbers. If you fill in its “Get updates” form, the team or business that made the page receives what you typed (your name, email or mobile number, and the answer to its question), with the time, the page, the QR code you scanned (if any) and the exact consent wording you saw. We store it for them: they decide how to contact you and must follow email and texting rules. We never email or text you ourselves, sell your details or use them for anything else. We don't keep your IP address, only a scrambled (keyed hash) form of your network and browser, used to spot floods of automated sign-ups. You must be 13 or older to sign up.

• Account: name, email address, a scrambled (hashed) password, which Terms and Privacy versions you accepted and when, and whether your email is confirmed.
• Teams and work: team names, members and roles, invitations, campaigns, QR codes and where they point, designs, uploaded logos, templates, bulk-print spreadsheets and PDFs, report settings and the email addresses you choose to send reports or alerts to.
• Client portal: the accounts you invite for your customers and your white-label brand settings.
• Integrations: Slack alert links (stored encrypted) and conversion events your systems send us (for example an order number and amount).
• Security: a list of your signed-in devices (browser and operating system, like “Edge on Windows”) and a log of important actions (such as deleting a QR code or exporting data) with the IP address and browser that did them. Attempt counters that stop password guessing store only scrambled values, never your email or IP address.
• Payments: handled by Stripe. We store your Stripe customer and subscription status, not card numbers. Subscriptions bought in the iPhone app are handled by Apple through RevenueCat: we receive the subscription's plan, status and dates and Apple's transaction number, never your Apple Account details or payment method.
• PMC pages: the pages you build, the photos you upload (we save them again without hidden details such as location), the contacts your pages collect, and daily counts of visits and button taps.
• Support requests: what you write, and with it the page you were on (with anything secret in its address removed), your team, its plan, your browser and the app version. Never your password.
• iPhone app notifications: if you turn on “Push to my phone” for a QR code, the push token Apple gives your phone, used only to send your scan alerts. It's deleted when you sign out of the app, when Apple says it's no longer valid, or when you delete your account.

• to run the service: show your dashboards, redirect QR codes, send the emails you set up (reports, alerts, invitations) and account emails (confirmation, password reset, security notices);
• to keep accounts secure and prevent abuse;
• to bill for subscriptions;
• to compare campaign performance within similar groups (benchmarks). Other teams only ever see their own campaigns plus totals and averages, never your data or names.

We use one essential cookie that keeps you signed in (it can't be read by page scripts). If you “Explore the demo” from our homepage, a second small cookie remembers when that one-hour visit ends. Your browser also remembers your light/dark theme and the team you last used. We don't use analytics, advertising or other tracking cookies. Scanning a QR code sets no cookies (one exception below: a live event’s voting page). We count visits to our public homepage and the button presses there (like “Start your free trial”) with Vercel Web Analytics, which uses no cookies, keeps no IP addresses and can't identify you; it never runs on signed-in pages.

Live events. If you take part in a team's live event (a fan vote, a quick poll or the hype meter you open by scanning its code), the voting page sets one essential cookie holding a random number, so each phone votes once; it holds nothing about you and expires after 30 days. Your answer is kept with scrambled (keyed hash) forms of that number and of your network address and browser, which can't be turned back into either; they're used only to count one vote per phone and to filter floods of automated votes. We never ask fans for a name, email, phone number or birth date, and we don't keep their IP address or location. Votes are just for fun: no prizes by chance, no payment.

We share data only with the service providers that run PMC QR Track for us, under their own privacy and security terms:

• Vercel: hosting, and anonymous visit counts for our public homepage (no cookies). Vercel also works out a scan's approximate location (country and city) from the IP address; we don't send IP addresses to any other location service;
• Neon: database hosting;
• Resend: sending emails;
• Stripe: payments and tax calculation;
• Apple: App Store subscriptions bought in the iPhone app, and delivering its push notifications;
• RevenueCat: keeping track of App Store subscriptions (it receives your team's ID, not your name or email);
• Slack: only when you set it up, and only the alerts you send there;
• Google (Web Risk): checking that the links QR codes open aren't known to be unsafe. Google receives those destination links, never anything about the people who scan them.
• The team or business whose page you signed up on receives your “Get updates” sign-up. Photos on PMC pages are stored by Vercel.

The businesses and schools that use PMC QR Track see their own campaigns' scan statistics. We may also disclose information when the law requires it, or to a buyer if our business is sold (with this policy still applying).

• Scan details are kept for 25 months. After that, each day's scans are reduced to daily totals per QR code (counts by device, country and city) and the individual scan records, including visitor codes and exact times, are deleted.
• Account and team data is kept while the account or team exists and deleted when it's deleted. Copies can remain in encrypted database backups for up to 30 days.
• Print PDFs are cleared after 30 days (they can be recreated); signed-in device records 30 days after signing out; emailed links a day after they expire or are used.
• IP addresses in the security log are removed after 90 days.
• QR code reports: the email address you gave is deleted 12 months after we've dealt with the report; the rest of the report is kept as a record of what we reviewed.
• “Get updates” sign-ups (contacts) are kept until the team that collected them deletes them, or until we delete them on request. When that team or the account that owns it is deleted, they're deleted with it, and never kept more than 12 months after that.

• Customers can see and change their information in Account settings, and delete their account there. Team admins can delete QR codes, campaigns and teams.
• Anyone, including people who scanned a code, can ask us what we hold about them, to correct it, or to delete it, by emailing alexistellezperez@prolificmediacompany.com. Because scans are anonymous we may need details (for example which code and roughly when) to find anything.
• People who signed up on a PMC page can unsubscribe with the team that sent the message, and can ask that team, or us at alexistellezperez@prolificmediacompany.com, to delete their details. We'll delete them.
• California residents have the right to know, delete and correct personal information, to opt out of its sale or sharing (we don't sell or share it for advertising), and not to be discriminated against for using these rights. You can use them by emailing us; an authorized agent may also make a request for you.

PMC QR Track accounts are for adults acting for businesses, schools and organizations; we don't knowingly let children create accounts. QR codes for schools and teams may be scanned by students, including children under 13. A scan collects no name, contact details, photo or IP address, and sets no cookies (section 1); a live event’s voting page sets only the one-vote cookie described in section 4 and asks nothing about the fan, and we don't use scan data to build profiles or for advertising. Schools shouldn't upload student records. A PMC page’s “Get updates” form asks anyone signing up to confirm they’re 13 or older.If you believe we hold a child's personal information, contact us and we'll delete it.

We use encrypted connections (HTTPS), hashed passwords, encrypted Slack alert links, sign-in rate limits and access by team role. No system is perfectly secure; if a breach affects your information we'll tell you as the law requires. Our data is stored in the United States.

Questions or requests: Prolific Media Company, 5134 N Muscatel Ave, San Gabriel, CA 91776. Email: alexistellezperez@prolificmediacompany.com. See also our Terms of Service.

We'll post any update here with a new date, and ask signed-in users to accept important changes.