Privacy Policy
This Privacy Policy describes how RlyRo LLC handles information when you use ChargeEnforcer.
See also Terms of Service.
1. Who We Are
RlyRo LLC ("RlyRo," "we," "us," or "our") operates ChargeEnforcer. This Privacy Policy explains how we collect, use, share, and protect information when you visit chargeenforcer.com or use ChargeEnforcer through the Ring App Store.
Contact: contact@chargeenforcer.com
2. Scope
This Privacy Policy applies to our marketing website, product onboarding flows, customer support interactions, and the ChargeEnforcer service integrated with Ring. It does not cover third-party services such as Ring, Amazon, or other platforms that maintain their own privacy policies.
3. Information We Collect
We may collect the following categories of information:
- Account and subscription information, such as name, email address, organization, Ring account identifiers, subscription status, plan type, and trial dates.
- Ring integration data, such as device names, device identifiers made available through Ring APIs, motion or event metadata, and video or image data processed to provide detection and alerting features.
- Configuration data you provide, such as EV zone boundaries, alert rules, escalation settings, and property labels.
- Usage and diagnostic data, such as feature usage, log data, performance metrics, crash reports, and support tickets.
- Marketing and communications data, such as campaign attribution, form submissions, email engagement, and customer inquiry content.
- Technical data from your browser or device when you visit our website, such as IP address, browser type, pages viewed, and referral source.
4. Purposes for Processing Customer Data
We process customer data only to provide and improve the EV charging compliance monitoring service you configure. We do not use Ring data for advertising, resale, unrelated analytics, or separate products.
How each data element is used:
- OAuth tokens and Ring account ID — authenticate Ring API calls for linked properties and maintain the integration.
- Webhooks, snapshots, and short clips — trigger and support violation detection for configured cameras and zones.
- Zones and rules — define monitoring scope, thresholds, and alert behavior.
- Incident and presence records — power alerts, dashboards, and enforcement workflows you enable.
- Model improvement (unless you opt out) — de-identified snapshots, clips, zone context, AI-generated labels, and confirmed, resolved, or dismissed incident outcomes may be used to train, fine-tune, and evaluate ChargeEnforcer detection models as described in Section 7.
- Account, subscription, support, security, and legal data — operate the Service, respond to requests, prevent fraud, and comply with law.
5. Data Minimization
We limit collection and processing to what is needed for the EV compliance service you configure:
- Opt-in cameras and zones only — we process Ring data only from devices and detection zones you explicitly configure in ChargeEnforcer.
- Event-driven analysis plus limited presence polling — not continuous 24/7 recording or archiving of your full Ring video library.
- No facial recognition or biometric identity systems — we do not use the Service to identify individuals or build biometric profiles.
- Training minimization — training datasets exclude OAuth tokens and direct account identifiers where practicable; model-training opt-outs are honored within 30 days as described in Section 12.
- Retention targets and user controls — pause zones, unlink Ring, and submit deletion requests as described in Section 10 and Section 13.
6. AI and Video Processing
ChargeEnforcer uses automated vision AI to process camera-related data received through Ring APIs, including snapshots, short clips, and related metadata, to detect gas-car blocking, overstays, tampering, and other EV compliance conditions you configure.
Processing may occur in real time or near real time depending on device, network, and service configuration. Real-time inference may use third-party AI APIs such as xAI Grok under provider terms that restrict use of API inputs for general model training.
We do not use ChargeEnforcer to create a continuous archive of your full Ring video library. We retain processed event data, thumbnails or frame extracts associated with incidents, webhook payloads, and related metadata according to the retention periods in Section 10.
Video metadata such as device ID, timestamps, event type, and processing status supports detection, audit logs, and — unless you opt out — aggregated model evaluation and training quality metrics. Full webhook payloads are retained per our retention schedule; they are not deleted immediately after processing.
7. Use of Customer Data for AI Model Training
Yes — Ring-derived data may be used to train and improve ChargeEnforcer detection models.
ChargeEnforcer uses automated vision AI to detect EV charging violations. To improve accuracy over time, we may use Ring-derived snapshots, short clips, zone configuration, AI-generated labels, and manager actions such as confirmed, resolved, or dismissed incidents to train, fine-tune, and evaluate our own detection models, including classical machine learning, deep learning, and LLM-assisted vision pipelines used for EV compliance.
Training uses data only from cameras and zones you explicitly configured. We do not use Ring data for unrelated products, advertising, or resale.
We do not use this data to identify individuals, perform facial recognition, or sell data to third parties.
Real-time inference may use third-party AI APIs such as xAI Grok under provider terms that restrict use of API inputs for general model training. We do not authorize those providers to use your data to train their general-purpose models beyond what their contract permits.
You may opt out of ChargeEnforcer model-improvement use of your data at any time. See Section 12. Opting out does not disable core violation detection; it stops your Ring-derived content from being added to future training datasets.
- Anonymization and de-identification — before use in model training we apply minimization and de-identification steps where practicable, including removing or not ingesting account email, name, and Ring OAuth tokens from training sets; excluding Ring account IDs and internal user IDs from training labels where possible; using zone geometry and violation labels rather than property or manager identifiers; and restricting training access to authorized personnel in secured environments.
- Incidental imagery — footage may still contain vehicles, persons, or legible license plates visible in the camera frame. We do not use training to identify individuals or build biometric profiles.
- Historical model weights — opt-out applies prospectively. Data already incorporated into a trained model snapshot cannot always be extracted from historical model weights.
9. Sub-Processors and Third-Party Service Providers
We use service providers that process personal information on our behalf to operate ChargeEnforcer. These providers act as sub-processors under contractual obligations requiring confidentiality, security, and use only for our instructions.
Our current sub-processors and service categories include:
- Ring and Amazon Web Services — device integration, authentication, and delivery of camera event data through Ring APIs.
- xAI (Grok) and other AI inference providers — real-time vision analysis under API terms that restrict provider use of inputs for general model training.
- Cloud hosting and application infrastructure providers — hosting the ChargeEnforcer application, APIs, and related services.
- Database and storage providers — storing account, configuration, incident, and operational data.
- Email and customer-support providers — sending service messages and handling support requests.
- Website analytics and marketing providers — measuring traffic and campaign performance on chargeenforcer.com and related marketing pages only.
- We may update this list as our vendors change. Material additions that affect how we process Ring-related customer data will be reflected on this page with an updated Last updated date.
10. Data Retention Periods
We retain information only for as long as needed for the purposes described in this Privacy Policy, unless a longer period is required or permitted by law. Typical retention periods are:
You may request earlier deletion as described in Section 11. Backup copies may persist for a limited period before being overwritten.
Deletion of ChargeEnforcer data does not delete data held by Ring in your Ring account. You may need to manage Ring-side video history separately through Ring.
- Account and subscription data — for the life of your account, then up to 30 days after verified deletion, except records we must retain for billing, tax, fraud prevention, or legal compliance.
- Configuration data such as zones, alert rules, and property labels — for the life of your account, then deleted with your account unless retained in backups for up to 90 days.
- Detection events, incident logs, and associated metadata — 90 days by default, or up to 12 months if your plan or settings enable extended incident history.
- Incident-related thumbnails or frame extracts — for the same period as the related incident record, then deleted or de-identified.
- Transient video or image processing buffers — only as long as needed to perform detection, typically seconds to minutes, unless saved as part of an incident record you retain.
- Support tickets and correspondence — up to 3 years after closure.
- Billing and transaction records — up to 7 years where required for accounting, tax, or legal purposes.
- Security, diagnostic, and application logs — up to 90 days, unless needed longer to investigate an incident.
- Marketing website analytics — according to each provider's configured retention, typically 14 to 26 months for analytics cookies and event data.
11. Privacy Rights and Data Subject Requests
Depending on your location, you may have rights to access, correct, delete, export, or restrict processing of your personal information, and to opt out of certain processing or marketing.
California residents may have additional rights under the CCPA/CPRA, including the right to know, delete, correct, and opt out of certain sharing for cross-context behavioral advertising, subject to applicable exceptions.
To submit a data subject access request (DSAR), deletion request, correction request, or other privacy request, email contact@chargeenforcer.com with the subject line "Privacy request" and include the email address associated with your ChargeEnforcer or Ring-linked account, the request type, and enough information for us to verify your identity.
We will acknowledge receipt within 10 business days where required by law and respond within the timeframe required by applicable law, typically within 45 days. We may extend that period where permitted by law and will notify you if an extension is needed.
We may deny or limit requests where permitted by law, such as when fulfilling the request would impair the rights of others, interfere with security or fraud prevention, or conflict with legal retention obligations. If we deny a request, we will explain the reason and any appeal rights available to you.
12. Opt-Out Mechanisms
You may opt out of the following processing using the methods below:
Model training opt-out — email contact@chargeenforcer.com with the subject line "Opt out of AI training." We stop adding your Ring-derived content to new training datasets within 30 days of a verified request. Core detection, alerts, and incident logging continue unchanged.
Effect of training opt-out — opting out stops model-improvement use only. It does not unlink Ring, pause monitoring, or delete existing incident records unless you take those steps separately. Opt-out applies prospectively; data already incorporated into historical model weights cannot always be extracted.
- Marketing emails from RlyRo — use the unsubscribe link in any marketing email or email contact@chargeenforcer.com with the subject line "Unsubscribe".
- Website analytics and advertising cookies — use your browser cookie settings and any industry opt-out tools described in Section 18.
- Ring-side video storage, sharing, and device settings — manage through the Ring app and your Ring account settings. ChargeEnforcer cannot change Ring account settings on your behalf.
13. When Humans May View Customer Data
ChargeEnforcer is designed to process camera-related data automatically. Authorized RlyRo personnel or contractors may view customer data only in the limited circumstances below:
Personnel with access are subject to confidentiality obligations and access controls. We do not routinely monitor live camera feeds for entertainment or unrelated purposes.
- When you request customer support and viewing the relevant incident, configuration, or diagnostic data is reasonably necessary to troubleshoot your issue.
- During quality assurance, fraud prevention, or security investigations involving specific incidents or accounts.
- When reviewing incident-related frames, clips, or confirmed or dismissed violation outcomes for detection accuracy or model training, unless you have opted out of model training as described in Section 12.
- When required by law, legal process, or to protect the rights, safety, or security of customers, RlyRo, Ring users, or the public.
14. How You Control and Review Your Data
You can review and control your data through the following channels:
- Ring app — view, download, share, and delete full video recordings stored in your Ring account, manage device settings, and control Ring subscription features.
- ChargeEnforcer app — review detection zones, alert rules, linked devices, incident history, and enforcement settings configured for your property.
- Incident records — review timestamps, detection results, alert history, and any thumbnails or frame extracts saved with incidents within the ChargeEnforcer app for as long as those records are retained under Section 10.
- Pause or remove monitoring — pause detection zones or unlink Ring in ChargeEnforcer to stop new processing for those cameras.
- Account deletion — request deletion of your ChargeEnforcer account and associated personal data by emailing contact@chargeenforcer.com. Ring account and video data must be managed separately in Ring.
- Privacy requests — use Section 11 to access, export, correct, or delete personal information we hold.
- Model training opt-out — use Section 12 to stop future use of your Ring-derived content for ChargeEnforcer model improvement.
15. Changes to AI Capabilities
We may update ChargeEnforcer detection models, alert logic, supported violation types, third-party AI providers, accuracy improvements, and related AI features from time to time.
When we materially change AI providers, violation types, or how customer data is used for model training, we will update this Privacy Policy with a revised Last updated date, show in-app notice where appropriate, and email the account address for significant changes.
Continued use of the Service after notice of material AI-related changes constitutes acceptance of the updated processing described in the then-current Privacy Policy, unless applicable law requires a different consent mechanism.
16. Security
We use reasonable administrative, technical, and organizational safeguards designed to protect information. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
19. Children's Privacy
The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, contact us and we will take appropriate steps to delete it.
20. U.S. Focus
The Service is intended for users in the United States. If you access the Service from outside the United States, you do so at your own risk and are responsible for compliance with local laws.
21. Changes and Contact
We may update this Privacy Policy from time to time. We will post the updated policy on this page and revise the Last updated date.
Privacy questions or requests may be sent to contact@chargeenforcer.com.