MODELPORTA

Your prompts stay out of our database.

Privacy notice · Updated September 10, 2026

We process your AI requests to deliver an answer. ModelPorta does not save the prompt, tool content or response text as conversation history.

Operated by mike, Guangdong, China. Privacy contact: support@modelporta.com.

What we keep

Your name, email, password hash, session records, API key hashes and prefixes, balances, invoices, token counts, charges, request status and timestamps support account access and billing. Passwords and customer API keys are not stored in plain text. Support messages are saved so we can answer them.

What we do not keep

Our application does not write AI request or response content to its database or application logs, and does not use it to train models. Request content is handled temporarily in memory while the API request is processed. API responses are marked no-store to prevent ordinary HTTP caching.

Who processes a request

Requests pass through OpenLux and its upstream providers. Their own retention rules and prompt caching can apply. Our no-content-storage design is not a promise of zero retention across every provider. Hosting services may retain infrastructure metadata and recovery copies of account records.

Payments and email

USDT TRC20 transactions are publicly visible on TRON and cannot be erased. We use TronGrid to verify payments and, when configured, Resend to deliver verification and password-recovery emails.

Cookies and security

An essential, HTTP-only session cookie keeps you signed in. Hashed identifiers limit abusive requests. We do not add advertising cookies or marketing trackers.

Retention and deletion

ModelPorta does not persist AI prompt text, uploaded request content, tool content, or model replies in its database or application logs. Content is processed in memory to deliver the request. We do not build a conversation archive or use this content to train models. Account details, hashed credentials, balances, token counts, billing records and support messages are stored to operate the service. Session credentials expire after seven days. Email verification codes expire after 10 minutes and password-reset links after 30 minutes. Previously issued verification links expire after 24 hours. Expired sessions, expired or used email tokens, and rate-limit identifiers older than 24 hours are removed in bounded cleanup batches during account/API activity or administrator maintenance. Automatic cleanup attempts run at most once per hour; inactive services and large backlogs can delay physical deletion. Expired credentials cannot be used while awaiting deletion. You can request access, correction or account deletion through authenticated support. Account and financial records are reviewed before deletion to settle remaining balances, prevent duplicate payments, resolve disputes and meet applicable record-keeping obligations. This policy does not promise immediate deletion of financial records. Data included voluntarily in support messages is retained for handling your case; never send prompts, passwords or private keys in support. Requests are forwarded to OpenLux and its upstream model providers. Their retention, security logging and prompt caching are governed separately; ModelPorta cannot promise zero retention by those providers. Hosting services may keep infrastructure metadata and recovery copies of stored account records. TRON payment records are public and cannot be deleted from the blockchain.

Your data requests

Use the support tab in your account to request access, correction or deletion. We verify ownership before acting. Include account, invoice or request IDs only; do not paste prompts, passwords, secret keys or wallet recovery phrases into support messages.