LEGAL / PRIVACY POLICY

Privacy Policy.

How the Aevrion Ops website handles the information you provide — what is collected, who processes it, how long it is kept and what you can ask for.

Written from the implementation rather than from a template. Where something is not yet in place, this page says so instead of inventing an answer.

01 / WHO IS RESPONSIBLE

A named person, not an abstraction.

LAST UPDATED / 22 AUGUST 2026

This website is operated by David John Perez, sole proprietor of Aevrion Ops.

Aevrion Ops is a sole proprietorship whose business name is registered with the Philippine Department of Trade and Industry (DTI), based in the City of Baguio, Philippines. The person accountable for the decisions described in this policy is the proprietor named above, working from Baguio City, Philippines.

Privacy contact: privacy@aevrionops.com. General contact: hello@aevrionops.com.

This policy is written primarily against the law of the Republic of the Philippines, including the Data Privacy Act of 2012 (Republic Act No. 10173) and guidance issued by the National Privacy Commission. It has not been reviewed or certified by legal counsel, and it does not claim certification under any privacy framework.

02 / INFORMATION YOU PROVIDE

What you type, plus a short record of how you reached the form.

This website asks you for information in one place and in one way: a form. There is the project-intake form on the Contact page, and two review-request forms reached only from links Aevrion sends directly. All three submit to the same place and are governed by this notice. They accept the following fields:

  • NAME

    Your name, so a reply can address you. Required.

  • WORK EMAIL

    The address a response would go to. Required.

  • BUSINESS PROBLEM

    Your description of what needs to work better. Required.

  • COMPANY / ORGANIZATION

    Optional context about the business.

  • WEBSITE / PRODUCT URL

    Optional link to the relevant site or product.

  • PROBLEM AREA

    An optional selection — Build, Automate, Operate, Deliver or Not sure.

  • DESIRED OUTCOME

    Optional description of what a good result would look like.

  • TIMING / CONSTRAINTS

    Optional notes on schedule or limitations.

  • CRM OR SYSTEM IN USE

    Optional, on the CRM review form only: the name of the system the business uses today.

The form also generates two technical values that contain no personal information: a random submission identifier used to prevent duplicate delivery of the same inquiry, and a timestamp used by spam protection.

A short record of how you reached the form is submitted with it, so that an inquiry about a CRM problem does not arrive looking identical to one about a website rebuild. It is assembled in your browser's memory while you are on the site, it is included in the email, and it is kept alongside your inquiry in Aevrion's own record of it. It is never used to build a profile of you, and it is never shared with an advertising or analytics network:

  • SERVICE INTENT

    One label from a fixed internal list — for example “crm-implementation” or “general” — describing the subject of the page you came from. Anything unrecognised becomes “unknown”.

  • PAGE YOU ARRIVED ON

    The path of the first page of this website you opened, such as /automation/crm-implementation/. A path only: no query string.

  • PAGE YOU CAME FROM

    The path of the page on this website you were reading immediately before the form.

  • REFERRING WEBSITE

    If another website sent you here, its domain name only — for example google.com. Never the full address, which could contain someone else’s search terms or identifiers.

  • CAMPAIGN PARAMETERS

    The standard utm_source, utm_medium, utm_campaign, utm_content and utm_term values, if the link you followed carried any.

None of this identifies you. There is no cookie, no advertising or click identifier, no device or browser fingerprint, and nothing is written to your browser’s storage — while you are browsing, this record exists only for as long as the page is open, and it is discarded when you close the tab unless you actually send an inquiry. Every value is checked against a fixed list on the server before it is used, and anything unrecognised is discarded rather than recorded. If JavaScript is turned off, none of it is collected and your inquiry is simply recorded without it.

Please send only the business information needed to evaluate a project. Do not include passwords, credentials or sensitive personal information — the form asks for none of these.

03 / HOW INFORMATION IS USED

To evaluate and respond to your inquiry.

  • REVIEWING CONTEXT

    Reading the project context you submitted to understand the situation.

  • RESPONDING

    Replying to you, including asking clarifying questions.

  • EVALUATING FIT

    Considering whether Aevrion is an appropriate fit for the work.

  • DEFINING SCOPE

    Preparing a potential scope or next step for the project you described.

The basis for this processing is straightforward: you sent an inquiry in order to get a response, and the information is used to give you one.

Submitting the form does not subscribe you to anything. Inquiry information is not used for advertising, is not added to a marketing list and is not sold. There is no newsletter signup on this website, and there is no pre-ticked consent box anywhere on it. If marketing is ever offered, it will be a separate, optional and clearly labelled choice.

04 / WHO ELSE PROCESSES IT

Four providers, each with a specific job.

Delivering an inquiry involves service providers. These are the only ones in the path, and each one is listed because it genuinely processes something:

  • Resend

    Transactional email delivery for project-intake submissions. It sends the inquiry notification from notify.aevrionops.com. Receives: The content of your inquiry, composed into an email message, plus your email address as the reply-to.

  • Google Workspace

    Receives, stores and sends Aevrion business email, including the inquiry notification and any reply the operator sends you. Receives: The delivered inquiry email and the correspondence that follows it.

  • Cloudflare

    DNS for aevrionops.com, network protection in front of the website, and DMARC reporting. It does not handle the mailbox. Receives: Standard request data when serving pages.

  • ChatGPT Sites (OpenAI)

    Hosting and serving of the website, its intake endpoint and the database holding the inquiry record. Receives: Standard request data required to serve a website, such as IP address, user agent and requested URL, and the stored inquiry record.

These providers operate their own infrastructure, which may be located outside the Philippines, and they retain data according to their own policies and their agreements with Aevrion. Aevrion does not control those retention periods and this policy does not restate them, because a number repeated here could quietly become wrong.

Aevrion does not sell personal information, and does not share inquiry information with anyone beyond the providers above.

05 / HOW DELIVERY WORKS

Validated, delivered as email, or clearly refused.

When you submit the form, the submission goes to this website's own intake endpoint over the same secure connection as the page. It is validated and size-limited on the server, checked by spam protections and screened against duplicate delivery before anything else happens.

If it passes, Aevrion records it first, and only then composes it into an email and hands it to Resend, which sends it from notify.aevrionops.com to hello@aevrionops.com. That mailbox is hosted on Google Workspace, which receives and stores the message and sends any reply the operator writes. Your email address is set as the reply-to so a response goes back to you directly.

The system is designed to fail closed: if delivery is not available, the form tells you plainly, nothing is claimed to have been received, and your entries stay in the form so you can try again. Your inquiry is never silently dropped and never silently diverted.

Aevrion keeps its own record of your inquiry. It is written before delivery is attempted and it is the reason a delivery problem no longer means a lost inquiry: if the provider refuses the message, the record remains and the delivery attempt is marked as failed, so your inquiry can still be answered. The record holds what you typed, how you reached the form, and whether delivery succeeded. It is not readable over the internet — this website has no page or endpoint that returns inquiries, and nothing reads them back out.

06 / HOW LONG IT IS KEPT

Inquiries are kept while they are useful, then removed.

An inquiry is held in two places: Aevrion's own record of it, and the email correspondence that follows. Aevrion retains both for up to 24 months from the last meaningful interaction, after which the record is removed and the correspondence is deleted from the operator's mailbox.

Information may be kept longer where:

  • IT BECOMES A CLIENT RECORD

    The inquiry leads to an engagement, in which case it forms part of that business relationship and its records.

  • THE LAW REQUIRES IT

    Accounting, tax or other legal obligations require a longer period.

  • A CLAIM IS LIVE

    The information is needed to establish, exercise or defend a legal claim.

This retention is applied by the operator rather than enforced by an automated deletion job. Aevrion's inquiry record has no scheduled expiry process, and neither does the mailbox. That is stated plainly rather than described as an automated control it is not.

07 / WEBSITE TECHNICAL DATA

Serving a website involves standard request data.

Like any website, delivering these pages involves the hosting and network infrastructure processing standard request information — such as an IP address, browser user agent and the URL requested — as part of ordinary operation, performance and security.

The website's own application code does not read, store or build profiles from this data. It is handled by the hosting and network providers listed above under their own terms.

The intake endpoint records an operational log line for each delivery attempt so that a failure is not invisible. That line contains the random submission identifier, a timestamp and a result. It deliberately contains none of your inquiry: no name, no email address, no message text.

08 / COOKIES, ANALYTICS + TRACKING

This website sets no cookies and runs no tracking scripts.

In its current implementation, this website:

  • COOKIES

    Sets no cookies of its own, and shows no cookie banner because there is nothing to consent to.

  • ANALYTICS SCRIPTS

    Loads no analytics or tracking scripts. There is no Google Analytics and no advertising or social pixel of any kind.

  • BROWSER STORAGE

    Stores nothing in your browser's local storage or session storage.

  • THIRD-PARTY REQUESTS

    Loads no third-party embeds or externally hosted scripts; fonts are served from this website itself.

Hosting and network providers may produce their own aggregate traffic measurements from the request data described above. That is infrastructure-level reporting rather than a tracking script placed in your browser, and it does not identify you personally to Aevrion.

This describes the current implementation rather than a permanent promise. If measurement tools are ever added, this page will describe them — what they collect and why — before they operate.

09 / RECRUITMENT

If you write to us about work.

The Careers page asks you to introduce yourself by email to hr@aevrionops.com. There is no application form on this website, so the only information Aevrion receives is what you choose to put in that email.

What you send is up to you. An application may include written answers, a CV or resume if you choose to attach one, links or work samples, and — where a role asks for one, as the B2B cold caller role does — a short audio or voice introduction.

All of it is treated the same way: a person reads or listens to it and decides whether to reply. Aevrion runs no voice recognition, no biometric analysis, no AI assessment and no automated scoring on application material, and does not use it to train anything.

It is used to consider you for current or future work, and for nothing else. Retention:

  • ACTIVE CONSIDERATION

    Application material is kept up to 12 months after the recruitment process closes.

  • FUTURE OPPORTUNITIES

    If you agree to be kept in mind for later work, your details are kept up to 24 months. You can ask to be removed at any time.

Please do not send sensitive personal information. Aevrion does not ask for government identification, passport details, bank or financial information, health history, religion or marital status at this stage, and none of it is needed to start a conversation. If you send it anyway, it will be deleted.

10 / YOUR RIGHTS

What you can ask for, and how.

Under the Data Privacy Act of 2012 and generally recognised privacy principles, you can expect to be able to:

  • BE INFORMED

    Know that your information is being processed, and why — which is what this page is for.

  • ACCESS

    Ask what information about you Aevrion holds, and receive a copy of it.

  • CORRECT

    Ask for information that is inaccurate or incomplete to be corrected.

  • ERASE OR BLOCK

    Ask for your information to be deleted, or its processing restricted, where that applies.

  • OBJECT

    Object to processing, including asking that no further contact be made.

  • COMPLAIN

    Raise a complaint with the National Privacy Commission if you believe your rights have not been respected.

To make a request, email privacy@aevrionops.com describing what you need. Requests about your own information are handled as such, not as project inquiries. Aevrion will respond within a reasonable period and may need to confirm your identity first, so that information is not disclosed to the wrong person.

The precise rights that apply depend on where you are and which law governs the processing. This page does not promise a specific statutory right under every jurisdiction, because that would not be true everywhere.

11 / SECURITY

Restrained measures, honestly stated.

Submissions travel over an encrypted connection. The intake endpoint validates and size-limits what it accepts, rejects malformed and oversized submissions, applies spam and duplicate-delivery protections, and refuses inquiries it cannot handle correctly. Credentials are held in server-side configuration and never reach the browser. Operational logs exclude inquiry content by design.

How Aevrion approaches security more broadly, and how to report a vulnerability, is described on the Security page.

No system can promise absolute security, and this page does not. No security certification is claimed.

12 / CHANGES TO THIS POLICY

This policy changes when the system changes.

This policy is written from the current implementation and is updated when actual behaviour changes — a new provider, a change in what is collected, or the introduction of any measurement tool. The revision date at the top records when the wording last changed.

This is a policy, not legal certification. It has been written carefully and from the actual implementation, but it has not been reviewed by counsel, and no compliance certification under any framework is claimed. Questions are welcome at privacy@aevrionops.com.