Clear handling of request details.

We handle the contact details you supply, such as your name, email, optional phone number, town or postcode, region, requested service, date and slot, and the context you choose to provide. Please do not send exact property addresses, financial records, boundary details or other sensitive material through the intake form.

We also keep request context and consent evidence, including the policy or terms version, acceptance and submission time. For short-lived abuse controls, we derive a keyed hash of a network identifier. We do not store the raw IP address in the application record.

We use this information to respond to enquiries, verify booking requests, review service fit and travel, manage conditional capacity, send lifecycle emails, prevent misuse and maintain service records. We do not sell personal information.

Primary application processing and storage use AWS in Sydney. Transactional email is currently sent through Amazon SES in us-east-1 until Sydney production access is approved, so email content and delivery metadata may cross regions.

This site loads Google Fonts. Requests to Google may disclose ordinary web request metadata such as your IP address, browser details, requested font resource and referring page, subject to your browser and network settings.

• Enquiry personal information: 180 days.
• Booking request personal information: up to 365 days.
• Declined, cancelled or expired request records: up to 30days.
• Transient outbox records: 7 days. Eligible failed deliveries may be replayed automatically; records in notification, replay and final failure queues remain for up to 14 days per queue.
• Application logs: 30 days; DynamoDB point-in-time recovery: 35 days.

Expiry uses database TTL and background deletion, so removal is approximate rather than immediate. Recovery copies and operational backups can lag the live record and age out on their own schedules.

Booking status and management links contain customer access capabilities. After you open a link, this site removes those capabilities from the visible URL and may keep them in sessionStorage, scoped to that request, so the same browser tab can refresh the status page. They are not placed in localStorage. Keep the email and link private, close the tab on a shared device, and clear site data if needed.

You may ask what personal information we hold about you, request correction or deletion, withdraw optional update consent, or raise a privacy concern. Some records may need to be retained briefly for security, integrity or legal reasons. Contact info@heimdall.farm.