This notice describes the website’s current inquiry workflow. Please avoid including confidential business material or sensitive personal information in your inquiry.
Information you choose to provide
The consultation form asks for your name, business name, email address, optional phone number, service of interest, and a description of your needs. HEVKAR uses this information to review your inquiry, contact you, and discuss potential support.
How an inquiry is sent
When online inquiries are available, the form sends your details to HEVKAR by email through Resend. A success message confirms that the email service accepted the inquiry for delivery. It cannot guarantee inbox arrival or a response time. When online inquiries are unavailable, the form tells you and does not send or store your inquiry.
Consultation requests and appointments
The separate consultation request form asks for your name, email, business name, optional phone, requested service, brief business needs, and a preferred date, time, and time zone. HEVKAR saves these details in its own persistent database so authorized administrators can review and manage the request. Customer details and internal notes are encrypted in storage. A saved request is not a confirmed appointment; only a HEVKAR administrator can approve it.
Administrators can record a proposed time, appointment status, internal notes, and manual follow-up. Changes are recorded in a private audit history. No external scheduling provider receives these requests, and no automatic email, reminder, calendar invitation, or online meeting link is sent by this system. Keep your saved reference for manual follow-up.
Security and spam prevention
When configured, Cloudflare Turnstile checks for automated submissions. A rate limiter temporarily uses a hashed network address to limit repeated requests. The temporary rate-limit record expires after 10 minutes and does not contain the inquiry text. Security providers and the hosting provider may process technical request information to deliver and protect the service.
The native consultation form uses server-side validation, a honeypot, a signed form token, request-size limits, duplicate prevention, and database-backed rate limiting. Consultation and staff sign-in limits use keyed hashes rather than storing raw network identifiers in the rate-limit table. Expired limits are removed on subsequent requests. Staff access uses essential, secure session cookies; these are not advertising cookies.
Storage and tracking
General inquiries remain separate and, when configured, are handled through email. Consultation requests, administrative notes, and audit history are retained in HEVKAR’s private database and protected backups until HEVKAR removes them under its operating policy. The current application does not automatically delete these records. It uses no marketing analytics or advertising cookies. Fonts and design assets are served locally. Customer content is not intentionally written to application logs.
Your choices
You can choose not to submit the form. If you have already contacted HEVKAR, use your established conversation with the team to ask about the information you provided or request its correction or removal. For a consultation request, include its saved reference so the team can identify it. No public lookup exposes another customer’s details.
Updates
This notice should be updated if HEVKAR introduces new ways to collect or use information.