Collected when relevant
Contact and inquiry data
Name, email, organization, inquiry type, app interest, and message context submitted through public contact and request forms.
Legal
Privacy practices for inquiry and diligence workflows
This policy covers how inquiry and diligence-request information is handled across public routes, including contact intake, controlled-review scoping, retention expectations, and reviewer safeguards.
Collected when relevant
Diligence intake metadata
Requested apps, reviewer role, timeline, and stated review goals used to scope technical and commercial follow-up.
Collected when relevant
Operational and security logs
Limited request-level telemetry and service logs used for abuse prevention, delivery reliability, and troubleshooting.
Purpose limitation
Why this information is processed
Respond to requests
Confirm intent, answer questions, route inquiries, and coordinate demos, licensing, implementation, partnership, or acquisition conversations.
Scope controlled review safely
Determine whether a request needs controlled review terms, app-specific materials, or follow-up meetings.
Protect service integrity
Detect abuse, diagnose form delivery failures, and maintain stable public inquiry channels.
Retention
Retention approach
General contact inquiries
Retained for active correspondence and reasonable operational follow-up, then removed or archived under internal record controls.
Diligence and transaction conversations
Retained longer when needed for legitimate review history, compliance, or transaction documentation requirements.
Operational logs
Kept for the minimum period needed for stability, security checks, and incident response, then rotated or deleted.
Subprocessors
Processor disclosures
Hosting and application runtime
ActiveInfrastructure providers may process request metadata needed to run and secure the site.
Transactional messaging
ConditionalEmail delivery services may process inquiry content when configured in the deployment environment.
Diligence workflow integrations
ConditionalDocument-signature and data-room providers are used only when integrations are enabled for approved review paths.
Your requests
Rights and requests
- Request a copy of contact data associated with your inquiry.
- Request correction of inaccurate submission details.
- Request deletion where retention is no longer operationally or legally required.
- Ask how your inquiry was routed and what follow-up context is being retained.
Submit privacy-related requests to preventioneer@gmail.com.
Sensitive-use safeguards
Keep public forms lightweight
- Do not submit confidential survivor, client, legal, or health records through public forms.
- Describe sensitive contexts at a high level so a safer review path can be coordinated.
- Use controlled review channels for materials that require confidentiality or risk-aware handling.
Policy updates
This policy is updated when route behavior, integrations, or review workflows materially change. The live version on this page governs current public interactions.
No sale of personal information
Personal information submitted through inquiry channels is used for operational response and review workflows. It is not sold for advertising or unrelated commercial profiling.
Next step
Need policy context before requesting diligence?
Review access expectations first, then submit a scoped diligence review request.