Privacy Policy

Data CREN collects

• Contact data such as name, email, phone number, company, role, and message.
• Account data such as email, password hash, member profile, role, interests, preferred area, tier, and status.
• Lead data such as persona, area, budget, timeline, property details, business details, capital-interest details, source page, consent, and status.
• Advertiser and business data such as business name, legal entity name, public contact details, service areas, credentials, claimant authority, dispute contact, creative assets, packages, and campaign details.
• Usage data such as page path, referrer host, event name, sanitized event payload, and daily visitor hash where analytics are enabled.
• Affiliate data such as partner slug, source path, and referrer when a user follows an affiliate redirect.

Sources of data

• Information you enter into forms, accounts, profiles, subscriptions, advertising inquiries, corrections, and business listing requests.
• Automated site interactions such as page views, conversion events, email engagement where supported, and affiliate redirects.
• Public records, official sources, business websites, data providers, advertisers, profile claimants, and service providers.

How data is used

• Operate the site, publish reporting, maintain accounts, process subscriptions, route requests, respond to messages, and manage advertising.
• Review profile claims, credentials, disputes, corrections, and sponsored-placement requirements.
• Measure content, campaigns, area interest, and conversion funnels using aggregated or limited operational analytics.
• Prevent abuse, enforce policies, comply with law, maintain records, and improve product quality.

Sharing and disclosure

CREN may share information with service providers that help operate hosting, database, email, analytics, payment, notification, security, and customer-support functions. CREN may share lead details with a provider, sponsor, advertiser, or profile owner only when the user request and site disclosure support that routing.

Campaign reporting should be aggregate unless a user has submitted a lead intended for a specific recipient. CREN should not sell raw contact lists. Whether any advertising or analytics activity is a sale or share under state privacy laws should be confirmed before public use.

Cookies and analytics

CREN currently has first-party session cookies for admin and member login. The audited pageview and activation endpoints use a daily visitor hash and do not store raw IP addresses or full user agents in those tables. Any third-party analytics, pixels, email tracking, or ad targeting must be inventoried in the Cookie Policy before launch.

Choices and requests

• Newsletter recipients should be able to unsubscribe from marketing email.
• Users should be able to request access, correction, deletion, or restriction where required by law or adopted voluntarily by CREN.
• Business and profile owners should be able to request corrections, claim review, dispute review, downgrade, or removal under the applicable profile policy.

Retention, security, and minors

• Retention periods should be defined by data type before launch-grade use.
• CREN should protect data with reasonable administrative, technical, and organizational safeguards, but no system can be guaranteed perfectly secure.
• CREN should not knowingly collect personal information from children under 13. Housing and business services are intended for adults and authorized representatives.