Privacy

TBD — LEGAL CONFIRMATION REQUIRED. The future CRAYS.pro controller, address, privacy contact and any representative or data-protection contact must be confirmed from the approved legal record. No Gym, venture or Association identity is substituted.

A production public site may need to process request and security data required to deliver and protect the service, such as route, time, response and security-event information. Exact fields, legal basis, recipients and retention remain subject to the confirmed production architecture and legal review.

The current CRAYS.pro Contact preview keeps a draft in the open page only for local review. It does not send or store the submitted content. A later sender, destination, retention rule and privacy notice require their own approval before transmission is enabled.

The target CRAYS.pro account journey may process the minimum identifiers, authentication state and security/session data needed for sign-in and account protection. Authentication does not grant a business relationship, role or record scope. Exact production purposes and provider disclosures remain later-gated.

Property, Candidate, Deal, Funding, Investor, Vendor and Team contexts remain separate relationship scopes. CRAYS authorises every private view separately for the approved relationship and scope. Public browsing, account creation or login alone does not expose private records, documents, notes or evidence.

Public summaries and public-safe intake are distinct from private Property Opportunity, Deal Package and diligence evidence. Private material is released only to an authorised relationship and purpose. It is not made public, merged across relationships or reused automatically.

Coffee, Retail, Gym and Clubs keep venture-specific customer journeys, purposes and applicable notices. A future shared application target or CRAYS.pro login does not silently combine customer histories, memberships, bookings, purchases, hospitality records or permissions across ventures.

TBD — PRODUCTION INVENTORY REQUIRED. Necessary session, security or journey-state storage and any optional analytics or marketing technologies must be inventoried by purpose. Optional technology may not be represented as active or consented until the approved production inventory and consent path permit it.

TBD — PROCESSOR AND TRANSFER REVIEW REQUIRED. No speculative provider list is published here. Production recipients, processors, international-transfer locations and safeguards must match the verified deployment and approved contracts before release.

TBD — PURPOSE-SPECIFIC SCHEDULE REQUIRED. Each processing context needs a verified retention trigger, period and deletion or anonymisation rule. Evidence that remains lawfully retained does not become current, complete, transferable or public.

TBD — LEGAL REVIEW REQUIRED. Applicable data-subject rights, identity-verification safeguards, complaint authority and response channel will be stated for the confirmed controller and jurisdiction before release.