Privacy notice · 1 October 2026
What happens to QR code data?
This notice describes QR Arab's current data processing from 1 October 2026. Mohamed Ahmed operates the project as an individual in Egypt. QR Arab is the project's name, not a registered company name. Contact support@qr-arab.com about your data.
Creating and managing a code
When you publish a code, the server stores its destination URL, design settings, status and identifier. A guest’s browser keeps the information needed to manage that code from the same browser. The server stores a digest to verify it; knowing the public short link alone does not let someone edit the code. Design drafts may also remain in local browser storage.
For the WhatsApp QR tool, the international number and optional prepared message become part of the stored destination URL and can be accessed by anyone who opens the published QR link. Do not enter another person's number or a private message you do not want scanners to see.
The QR image reader decodes the code in your browser; it does not upload the image or its contents to QR Arab. A visit to the tool page itself is included in the public-page usage totals described below.
Clearing browser data or switching devices may leave a guest without that management access. A guest code can be transferred to an email-verified account while its management secret is still available in the browser.
Accounts, email and Google sign-in
When you create an email account, the service stores your name, email address and password-verification data, and sends messages to verify the account or reset its password. Operational email currently uses Brevo. If you choose Google sign-in, the service receives your Google account identifier, name and verified email to link the sign-in to your account. It stores the link identifier, name and email, but not your Google password.
The current Brevo account setting removes transactional email logs automatically after one month for all senders and does not save previews of new messages. Changing preview storage does not erase older previews retroactively; the existing logs follow the same retention period. This does not cover the separate inbox receiving direct support mail.
Scans and reports
When an active QR link is opened, the server sends the destination redirect first, then attempts to queue a scan event after sending the response. A queue failure does not change the destination; a failed enqueue is absent from the report. The event records time, bot and prefetch classification, device, operating system, browser, and source or campaign if available. Known bots and prefetches are excluded from the displayed count, while repeat requests are counted. Reports describe eligible requests, not unique people.
The local DB-IP City Lite database may estimate country and city from the client IP during a scan request. It is used under CC BY 4.0 with attribution; its coverage and accuracy are lower than the commercial version. Of the geographic data, only the estimated country and city enter the analytics queue and scan tables; the IP is not included in their payloads or rows. Without a readable database, geography shows as unknown. City is approximate, and a phone camera may provide no referral source. Web server and proxy logs may have separate IP retention settings.
Detailed scan events are removed after 12 calendar months only after their summary counts are reconciled. Daily summaries remain for historical reports. Encrypted backups are currently retained for seven days on the production server; an off-server backup location has not yet been approved.
Contact messages
The contact form stores a name, reply email, topic and message in a private admin panel for review and possible reply outside the platform. Do not submit passwords or guest code management secrets. Once follow-up is manually closed, the form record is deleted from the database one year after closure. Open messages are not automatically deleted; those older than 90 days are flagged for review. Email sent directly to the support address is forwarded to an external Gmail inbox. It currently has no fixed automatic deletion period; messages there are reviewed manually.
Choose “Privacy or data request” in the contact form to request access, correction or deletion. Provide your account email or relevant code link only if needed; do not send a password, management secret or identity document in the initial message. We do not disclose account or code data or delete it merely because someone knows the public QR link. The requester's authority, data scope and applicable retention must be reviewed before action. Sending the form does not execute deletion automatically.
Public page usage measurement
The app keeps daily totals for the first public page a browser session opens and for QR codes created later that same day. Available referrers are grouped as Google or Bing search, another referrer, or unknown; a missing referrer is not proof of a direct or organic visit. This measurement table stores no IP address, full referrer URL or session identifier. Counts may be approximate when referrers are withheld, sessions are not retained or unknown bots are involved. These totals currently remain for the lifetime of the service without a fixed automatic deletion period.
On the live site, Cloudflare adds a page performance beacon (RUM) and sends timing metrics to /cdn-cgi/rum on this domain. This is separate from the Laravel daily totals above. Cloudflare documents the fields collected by the beacon; its Web Analytics FAQ says unsampled data is retained for seven days, then aggregated for longer-term storage, with the previous six months available to view. The viewing period does not mean that all Cloudflare copies are deleted when it ends. Our QR reader code does not send the selected image or decoded text to this endpoint. We cannot specify a deletion period for all other Cloudflare copies because we do not control every layer of its retention.
Operational logs
Web-server logs may contain an IP address, requested path, request time and browser information for operations and security. They rotate daily, with local copies kept for approximately 30 days. Daily application error logs keep the most recent 30 daily files. These periods do not cover Cloudflare copies or the external support inbox.
Other sites and providers
A scanner is sent to the destination selected by the code owner, where that site's own privacy terms may apply. The service uses a hosted server and Cloudflare to serve requests and route incoming support email, Brevo for outgoing operational email, and Google only when a user chooses Google sign-in. Some data may be processed outside Egypt by these providers under their terms; this page does not identify every processing country or the legal basis for each transfer. You can ask a privacy question or request your data at support@qr-arab.com or through the contact form. You can also lodge a complaint with the Egyptian Personal Data Protection Center.
See the terms of use and the editable link explanation.