Use synthetic or sanitized, authorized material. We have not established arrangements for classified, regulated, biometric or other restricted datasets. Contact us before sharing material that needs contractual confidentiality or residency commitments.
1. Operator and contact
SecurityDesignAI is operated by Brent Bateman in an individual capacity. A registered company is not represented as the operator. For demo, privacy, deletion and security requests, contact support@securitydesignai.com.
2. Information we collect
- Demo requests: name, business email, organization, selected workflow, time zone, optional preferred times, permission to respond, submission time and a receipt reference. The form does not request project files or send its contact details to an AI provider.
- Accounts: account/contact identifiers, authentication information and agreement acceptance records.
- Project work: requirements, customer/site descriptions, inventories, health reports, screenshots, files, notes, engineering decisions and outputs you provide or generate.
- Operations: requests and diagnostics may include IP addresses, paths, browser information and timestamps. Do not put secrets or customer details in project names or URLs.
- Support email: the contents and attachments you choose to send, processed by the mailbox services involved.
3. Why we use information
We use contact details to respond to the request you made and arrange a conversation. Sending a request does not subscribe you to a marketing list or book an appointment. We use authorized project material to provide intake, engineering analysis, project storage, requested support and deliverables, and technical information to operate, protect and troubleshoot the service.
This notice does not authorize sale of customer material, unrelated advertising use, publication of customer evidence or training a SecurityDesignAI model on your project content. A separate permission is needed for a public case study, identifying quote or logo. We may disclose information when required by law or necessary to address misuse or protect legal rights.
4. Storage, access and service providers
Project and demo records are stored in the service backend on a virtual private server operated by Hostinger in the United States (Boston, Massachusetts). Demo records are in an operator-only inbox; they are not visible to ordinary workspace accounts or public visitors. Authorized administration and support can require access to records.
The browser also stores authentication state and project caches; agreement acceptance may be stored in session storage. Signing out does not erase every cache or downloaded file. On shared devices, clear site data and remove exported copies when appropriate.
Relevant project evidence may be sent to OpenAI through the OpenAI API for analysis and drafting. Every request asks OpenAI not to store the response (store: false), and no project files are uploaded to OpenAI's file storage. Under OpenAI's published API terms, API data is not used to train OpenAI models unless a customer opts in, and OpenAI keeps abuse-monitoring logs for up to 30 days. SecurityDesignAI has not opted in: sharing of API inputs and outputs, model feedback, and evaluation or fine-tuning data with OpenAI is disabled for our OpenAI organization. We do not have a zero-data-retention arrangement with OpenAI, and AI processing is not restricted to a particular country. Support email is hosted by Hostinger. Hosting, AI and email providers process information needed for their roles under their applicable terms. Request the deployment/provider details and any required contractual commitments before sensitive onboarding.
5. Retention and deletion
Demo inbox records are scheduled for daily removal once they are more than 90 days old. This removes the active inbox record, not every historical backup or correspondence copy. A follow-up account or project is governed by its own purpose and records.
Workspace projects remain until you remove them through the available project deletion workflow or an authorized administrative process. The application attempts to remove related workflow records. Browser caches, exported copies, security diagnostics and provider-held information are separate. Account and support records are retained as needed to operate the account, answer the request, resolve disputes and meet applicable obligations; contact us to request removal.
Web access logs are configured for daily rotation with 14 rotated copies. The hosting provider takes a weekly server backup. Application diagnostics and release/database snapshots are maintained separately and do not currently have one uniform deletion deadline. Project deletion does not automatically purge those snapshots. We do not promise immediate or complete deletion from backups; request the applicable recovery and deletion arrangements before sharing sensitive information.
6. Your choices and requests
Limit what you upload, sanitize identifiers, review project information, use available deletion functions and manage your browser data. Contact support@securitydesignai.com to request access, correction, export or deletion, or ask about processing and providers. We verify identity and authority before disclosing records or making destructive changes. Applicable rights depend on the circumstances and governing law; this notice does not waive them.
7. Forms, email and browser technologies
The demo form sends your chosen contact fields to our backend and confirms receipt only after storage succeeds. It uses a short-lived challenge and rate limits to reduce automated misuse; no file upload or AI processing is part of the form. We do not add its fields to browser local storage.
Email links open your mail application; you review and send that message yourself. Copy buttons send nothing. The public contact pages do not embed a third-party scheduler or advertising tracker. Hosting and network logging may still occur.
8. Security, scope and changes
The service is intended for professional security-engineering evaluation. Do not submit credentials, live surveillance, facial/biometric datasets, regulated personal records, classified data or other restricted material we have not agreed to support. Camera analytics planning is distinct from processing real surveillance or biometric data.
Read the security statement for controls and limits. This notice describes the current evaluation service; it is not a certification or a replacement for a customer-specific agreement. Material updates will be reflected here with a revised effective date, and any change requiring separate permission will be handled accordingly.