Data Protection & AI Usage Disclosure

Client Data We May Process

Depending on the project, Ravenence may process contact details, business requirements, website content, CRM fields, lead data, analytics events, workflow data, technical access details, and support conversations.

• We ask clients to share only the data needed for the agreed project.
• Sensitive data requires a written handling plan before it is shared.
• Project data is used for discovery, implementation, testing, support, and improvement of the agreed solution.

Collection, Storage, and Processing

Client data may be collected through forms, calls, emails, booking tools, chat tools, shared workspaces, project systems, and connected platforms. Storage locations depend on the tools selected for a project.

• Access is limited to team members and providers who need the data for delivery.
• We prefer secure, reputable platforms with access control, authentication, and audit-friendly records.
• We avoid unnecessary copies and remove or return project data when retention is no longer needed.

AI Usage Disclosure

Ravenence may use AI systems to assist with research, chat responses, content drafting, code support, automation design, data structuring, and internal productivity.

• AI-generated outputs may contain mistakes, omissions, outdated information, or unsuitable recommendations.
• AI outputs should be reviewed before publication, client delivery, legal use, financial use, or operational reliance.
• We do not intend AI tools to make final decisions about clients, users, employment, eligibility, credit, legal rights, or other high-impact matters without human review.

Secure Data Handling Procedures

We use practical safeguards to reduce privacy and security risk during website, app, CRM, analytics, and automation projects.

• Least-privilege access for project tools and data.
• Secure credential exchange where possible instead of sending secrets in plain text.
• Separation of production credentials from demo, testing, and development work where feasible.
• Review of automations before launch to reduce accidental exposure, unsafe routing, or unintended data sharing.

International and GDPR-Style Transparency

For international clients, Ravenence aims to document the purpose of processing, categories of data, providers involved, access rules, retention expectations, and consent requirements before launch.

• European users may have rights to access, correct, delete, restrict, port, object to, or withdraw consent for certain personal data processing.
• Some providers may process data outside your country. We consider provider terms, security posture, and project needs when choosing tools.
• Clients remain responsible for their own notices, lawful bases, records, and jurisdiction-specific compliance unless a formal compliance scope is agreed.

User Consent and Automated Systems

Optional website tools are disclosed through the cookie banner and policy. Live chat is not loaded until support-tool consent. The booking calendar loads on the contact page so visitors can schedule directly.

• Visitors can change cookie choices through Cookie Settings.
• Automated systems should be clearly disclosed in client-facing workflows where they materially affect users.
• Automation should include human handoff paths for sensitive, unclear, or high-value interactions.

Questions or Data Requests

Contact contact@ravenence.com for privacy, AI usage, or data protection questions. This disclosure is general website transparency and does not replace a formal data processing agreement where one is required.