PRIVACY / 05
Privacy policy / last updated October 2026
This page explains how dravellagency handles project enquiries, saved drafts and administrator access.
When online sending is available and you submit an enquiry or brief, your name, email, company, phone, service selections, project message and any brief answers are sent securely to dravellagency's Supabase-backed CRM. dravellagency uses these details to respond to your request and manage the resulting project relationship. A successful send is shown only after the server confirms the enquiry was saved.
If the form says “Save enquiry” or “Save brief”, it saves a draft in your own browser rather than sending it. In-progress brief answers may also be saved locally. Drafts are not automatically uploaded when you return. You can remove local drafts through your browser's site-data settings.
CRM records are restricted to authorised administrators through Supabase Auth and database access policies. Anti-abuse checks validate submissions and use limited, hashed network identifiers for rate limiting; raw network addresses are not saved in CRM enquiry records. No system can guarantee that every spam attempt will be blocked.
Administrator sign-in uses an email address and password through Supabase Auth. Browser session storage supports the signed-in session; signing out clears the dashboard's session and loaded records. The website does not collect payment-card details. Finance entries are an internal project tracker, not a payment-processing service.
To ask about an enquiry or request correction or deletion, contact dravellagency using the Instagram link in the footer and include your enquiry reference when available. Do not send passwords or other sensitive account credentials.
Supabase provides authentication and enquiry storage. Featured media may load from Cloudinary. An anti-bot verification provider may be enabled for forms. External links, including Instagram, lead to services with their own privacy practices.