Privacy

Information you provide

When you request Helka access, a demo or a pilot, ask for Helka updates, or send a general project enquiry, StructylAI receives the details entered in that form. These can include your name, email address, organisation and the type of request you selected.

You may also choose to provide context such as your role, country, website, preferred contact details, current tools, approximate volume, timeframe or a message. Optional context is used only when it is supplied.

When a form is submitted, the receiver also processes the client IP address for the connection, or the single validated client address supplied by a configured trusted reverse proxy. It also processes the submission time and any idempotency key supplied with the request, and derives keyed-HMAC request and client-address digests.

How it is used

The information is used to review and respond to your request, assess whether Helka or another StructylAI service may be relevant, discuss a possible project and keep a related communication record. An opaque reference confirms that the website saved a request; it does not mean an email was delivered, a demo was booked or access was granted.

A request for Helka product updates is separate from other enquiry purposes. Contact details may be used for those updates only when you select that choice, and you can later ask for them to stop. The website does not currently send an automatic acknowledgement email.

The technical request data is used for receiver security, anti-abuse controls, rate limiting, duplicate detection and safe handling of repeated submissions. The saved technical records can include the HMAC client-address digest, request fingerprint, idempotency key, opaque reference, event times and expiry metadata.

Storage and service providers

The website and enquiry database run on the founder's private DigitalOcean servers. DigitalOcean supplies the underlying hosting infrastructure. No separate managed form processor or enquiry email service is configured for these forms.

The enquiry application uses the raw client address to derive the client-address digest but does not write that raw address to its SQLite enquiry tables. This distinction concerns application storage: hosting, network or reverse-proxy systems may also process addresses under their operational logging and security settings. The retained HMAC digests and fingerprints are pseudonymous technical identifiers, not a promise that the data is anonymous or impossible to relate to other information.

Any future email, integration or other provider must be reviewed before use, and this notice must be updated when that changes how personal information is handled.

Retention and security

Enquiry information is kept only for as long as reasonably needed for communication, project administration and applicable legal obligations. The exact production retention and deletion schedule remains subject to founder, legal and operational approval before launch.

Newly saved enquiries do not retain the client-address digest or request fingerprint with the enquiry itself. Those identifiers are kept separately for limited receiver-control purposes: duplicate detection for 30 seconds, rate limiting for 15 minutes and safe idempotent retries for seven days. Expired metadata is ignored and removed during a subsequent save attempt, rather than by a scheduled deletion timer, so an idle database or backup may still contain expired records.

Older saved enquiries may still contain technical identifiers. Their cleanup and the retention of enquiries, backups and exports require a separately reviewed deletion procedure and explicit founder approval before launch. Opening the database does not automatically erase existing values.

Enquiries are stored for restricted private review. Technical and organisational controls are used to limit access to the database, secrets, backups and any exports, but no system can guarantee absolute security.

Your choices

Depending on the law that applies, you may ask what personal information is held about you, request a correction or deletion, or object to some uses. You may also withdraw a separately requested product-update choice. Use the Helka enquiry form and state that your message concerns privacy.

Review before launch

The founder, legal adviser and operations owner must review this notice and the production arrangements before enquiries are enabled for launch. That review includes the legal identity and contact details, applicable rights, retention, deletion, backups, access controls and any later service providers.

Questions

For a privacy question, contact StructylAI through the website.