RousingTech

Privacy policy

Your information, handled with care.

Understand what we collect when you contact us, why we use it and how to ask about your information.

Who handles your information

Rousing Tech Ltd operates this website and handles the personal information submitted through its contact form. This notice covers website enquiries and security checks; separate terms may apply if you become a client.

You can use the contact page to ask a privacy question or request access, correction or deletion of your enquiry. Do not include identity documents or other sensitive information in an initial request. We may need proportionate information to verify your identity before disclosing or changing a record.

Information you provide

The form collects your name, email address and project description. A phone number and service selection are optional. We need an email address to respond and enough information to understand your enquiry; you do not need to provide a phone number to submit.

Please do not include passwords, payment card details, access keys, identity documents, health information or other sensitive personal information. Only include information needed to explain your project.

How your enquiry is used

Your details are used to review your request, respond to you and discuss the services you asked about. Submitted enquiries are stored in a private website database. When email notifications are configured, enquiry details are also sent through Amazon Simple Email Service (SES) to the configured company mailbox. Your enquiry may remain saved if an email attempt fails; the form reports successful submission only after the email service accepts the message. Your email address is used as the reply address.

Submitting an enquiry does not subscribe you to marketing. The current website does not add advertising or analytics trackers. Service providers and the hosting environment may process technical connection information needed to operate and secure their services.

Security checks and cookies

The form uses an image code followed by Cloudflare Turnstile to help prevent automated or abusive submissions. The image check sets a first-party cookie named contact_code. It contains a random challenge identifier, lasts up to five minutes and is restricted to the contact API. It is HttpOnly and SameSite=Strict, and has the Secure flag on HTTPS connections.

The image answer is not stored as plain text. Its challenge record expires after five minutes and is consumed after a correctly formatted attempt. Expired records are removed when new challenges are created; expiry does not mean immediate physical deletion from database backups.

Turnstile processes browser, device and network signals. Its verification token is sent from our server to Cloudflare for validation. The server does not include your enquiry, email address, phone number or an explicit IP-address parameter in that verification request. Cloudflare still receives connection information when your browser loads its widget. Turnstile tokens are not saved with your enquiry.

Who receives information

Enquiry information is available to the team members who need it to handle your request and to the service providers involved in storage, hosting and email delivery. Amazon SES processes the enquiry email; the receiving mailbox provider also processes that email. Cloudflare processes the security-check information described above.

These services may process information in more than one country. Provider arrangements, processing locations and any required international-transfer safeguards must be confirmed for the production configuration. A selected AWS sending region alone does not establish where every copy or provider operation is located.

Storage, retention and deletion

Enquiry records contain a numeric ID, name, email, optional phone and service, message and submission time. Separate records track email delivery and retry references. The database is outside publicly served website files; production does not expose a public enquiry-list API. Email copies also exist in the receiving mailbox.

No automatic enquiry-retention schedule is currently implemented. Records remain until an authorised operator removes them. The company must set and apply an appropriate retention period or documented criteria, including mailbox copies and backups, before treating this notice as final. Deleting a database record alone does not delete its email or backup copies.

Your privacy choices and rights

Depending on the law that applies and the circumstances, you may have rights to access or correct your information, request deletion or restriction, object to processing, and receive a portable copy. Some rights have exceptions. If processing relies on consent, you may withdraw that consent without affecting earlier lawful processing.

Use the contact page to explain your request and the email address used for your enquiry. You may also complain to the relevant data-protection regulator. If UK data-protection law applies, this is the Information Commissioner’s Office (ICO). The company’s jurisdiction and the lawful bases for handling enquiries and preventing abuse still need confirmation.

Protecting your information

The implementation validates submitted fields, verifies security checks on the server, uses parameterised database queries and restricts database-file permissions. Local environment files and enquiry data are excluded from source control. Enquiry contents and credentials are not intentionally written to application error logs.

No system can promise absolute security. Production access controls, encrypted transport, credential management, backups, retention procedures and abuse protections need to be maintained as part of operating the website. Automated anti-abuse checks may block a submission; this website does not use enquiry information to make automated decisions about eligibility for services.

Provider information and complaints

We will update this notice when the website’s data handling changes. The date above identifies the latest website notice.