Privacy Policy

Effective October 30, 2026. Updated November 4, 2026.

Meldport is operated by its owner as an individual. For privacy requests, contact privacy@meldport.com.

Data we collect

We process the details needed to run your account and the features you use. This can include your email address, name, external account ID and profile image if you choose social sign-in; project names and API-key labels, scopes and status; model and route IDs, request time, status, token or media usage, quoted and settled amounts, and processing costs; payment references and status; security and audit events; and messages you send to support. We do not store application diagnostic logs in the application database, and ordinary application logs do not store prompt or completion bodies. Saved chat and generation content is described below.

Cookies and local storage

Meldport uses essential browser storage for sign-in sessions, cross-site request protection, the temporary social sign-in flow, and your theme choice. Access cookies last up to 15 minutes, refresh cookies up to 30 days, cross-site request tokens up to one hour, and social sign-in state up to 10 minutes. The theme cookie lasts up to one year, and the browser also stores the theme choice locally. The application does not load third-party advertising or visitor analytics scripts.

How we use data

Email signup uses an anti-bot check to detect automated registrations. The verification service processes browser and network information for this check. Meldport validates the result on its server before creating an email account.

We use data to authenticate users, deliver requests, calculate charges, prevent abuse, reconcile payments, support customers, improve reliability, and meet legal obligations. The required signup agreement records your consent for email product updates, feature announcements, offers, and promotions. Account, security, billing, maintenance, and other service notices are sent to operate your account. Meldport does not sell account information or give your email address to another company for that company's marketing.

External processing and international transfers

Meldport uses external services for sign-in, email delivery, payments, hosting, private media storage, model routing, and generation. Each service receives the data needed to perform its part of the request. Processing may take place outside Indonesia. Available regions and retention depend on the service, route, and account configuration. We do not promise a specific processing region unless it has been verified.

Our email delivery service receives the email address, delivery details, and message needed to send account notices and, where you have agreed, product announcements and promotions. It processes that data for Meldport to deliver the message. It does not receive your model prompts for this purpose.

Model execution and routing services receive the prompt, conversation context, and attachments needed to answer your request. Some chat routes log model IDs, token counts, costs, status, time, and caller region. Security investigations may retain system prompts, tool definitions, and request parameters for up to 7 days. Safety screening may retain matching-rule metadata for 90 days and screened messages and system prompts for 14 days. Tool results, file contents, and attachments are excluded from those specific screening and retention processes. These route-specific practices are separate from Meldport application logs and may change. Do not assume every model route has the same retention or training terms.

Media generation services receive the prompt, supplied input media, selected model, and options needed to create an image, video, or audio result. Generated media may remain on their systems for seven days. Task records may also include the original request and response; their retention period has not been verified for Meldport. We do not request those task details during normal generation. We have not verified zero data retention for these services, so do not assume request content is discarded immediately after generation.

Retention and security

Meldport keeps media-job prompts and options, input and generated assets, and the generation task reference for up to eight days after a result is ready. At expiry, the prompt and options are redacted and the stored assets are deleted. An upload that is not attached to a completed job expires after 15 minutes. Closing an account removes active access immediately and queues remaining media for deletion after any job or billing reconciliation is complete.

Saved Web Chat history is kept for up to 100 threads per project and 100 messages per thread. A thread expires after 30 days without activity. This saved history is separate from ordinary application logs, which do not store prompt or completion bodies.

For email announcements and promotions, we store whether you agreed, the consent version and time, and when you last changed the preference. We use this record to send email according to your choice and to show when consent was given or withdrawn. You can turn off promotional email in Account settings. We retain the minimum consent record needed to honor that choice and handle legal claims.

Usage, wallet, payment, processing-cost, dispute, and administrator audit records are kept for billing, reconciliation, security, dispute handling, and legal obligations. These records do not have an automatic deletion period in the current service. Operational application and access logs are kept outside the application database and rotated by the hosting environment. Backups may retain deleted records for up to 14 days on the host and 31 days off the host before the backup expires.

If you submit a social post for an optional token campaign, we keep its public URL and platform, the account-bound verification code and required destination, verification status, and any administrator review decision. We check readable public post content through the official platform endpoint or manual review; we do not retain the raw embed HTML. Keyed social-author, post, device and network identifiers help detect repeated claims. These signals do not establish a unique human or hardware identity. Campaign verification and review records are retained for abuse prevention and audit without an automatic deletion period in the current service. The regular monthly free allowance does not require a social post.

If a personal data incident occurs, we will notify affected people and the relevant authority where required by applicable law. We use access controls, protected credential storage, audit trails, and data minimization, but no system is risk-free.

Website audience measurements

When enabled, we measure public-page visits with random first-party visitor and session cookies, page paths without query strings, referring site names, coarse browser/device information, and country information supplied by the hosting edge when available. Browser activity helps estimate active visitors and separate likely human visits from recognized bot patterns; this classification is not proof of identity. These measurements do not include model prompts, chat contents, payment details, or raw visitor IP addresses.

The visitor cookie expires after 30 days without renewal, and the session cookie after 30 minutes without renewal. Page observations older than 90 days and inactive sessions older than 90 days are removed by periodic traffic-driven cleanup. Collection honors browser Do Not Track and Global Privacy Control signals. Blocking cookies or scripts can reduce the accuracy of these estimates.

Your choices

When measurements are enabled, a temporary opaque reference can connect a public landing visit to a subsequent account registration on our console host. It expires after 15 minutes and can be used once. We use account, API key, successful request and finalized wallet records to report aggregate activation outcomes, without adding prompts, API key secrets or payment details to analytics. Unmatched visits remain unknown. Account links older than 90 days are removed during traffic-driven cleanup. An opt-out recorded during authentication or an authenticated API request suppresses that account's analytics outcomes; the minimal opt-out preference is retained to avoid collecting them again. Contact privacy@meldport.com to change that preference. Existing security, accounting and service records follow their separate retention rules.

You can update account details, revoke API keys, request an export, or request closure from the dashboard. For access, correction, deletion, restriction, objection, withdrawal of consent, or other privacy requests, contact privacy@meldport.com. We will verify the request before acting.