Data We Collect
Contact data, verification photos submitted for onboarding, service metadata, referral IDs, and API telemetry.
Policy
Privacy Policy
This Privacy Policy explains how Ronan Hayes Management collects, uses, shares, stores, and protects information across the full service ecosystem, including web properties, referral systems, tracking routes, and API services.
Quick Summary
This summary is simplified for readability. The full legal policy below controls if any summary text differs.
How We Use It
Operations, support, security, anti-fraud controls, analytics, and referral attribution integrity.
Who Gets Access
Authorized operators and service providers with a documented operational or legal need.
Your Options
You can request access, correction, deletion, or clarification by contacting the policy address.
1. Scope and Applicability
This Privacy Policy applies to personal information and related operational data processed through Company websites, creator subdomains, contact workflows, short-link routing, campaign attribution systems, and API endpoints. It applies to direct users and indirect interactions routed through links or integrations.
2. Data Controller and Contact
Ronan Hayes Management is responsible for policy administration and operational decision-making for covered systems. Privacy questions, rights requests, and dispute notices should be sent to contact@ronanhayes.net.
3. Information We Collect
3.1 Identity and Contact Data
- Name, stage name, email address, communication preferences, and intake form responses.
- Support communications and correspondence related to onboarding, compliance, or dispute handling.
3.2 Operational and Technical Data
- Timestamps, path/route requests, request outcomes, and service interaction records.
- Network, browser, or device signals used for abuse detection and performance troubleshooting.
3.3 Referral and Promotion Data
- Campaign IDs, referral IDs, source tags, conversion markers, and attribution calculation events.
- Integrity and anomaly signals used to detect fraudulent or manipulated referral behavior.
3.4 API and Security Telemetry
- Endpoint path, method, response status, authentication metadata, and rate-limit events.
- Security logs relevant to key misuse, unauthorized access patterns, and incident investigation.
3.5 Application Verification Images
- When you submit a management application, uploaded verification photos are processed for identity matching.
- Verification outputs may include match status, similarity/confidence score, and verification timestamp.
4. Sources of Information
- Information you provide through forms, email, support messages, and direct interactions.
- Information generated automatically through access to sites, links, and API endpoints.
- Information received from infrastructure vendors and analytics/security tools used to operate services.
5. Purpose and Legal Basis for Processing
Processing may occur under one or more legal bases depending on jurisdiction, including contractual necessity, legitimate interests, legal obligations, and consent where required.
- To provide site functionality, creator management operations, and service support.
- To authenticate users, protect credentials, and preserve system availability and integrity.
- To perform application identity checks and reduce impersonation or onboarding fraud risk.
- To measure referral and campaign outcomes and prevent fraudulent attribution behavior.
- To investigate incidents, enforce policies, and comply with legal and regulatory requirements.
6. Branch-Specific Processing Notes
Branch A: Main Site and Corporate Pages (ronanhayes.net)
- Processes contact form submissions, policy interactions, and browsing analytics.
- Application workflows may process verification photos and related match outputs.
- Logs are used for site performance, abuse detection, and documentation of policy changes.
Branch B: Client Subdomains and Link Trees (e.g., angel.ronanhayes.net)
- Processes page interaction events and outbound link engagement metrics.
- May process report evidence for impersonation, unauthorized use, or account abuse claims.
Branch C: Promo and Referral Systems
- Processes campaign metadata, attribution paths, conversion markers, and anti-fraud indicators.
- Stores evidence used to validate or invalidate suspected manipulated referral events.
Branch D: Tracking and Redirect Layer (track.ronanhayes.net)
- Processes short-link route traffic, destination mapping metadata, and safety signals.
- Records may be retained for abuse response and link integrity investigations.
Branch E: API Platform (api.ronanhayes.net)
- Processes request telemetry, token events, and operational performance metrics.
- Security logs may be retained to support incident response, auditing, and enforcement actions.
7. Sharing and Disclosure
- Data may be shared with hosting, analytics, communication, and security vendors under operational controls.
- Verification processing may use contracted cloud and identity-matching infrastructure providers.
- Data may be disclosed to legal authorities where required by law, legal process, or safety obligations.
- Data may be disclosed in good-faith response to fraud, abuse, or active security incidents.
- Data is not sold as a standalone commercial dataset.
8. International Processing and Transfers
Services may be operated using infrastructure in multiple regions. Where information is transferred across jurisdictions, the Company uses reasonable contractual and technical safeguards consistent with applicable law.
9. Data Retention
Retention periods vary by data type, legal requirements, security needs, and business purpose. Some records may be retained longer where necessary to investigate abuse, defend legal claims, or satisfy regulatory duties.
- Contact records: retained for support continuity and contractual follow-up.
- Referral and tracking logs: retained for attribution reconciliation and anti-fraud review.
- API/security telemetry: retained for monitoring, incident response, and auditing controls.
- Verification photos: processed for live comparison and not retained on the site after verification.
- Verification metadata: match outcomes and timestamps may be retained for abuse prevention and audit.
- Resolved complaints: retained for legal defensibility and recurring-abuse prevention.
10. Security Safeguards
- Access controls, role restrictions, and authentication requirements for administrative actions.
- Monitoring and logging systems to detect misuse, anomalies, and unauthorized attempts.
- Procedural controls for incident handling, containment, and post-incident documentation.
- Credential rotation and endpoint control adjustments when risk indicators require containment.
11. Your Rights and Requests
Subject to applicable law and verification requirements, you may request access, correction, deletion, or clarification regarding your personal data and associated tracking records.
- Requests should include domain, URL/path, known identifiers, and date range where possible.
- Identity verification may be required before sensitive records are disclosed or modified.
- Certain records may be retained where legally required or necessary for fraud/security defense.
12. Children and Restricted Use
Services are intended for lawful adult use. The Company does not knowingly process prohibited child sexual abuse material and maintains an immediate escalation protocol under Section 4 of the Reports & Complaints Policy.
13. Automated Decisioning and Integrity Controls
Automated systems may flag suspicious referral, tracking, API, or verification activity for fraud and abuse review. Automated verification outcomes may block application submission when requirements are not met. Final enforcement decisions may include manual review where needed for legal or operational accuracy.
14. Policy Updates
This Privacy Policy may be revised to reflect legal requirements, service changes, or updated controls. Continued use of covered services after updates indicates acceptance of the revised policy.
15. Contact
Privacy questions and rights requests can be submitted to contact@ronanhayes.net.