Tool data
Free tools may ask for service selections, domain names, quiz answers, project stage, budget range, and launch blockers. This information is used to generate a result and help you send useful scoping context.
Data Policy
Data policy.
Last updated May 18, 2026. This policy explains how tool inputs, project context, credentials, and sensitive technical data should be handled during scoping and service delivery.
Project data
If you share repositories, credentials, API keys, customer data, production access, or private documentation during a paid engagement, handling rules should be agreed in the project scope before access is granted.
Sensitive data
Do not submit passwords, API secrets, private keys, regulated customer data, medical data, financial records, or confidential source code through public forms or plain email unless a secure transfer method has been agreed first.
Security practices
For service work, I prefer least-privilege access, temporary credentials, environment separation, audit trails where available, and revocation of access after delivery or when it is no longer needed.
AI and automation
Project information is not intentionally used to train public AI models. If AI-assisted tooling is useful during delivery, sensitive details should be removed or handled under the agreed project rules.
Deletion and access removal
You can request deletion of submitted context or removal of access by emailing hello@cyprianaarons.xyz. After a project ends, you should rotate credentials and remove accounts that are no longer needed.