What we keep
Scanning a sticker does not reveal the owner’s phone number or email. To manage your vehicles, we use your email address or the available sign-in provider you choose. Sticker order details are used to deliver your order.
Who is responsible for your data
OUQM is owned and operated by Exabyte Investment LLC in Muscat, Oman. Exabyte Investment LLC is responsible for the processing described in this policy. For questions or privacy requests, contact privacy@ouqm.com.
What we actually keep
Supabase Auth holds your sign-in email and provider identifiers to authenticate your account and send email sign-in codes when you choose that method. We do not copy the email into your owner profile or vehicle records. We also hold vehicle and sticker details, device notification tokens, alerts and replies. Scanning requires no account; a temporary marker that changes daily helps limit misuse.
Care requests
When you submit a Care request, we store the service category, your message, your selected vehicle if any, replies, timestamps, request status and read status. Our authorized OUQM team also sees your saved name, sign-in email, phone if provided, account information, vehicles and tags to understand your needs and respond in the app. Conversations are private to your account and our team; people scanning your tag cannot see them. We do not automatically attach your Mulkiya photo or forward your conversation to suppliers. Do not include payment details or identity documents in messages. Conversations remain until you delete them from conversation options or delete your account; deletion also removes them from the team inbox. Deleting a conversation does not delete your account or vehicles. Care is an enquiry channel, not a confirmed booking or emergency service.
Your account and vehicles
We use your account ID, language, service settings, account dates and privacy-acceptance records to manage the service. Your sign-in provider may also supply a display name or profile image as authentication metadata. We store your chosen vehicle name, make, body type, colour and plate ending, plus sticker identifiers, labels, status and activation/replacement dates. If you set absence mode, we store its reason and dates. Scanners can see the vehicle description, plate ending and the absence information shown by the app; they do not see your sign-in email or complete private registration.
Reports, replies and service protection
We store the report type, time and status, preset or owner-written replies, and abuse reports. Replies are shared with the relevant reporter, so do not include personal information you do not want to share. We may derive an approximate city from the connection; we do not request precise GPS location. Browser information, language and part of the IP address produce a marker that changes daily to limit abuse. Hosting services process connection information to serve and secure the site. When signed in, in-app scans use account-bound security markers and request identifiers to enforce limits and recover interrupted sends. A sender token and recent alert receipts are stored securely on your device to display status and manage replies; these receipts expire after one hour. Notification tokens, device platform, last contact and delivery errors support alerts and delivery troubleshooting.
Email notifications
We send vehicle alerts, vehicle and sticker change confirmations, and Care updates to your sign-in email through Google Workspace. Email links open the app to reply; we do not attach your documents or Care files. You can turn these emails off through their settings link; sign-in and security emails are separate. Delivery records are retained for up to 30 days; messages in your mailbox remain until you delete them.
Sticker reservations and support
A sticker reservation collects a contact name, phone number, email, language, order details and status. Delivery records may include an area and address instructions when supplied. We use these to contact you about the order and fulfil it, and may link allocated stickers to their order for fulfilment. People handling delivery may receive the details they need. If you contact support or privacy, we process your contact details and message to resolve the request. Do not send Civil ID details or complete documents without a specific need and appropriate instructions.
Private vehicle registration
Tag activation does not require a registration document, full plate or chassis number. You may optionally save the private Mulkiya photo described below. If you previously supplied private registration details or provide them in a recovery request, records may include issuing country/authority, plate code and complete number, encrypted with a private matching fingerprint. The account holder and authorized reviewers can access these records. Current details remain while linked to the account; closed request details and former registrations are removed after 30 days when cleanup runs. Review requests expire after seven days. A stored photo alone does not verify ownership or prevent the same vehicle being registered through another account.
Registration review and administrative access
When review is needed, we store the registration request, status, your note, clarification messages, reviewer decision, reason and dates. Administrative operation records include the staff member, action, affected record, reason and change details for accountability. Access is restricted to authorized roles. A registration match does not reveal another account’s details, and knowing a plate or presenting a photograph alone does not grant access to a vehicle or account.
Your private Mulkiya photo
A Mulkiya photo is optional. You can activate and use your sticker without uploading a document, and add or delete a private registration photo later. Tapping Agree and activate or Agree and save uploads the image to private encrypted storage. We store the image you submit, including any chassis number, personal information or embedded metadata it contains, together with account/vehicle IDs, file type, size, integrity hash, upload/consent/expiry dates and notice version. Crop to the vehicle details and cover unrelated Civil ID, address, signature and insurance details before sending; we do not redact them automatically. We retain it as a private vehicle registration record to support manual review of ownership disputes, suspected duplicate registrations and abuse reports. Uploading it does not automatically verify ownership or prevent duplicate registrations. Before introducing any further use, we will explain the processing and obtain the necessary consent. Existing uploads retain their original consent record; this policy does not authorize a new use of them. We do not run OCR or automatically verify ownership; the sticker activates after saving without an approval queue. Scanners cannot see the photo, and we do not send it to advertising or parts services. You can view and delete it in private registration. Access expires 90 days after upload, or after 24 hours if it is not attached to a vehicle. Replacing/deleting it or deleting your account revokes access and queues the file for deletion. Scheduled cleanup removes expired/deleted files and keeps a deletion marker for 24 hours to repeat cleanup after any late upload. Temporary device copies may remain until device cleanup; we do not delete your original library image. Photo deletion or expiry does not deactivate your sticker.
An experience suited to you and your vehicle
We use your vehicle details, chosen language and settings to personalise your OUQM experience. We plan to help you find suitable parts and accessories when you choose those services. This may involve extracting a chassis number and vehicle specifications from the image; your choices tell us your preferences. The photo is currently stored without automatic extraction or parts matching. Before enabling those features, we will explain the extracted data, recipients, processing locations and retention and obtain any required permission. Accepting this policy is not advance consent to marketing or new sharing.
Care photos and files
You may choose to send an image or PDF in a Care conversation. We store the encrypted file, its name, type and size with the message so our team can understand and respond to your request. Access is limited to your account and authorized OUQM staff. We do not automatically attach vehicle documents or extract file contents. Do not send unnecessary identity documents or payment details. Files remain with the conversation; deleting the conversation or account revokes access and queues files for scheduled deletion. Unfinished uploads are removed after a day, with a second cleanup pass after 24 hours to catch late uploads. Temporary device copies may remain until cache cleanup; copies you save or share outside the app are under your control. Team reply notifications may show a text preview according to device settings, but do not contain the file.
Where it is kept
Supabase processes account, vehicle and Care conversation data and stores encrypted Mulkiya images and Care files. Your chosen sign-in provider processes authentication. Hosting, email and notification providers also help operate OUQM. Contact privacy@ouqm.com about processing providers or to exercise your rights.
Reporting and blocking alerts
When you send an alert, we set an essential random browser cookie lasting up to 90 days and derive a different identifier for each sticker to prevent misuse. We do not block shared network addresses. If an owner reports an alert, we store the reason and review status; they may block that browser for that vehicle, including safety alerts. Owners can remove their blocks in Settings. A scanner can also block that owner’s replies for that sticker in their browser, including preset replies, and unblock on the sticker’s scan page. This control reuses the same identifier and does not prevent sending alerts or calling emergency services. We store the owner, sticker, browser identifier, source alert and block/expiry dates. These blocks end when the source alert is deleted or expires within 90 days. The identifier does not reveal the sender’s identity to the owner. Clearing cookies or using another browser bypasses a browser block, and replies already received cannot be recalled. These identifiers are not used for advertising.
On-device storage and website measurement
The app retains session credentials and preferences; the website uses language and session cookies where needed. Marketing and order pages may use measurement through Google Tag Manager when enabled, processing visit and interaction information. These tools are not placed on sticker-scanning or private-registration pages and do not receive Mulkiya images. Acceptance of this policy alone is not consent to new measurement purposes.
How long we keep it
Alerts are deleted after 90 days and delivery details after 120 days. Sign-in data remains while your account exists. You can delete your account in Settings; limited records may remain under the exceptions explained on our data deletion page.
Your rights
You can ask for a copy of your data, ask us to correct or delete it, and withdraw your consent at any time.
How to use your rights
Email privacy@ouqm.com to get a copy of your data, correct it, delete it, or withdraw your consent. We answer within 30 days. You can also complain to the Ministry of Transport, Communications and Information Technology.
Updated 20 October 2026