Security
Last updated: 18 August 2026
This page describes how AIWeekly protects information submitted through this website and how to report a suspected security issue.
Data in transit and at rest
The site is served over HTTPS. Enquiry, newsletter and order data is stored in a managed database with encryption at rest, and access is restricted by row-level security policies so that records are only readable by authorised administrators.
Access control
Administrative access requires an authenticated account with an explicit role grant. Roles are stored separately from user profiles and checked server-side on every privileged operation. Administrative actions on governance-sensitive records are written to an audit log.
What we ask you not to send
Please do not submit special category personal data, patient information, client-privileged material, credentials or payment card details through website forms. If a discussion requires that kind of information, contact us first and we will agree a suitable channel.
Payments
Card payments are processed by our payment provider. AIWeekly does not receive or store full card numbers.
Reporting a vulnerability
If you believe you have found a security vulnerability, please report it to us through our contact page with enough detail to reproduce the issue. Please give us a reasonable opportunity to investigate and remediate before any public disclosure, and do not access, modify or exfiltrate data belonging to other people while testing.
We will acknowledge legitimate reports, keep you informed of progress, and credit reporters who wish to be named once an issue is resolved. We do not currently operate a paid bug bounty.
Related policies
See our Privacy Policy for how personal data is used and retained.