Last updated: 15 November 2026
Your information.
Handled with care.
This notice covers the RipTags marketing website, its interactive examples, enquiries and private QR-family workspace. Your enquiry stays private. The marketing examples use sample records. QR-family observations are real records saved when you submit them. Optional advertising and analytics scripts are not enabled on these pages.
Who is responsible
RippleXn operates RipTags and is responsible for deciding how the personal information covered by this notice is used. Use the privacy-request route below to contact the team or request the registered controller’s identity and contact details. The wider RippleXn notice is available at RippleXn.com/privacy.
What this website handles
- QR families: your site-specific sign-in identifier, location and point names, observations, readings, photos, reviews, check intervals and recorded actions are saved in the hosted workspace. The owner can invite named colleagues as engineers or viewers for a specific location. Invitations store the recipient email, role, expiry and a token hash; accepted membership uses the site-specific account identifier. Scanning a QR code does not grant access. Revocation stops future online access but cannot recall copies already downloaded. Point relationships, priority explanations and feedback are stored with the evidence. Photos submitted through the workspace are resized and re-encoded in your browser before upload.
- Sensor records and optional browser alerts: a stream is linked to a point and stores timestamped values, units, quality, calibration notes, configured limits and evaluation evidence. Device credentials are stored as hashes; the credential itself is shown once to the owner. Test streams are labelled synthetic. Browser alerts are opt-in. We store the browser push endpoint and subscription keys privately and send an encrypted, generic notification through your browser’s push service. Notification attempt status is retained; acceptance by that service does not prove a person saw it. Disable your browser subscriptions from the sensor workspace or revoke permission in browser settings. Location membership controls access to the underlying evidence.
- Enquiries: your signed-in account identifier and email, contact name, request type, quantity, requirements and any delivery information you choose to include. Status updates and customer-visible replies are saved in the request history.
- Security information: hosting and security services receive connection information such as IP address, browser details, request time and pages requested. The request workspace applies account and input limits to reduce misuse.
- Examples and choices: sample updates, pack selections and creator-invitation text are held in the open page’s memory. They reset when the page reloads and are not saved as customer records. Pack choices are sent only when you submit an enquiry.
- Privacy choice: a small browser-storage item remembers that you chose essential-only operation. It contains no name, email or visitor identifier.
If you use the share or copy buttons, your device handles the sharing action you select. A copied example link can include the creator or crew text you entered. Do not include private information in a shareable example.
Why we use it
We use enquiry details to respond, assess your requested setup and prepare a quote. Where you request a contract, this supports steps taken at your request before entering that contract. Otherwise, responding to your enquiry and keeping an accurate correspondence record are our legitimate interests. Security processing supports our legitimate interest in protecting the service and preventing abuse. Information needed for legal obligations may be retained for that purpose.
An enquiry is not a marketing subscription. We do not sell enquiry information or share it for another organisation’s own marketing. The marketing examples do not make automated decisions with legal or similarly significant effects about you.
Who receives it
Saved requests are available to the submitting account and the designated RipTags administrator. Replies appear in the request workspace; automatic email and SMS delivery are not enabled. Hosting, delivery, database and email service providers help operate the site and correspondence. The marketing page is served through ChatGPT Sites and Cloudflare infrastructure; the QR workspace and new request records use the Site’s database and private file storage. The separate legacy pack and sports account service uses Render. Access should be limited to the people and providers needed to handle the request.
Providers can process information outside the European Economic Area. You can ask the team which locations and transfer arrangements apply to your information. The applicable provider terms and any required transfer safeguards must be considered for the particular service.
How long it is kept
We keep enquiry information while needed to answer the request, prepare or follow up a quote and maintain necessary correspondence. Retention also depends on whether the enquiry becomes a customer relationship, an unresolved issue or a record required by law. You can request deletion; the team will explain if a legal or other valid reason requires any part to be retained.
Raw sensor readings have a 90-day retention target and a 200,000-record allowance per location. Expired readings are removed in bounded background maintenance batches, so deletion can follow the target time. Alert evidence snapshots, approved reference samples, actions and audit history remain with the location. Export raw readings before the retention period expires.
Sample-page entries last only in the open page. The privacy-choice item expires after six months or can be removed sooner through your browser settings. Unused invitation links expire after seven days. Archiving retains a location and its history; a separate deletion request is required for erasure.
Accounts, QR families and other websites
The QR-family workspace uses Sign in with ChatGPT to identify your account. Its records and photos are held in the site’s database and file storage. Export downloads the location’s records and evidence relationships as JSON; photos are separate files. Archiving keeps the records and can be reversed. To request permanent deletion, use the contact routes below. Creating a tag-pack account, claiming purchased packs and using a live sports session take place in the separate shared customer service. Those activities involve additional account and content information and should be read alongside the notices and terms shown there. Payment checkout is not enabled on this marketing page.
Links to JumpXn, GeoVeracity, RippleXn and external services take you to their websites. Their notices and device-storage choices apply there. A link does not automatically share your private RipTags records.
Your choices and rights
Subject to the conditions in data protection law, you can ask for access, correction, erasure, restriction, portability or object to processing based on legitimate interests. Where processing depends on consent, you can withdraw it. We may need proportionate information to verify a request and protect the record from unauthorised disclosure.
We aim to answer rights requests within one month. If an extension is permitted and needed, we will explain it. You can complain to the Irish Data Protection Commission or your relevant supervisory authority.
Providing enquiry information is voluntary, but we need a reply address and enough details to handle the enquiry. Delivery details are needed for a pack quote. Please do not send passwords, payment-card details or sensitive records through the general enquiry form.
Public contact enquiries
No account is required to contact us. We store your name, email, selected interest, optional message, reference and submission time in the private RipTags request database so the authorised team can handle your enquiry. Contact details are self-reported and not email-verified. We apply submission limits to reduce abuse. Submitting does not subscribe you to marketing, create an account or send an automatic email. Existing retention and privacy-request arrangements below apply.
Make a privacy request
Use the contact form to ask about your information, request deletion or correction, or ask for controller and provider details. Include enough context to locate the enquiry without sending sensitive documents.
Open the contact form →If the form is unavailable, contact the team through RippleXn’s contact page. This site does not publish an individual’s name or email address as its contact route.