OWL Contact Privacy Policy

Privacy Policy

Who we are

OWL means Optimized Workflow Logic. OWL operates primarily from the Philippines. For privacy questions or requests about this Contact service, contact us at optimizedworkflowlogic@gmail.com. OWL is using this operating identity while an official legal-entity name and registered address, if applicable, are not recorded. We do not state an unverified registration number or address.

Scope

This policy explains how OWL handles information sent through this website’s Contact form and the limited technical information created to operate and protect that service. It does not cover a separate relationship governed by a signed agreement or third-party websites and services.

Information you provide

The Contact form asks for your Name, email address, conversation type, optional company or organization, and message. The rendered form label remains Full name. The form does not ask for a phone number, postal address, payment information, government identification number, file attachment, or marketing sign-up.

The form also contains a hidden website field used only to identify automated spam. A honeypot submission does not deliver, and that field is not included in a delivered message or retained as ordinary inquiry information.

Technical and anti-abuse information

To operate and protect the Contact service, OWL records only minimum necessary application metadata: a submission reference, time, outcome, failed field names, applicable rate-limit rule, and a truncated HMAC-derived network-address hash. The application uses a network address momentarily to apply rate limits but does not store the raw address in its Contact-service records. Short-lived rate-limit counters are held in memory.

The production topology is now selected. The website runs on an OWL-controlled origin server reached directly over HTTPS, with DNS provided by Cloudflare in DNS-only mode and no proxy or content-delivery edge in the request path. Web-server records created by that origin follow the operational log standard described under Retention.

Why we use information

OWL uses Contact information only to respond to inquiries; route inquiries to authorized OWL representatives; maintain necessary communication records; prevent spam and abuse; protect and diagnose the Contact service; and handle approved operational, security, or legal requirements. We do not use Contact information for marketing, advertising, profiling, automated decision-making, or unrelated purposes, and we do not sell it.

This policy provides notice about that processing. The Contact form has no consent checkbox, and submitting it is not described as legal consent.

Delivery and replies

The service validates and cleans entries, applies anti-abuse controls, and records one submission in an encrypted store on OWL’s own server. Your input cannot control the storage location, retention, notification settings, or any other processing configuration. Your email address is recorded only so OWL can reply to you.

OWL keeps a Contact-submission record. Each accepted submission is encrypted and stored on the OWL origin server, and that encrypted store is the operational communication record. Email notification is not currently configured, so no Contact message is transmitted to an external email provider. There is no web interface to the store; reading a message requires direct server administrator access. If the store is unavailable the service fails closed and shows a general error — it does not accept a message it cannot retain, and it does not retry in the background.

Access and providers

Access to Contact messages is restricted to authorized OWL personnel who need it to respond to inquiries or operate the service. OWL may use contracted hosting, email, communications, security, and infrastructure providers to operate the Contact service.

The Contact service runs on a dedicated virtual server operated by Hetzner in Germany, with DNS provided by Cloudflare. Contact messages are stored only on that server and are not sent to an email, communications, analytics, or advertising provider. If OWL later introduces such a provider, this policy will be updated before that change takes effect.

Cookies and analytics

No Contact-specific cookies or Contact-specific analytics have been identified in the accepted implementation. If that changes, OWL will review the change before public use.

Security

OWL restricts access, validates requests, uses anti-abuse and rate-limit controls, and prevents visitors from controlling sender or recipient configuration. Development and production credentials must remain separate, and secrets must remain outside Git. Stored Contact messages are encrypted at rest using authenticated encryption, with the key held outside the code repository and readable only by the service account. No method of transmission or storage is completely secure; OWL does not promise absolute security, end-to-end encryption, certification, audit status, or zero risk.

Retention

Contact messages are normally retained in OWL’s encrypted Contact store for up to 90 days and may be removed earlier when no longer needed. A message marked resolved is deleted no later than 30 days after resolution. Limited active-inquiry, operational, security, fraud, or legal exceptions may apply.

Limited residual copies may remain temporarily in OWL-controlled encrypted backups and expire as those backups rotate. Those residual copies are not used for ordinary business processing. OWL does not claim that every residual copy is irreversibly destroyed within 90 days.

Operational logs follow a retention standard of up to 30 days and contain only minimum necessary metadata: a submission reference, time, outcome, failed field names, applicable rate-limit rule, and a truncated network-address hash. They never contain message content, names, or email addresses.

Privacy requests and deletion

To make a privacy request or ask about this policy, email optimizedworkflowlogic@gmail.com. OWL will review and respond as reasonably required by applicable obligations. OWL may need additional information to understand or process a request, but does not promise a particular identity-verification method, statutory deadline, or automatic deletion in every circumstance.

You may ask OWL to delete a Contact message. OWL may retain information where an active inquiry, approved operational, security, fraud, or legal requirement applies. When OWL deletes a message, it removes the message from the encrypted Contact store and other locations it controls; residual copies in encrypted backups may continue temporarily as described above.

Minors

The Contact service is intended for business and general inquiries. OWL has not implemented a child-specific collection, age-verification, or parental-consent workflow. Any future targeting of children or collection of child-specific information requires a new review.

Changes and publication status

OWL may update this policy when implementation, provider, location, legal, or operational facts change. The Contact service is active. Search-engine indexing of this website remains disabled and requires separate OWNER approval.