Everything before
your first scan.

A static QR code stores its final content directly in the image. A dynamic QR code stores a QRalto redirect address, allowing you to update the destination and measure scans after printing.

No. A downloaded static QR code continues to contain its encoded content and does not depend on QRalto hosting. The destination website itself must remain available.

Yes, when the campaign uses Dynamic mode. Static QR pixels cannot be changed after download or printing.

Protected product features are blocked after entitlement expiry. Dynamic redirects are subscription-controlled, while previously downloaded static codes remain independent.

Raw scanner IP addresses are not retained in product analytics. QRalto creates an irreversible value with a private salt for approximate unique-scan reporting.

QRalto measures scans that pass through an active Dynamic QR redirect. Static QR codes encode their final content directly and are therefore shown as Not tracked rather than displaying a misleading scan count.

Dynamic QR analytics include hourly and daily trends, countries, cities, devices, operating systems, browsers, referral hosts and privacy-aware unique-scan estimates. Country and city coverage is shown so incomplete geographic data is not presented as complete.

Yes. QRalto workspaces support Owner, Admin, Editor and Viewer responsibilities, subject to plan limits.

API access is available on eligible plans using scoped, expiring keys. Sensitive key creation and revocation require multi-factor re-authentication when MFA is configured.

Yes. A restaurant can create a managed Digital Menu with categories, items, prices, images, dietary tags, allergen notes, availability, date-based specials, brand colors and guest contact actions. QRalto creates the associated Dynamic QR automatically.

Yes. Teams can publish product model, materials, origin, manufacturer references, care, repair, warranty, recycling, sustainability and documentation information. QRalto creates a managed Dynamic QR for the product-level passport.

The same model and unit QR codes open the latest published record. Every saved product-information change creates a numbered snapshot with changed fields and a hash linked to the previous revision, and that history is visible on the public scan page.

No. The hash-linked application history makes ordinary publisher changes visible and detects broken links inside the stored chain. It is not a blockchain, manufacturer digital signature, third-party certificate or proof that a database administrator could not rewrite stored history.

Yes, on plans with bulk creation. A batch can queue up to 100,000 units and is processed in resumable 1,000-unit chunks. Each unit receives a stable serial and non-sequential data-carrier token, with CSV export and individual SVG or PNG QR downloads.

No. QRalto confirms whether a QRalto-issued digital token exists, reports its active, suspended, recalled or revoked state, and flags simple scan anomalies. A label can still be copied or moved, so physical security and investigation remain the brand's responsibility.

Yes. Eligible plans can upload a validated CSV or XLSX file containing up to 1,000 rows per job. QRalto creates the codes in the background and provides a private ZIP export with a manifest for seven days.

Yes, through signed automation webhooks on eligible plans. QRalto sends versioned events with retry and delivery tracking to webhook-capable Zapier, Make, HubSpot or custom workflows. Official marketplace listings are separate provider-review deliverables.

Yes, on eligible plans. Add QRalto's TXT ownership record and CNAME traffic record, verify the hostname, and choose it when creating or exporting Dynamic QR codes. QRalto provisions HTTPS, keeps the hostname tenant-isolated, and lets a workspace choose a default domain without silently changing previously generated QR artwork.

Workspace owners receive a tracked referral link. A referred business receives extra trial time, and the referring workspace receives bonus scans after Stripe confirms a qualifying first paid checkout, subject to fair-use controls.

No. QRalto implements security controls such as tenant authorization, MFA, hashed API keys, private asset storage, audit records and durable event delivery. It will not claim SOC 2 Type II assurance or support protected health information under HIPAA until the required independent assessment, agreements and operating procedures are complete.