Privacy Policy

Creaptor is a solo project built, run, and maintained by me alone. In these pages, "Creaptor", "I", "me", and "my" mean me as the operator of the public Creaptor website and browser-based media tools.

When you use the browser media tools, selected files are processed locally in your browser on your device.

The main workflow is designed not to upload source files, output files, or file contents to my server for conversion, compression, or browser-side preview generation.

That local-first model does not mean the public website is data-free. Separate operational, analytics, monitoring, and support systems may still process limited technical information as described below.

The public site may process technical request data needed to deliver and protect the site, including IP address, user agent, timestamps, request metadata, and similar infrastructure logs.

If you opt in to optional analytics or browser-side diagnostics, the product may process limited telemetry about how the site is used, such as tool or page context, browser family, operating system family, conversion stage, and file-size buckets.

If you email support, I receive your email address and the message or attachments you choose to send. Your email provider and Google, which hosts the support inbox, also process that correspondence. The website does not handle your email.

If the feedback form is available, the website sends the feedback type, page path, and message to my server. The server removes common sensitive values from the message and emails it to the same Gmail inbox. The form does not ask for an email address, so I cannot reply to form submissions.

• I do not intentionally send file contents to Google Analytics 4 or Uptrace as part of the normal browser workflow.
• I do not intentionally send raw file names in the normal analytics and monitoring flow.
• Some monitoring events may still include coarse technical context such as file-size buckets when a local job fails.

The public site uses Google Analytics 4 for optional product analytics and OpenTelemetry with Uptrace for optional browser diagnostics. Browser traces pass through the site's own server gateway before reaching Uptrace.

These services receive limited product and technical data rather than the media files being processed. Each optional category stays off until you opt in through the site privacy settings.

I may change vendors, add vendors, or remove vendors over time when that is necessary to run, secure, or improve the public product.

The app may use browser memory, object URLs, and other local runtime state to complete local processing, preview, and download flows.

A first-party consent cookie may be used to remember your optional analytics and diagnostics choice for up to 180 days.

Google Analytics 4 may set analytics cookies after you opt in. You can withdraw consent at any time through Privacy settings; the site then stops analytics delivery and expires its GA4 cookies.

Hosting, CDN, anti-abuse, or security layers may also use essential cookies or equivalent browser technologies where needed to deliver, protect, or troubleshoot the site.

I use limited website, telemetry, and support data to deliver the public site, detect errors, improve product quality, understand tool usage, respond to support requests, and protect the service against abuse or misuse.

I do not treat that operational data as a license to inspect or repurpose your local media workflow.

I may share limited data with service providers that help me host, monitor, analyze, or secure the site, or receive support email.

Support email is delivered to a Gmail inbox.

I may also disclose data where required by law, legal process, or a good-faith need to protect the rights, safety, security, or operation of the site, its users, or the public.

I do not claim that I will never disclose data under legal compulsion. I aim instead to keep the normal product model as data-minimized as practical.

I try to retain operational and support data only for as long as reasonably needed for service delivery, security, troubleshooting, recordkeeping, and legal obligations.

Retention periods can vary depending on the system, vendor, and the type of record involved.

Because the core media workflow is browser-local, the actual source files and output files from the normal tool flow are intended to stay on your device rather than in my long-term server storage.

The public website and third-party vendors I use may process technical or support-related data in more than one country.

If data is transferred across borders, I aim to use providers and arrangements that are commercially reasonable for a public internet product, while recognizing that no internet-based service can promise zero transfer risk.

Depending on where you live, you may have rights to request access, correction, deletion, objection, or other controls over personal data that I hold about you.

You can revisit optional analytics and diagnostics choices through the Privacy settings control in the site footer.

To make a privacy request, email creatorflowfeedback@gmail.com with enough detail for me to understand the request and verify that it relates to you.

I may need to keep certain records where required for legal, security, anti-abuse, or operational reasons.

The public site is not intended for children to use without appropriate supervision where local law requires it.

If you believe a child provided personal data through the site or a support workflow in a way that should not have happened, contact me so I can review the report.

I may update this Privacy Policy as the product, vendors, infrastructure, or legal posture changes.

When I do, I will update the published version on the site.

For privacy, security, or legal questions, email creatorflowfeedback@gmail.com.

Even with a local-first architecture, you should still use a trusted device and browser when working with private media.

Do not send private media files, raw file names, tokens, secrets, or unnecessary personal data in support email unless a clearly documented secure workflow explicitly asks for that information.