All Applicable Policies
This hub includes every policy that applies to Hard Coded Real Estate.
Use this page for privacy, terms, communications, AI, accessibility, fair housing, antitrust, security, sub-processors, disclaimer, copyright, DMCA, and acceptable content guidance.
Sub-processors
The third-party service providers and platform categories that may process information to host, secure, deliver, support, analyze, automate, and improve Hard Coded Real Estate services.
- Last updated
- July 22, 2026
- Applies to
- Website visitors, leads, prospects, clients, administrators, portal users, learners, event attendees, brokerage users, association users, support contacts, and client-approved workflow participants.
Purpose and Scope
Hard Coded Real Estate, LLC uses carefully selected third-party service providers and platform vendors to provide, secure, maintain, support, analyze, and improve our websites, portals, lead workflows, communications, CRM connections, AI-assisted workflows, hosting, logging, and related services.
A sub-processor is a third party that may process personal information, business information, technical logs, or service data on our behalf. Sub-processors are expected to process information only for authorized purposes and under appropriate contractual, technical, and organizational safeguards.
Current Sub-processor Categories
The providers below are representative of the categories and vendors that may be used across the public website, client implementations, integrations, support workflows, analytics, communications, and approved service configurations. Not every provider is active for every customer, product, or page.
| Provider or Category | Purpose | Data Processed | Status |
|---|---|---|---|
| Cloudflare | DNS, CDN, caching, security filtering, performance services, bot protection, and optional web analytics/RUM. | IP address, request metadata, device/browser signals, security logs, performance events, and cookie or consent metadata where configured. | Active where configured |
| Coolify, VPS, and hosting providers | Application hosting, deployment orchestration, container runtime, backups, uptime, and operational infrastructure. | Website and platform content, operational metadata, server logs, deployment metadata, and technical diagnostics. | Active |
| GitHub | Source control, deployment triggers, code collaboration, issue tracking, version history, and release coordination. | Repository content, commit metadata, deployment references, project notes, and authorized collaborator information. | Active |
| app.gr0.ai CRM or approved CRM endpoints | Lead intake, demo routing, contact management, support handoff, sales follow-up, and client-approved workflow routing. | Contact details, organization information, role, message content, consent metadata, UTM data, support context, and follow-up status. | Active when configured |
| Email and SMS providers, including Twilio where configured | Transactional messages, service notices, support replies, optional marketing communications, SMS opt-in/opt-out handling, and message deliverability. | Name, email, phone number, message content, consent records, opt-in and opt-out status, delivery metadata, and support context. | Active when configured |
| Analytics and advertising platforms, including Google Analytics 4 and Meta Pixel where configured | Website analytics, campaign attribution, conversion measurement, retargeting audiences, performance review, and product improvement. | Cookie or pixel identifiers, device/browser data, page/event data, referrer, UTM parameters, approximate location, and consent preferences. | Optional/configured |
| AI providers, including OpenAI or comparable approved model providers where configured | AI-assisted drafting, summarization, search, classification, support triage, QA, accessibility review, workflow automation, and knowledge retrieval. | Prompts, approved context, uploaded or selected content, outputs, usage metadata, and review notes. Sensitive data should not be submitted unless an approved agreement and secure workflow permit it. | Optional/configured |
| Payment processors where approved for client workflows | Invoice payment, payment processing, receipts, fraud prevention, and billing support for approved client or platform workflows. | Billing contact information, customer identifiers, payment status, receipt metadata, billing ZIP code, and transaction metadata. We do not store raw card numbers or CVV codes. | Optional/configured |
| Authentication and SSO providers where configured | Login, account verification, identity management, role assignment, single sign-on, access control, and account security. | Account identifiers, email address, organization membership, role data, authentication metadata, session metadata, and security events. | Optional/configured |
| Monitoring, logging, backup, and security tools | Error detection, uptime monitoring, vulnerability review, backups, audit trails, incident response, abuse prevention, and platform reliability. | Technical logs, IP/device metadata, error traces, service events, backup snapshots, access logs, and operational alerts. | Active/optional by environment |
Selection, Safeguards, and Review
We evaluate sub-processors based on the service they provide, security posture, operational need, data sensitivity, reliability, contractual controls, support expectations, and whether the provider helps us deliver a faster, safer, more accessible, or more reliable experience.
Where appropriate, safeguards may include access controls, encryption in transit, least-privilege access, logging, data minimization, contractual processing limits, incident-response expectations, retention practices, vendor review, and separation between public website data and private client platform data.
Changes and Customer Notice
We may add, replace, or remove sub-processors as our services, infrastructure, integrations, security needs, and client-approved workflows evolve. We update this page when material changes are made to the public sub-processor list or categories.
Customers with signed agreements may have separate notice, objection, data processing, or vendor-review rights stated in those agreements. If a signed agreement conflicts with this public page, the signed agreement controls for the covered customer relationship.
Data Location and Transfers
Sub-processors may process or store information in the United States or other regions depending on the provider, infrastructure, customer configuration, backup needs, and support requirements. We use commercially reasonable safeguards and vendor controls designed for the type of data and service involved.
Client organizations are responsible for telling us if a workflow requires specific residency, retention, contractual, MLS, association, brokerage, or regulatory handling before implementation.
Questions and Vendor Requests
Questions about sub-processors, vendor categories, privacy handling, AI providers, analytics, communications vendors, or client-specific data processing should be sent through the policy contact form. Include the product, workflow, vendor category, and any contractual requirement that applies.
Contact
Questions about any policy, privacy requests, accessibility feedback, AI policy questions, communications opt-out issues, fair housing or antitrust concerns, security reports, copyright notices, and legal notices can be sent to Hard Coded Real Estate, LLC.
Hard Coded Real Estate, LLC319 Clematis Street
West Palm Beach, FL 33401
(561) 316-7712
Policy contact form