Skip to content
agentport.cloud

Plain-language notice

Privacy at AgentPort

This notice explains the information the AgentPort service handles when you visit the site, create an account, pay for credits, deploy an app, or contact us.

Updated October 22, 2026

Information AgentPort handles

Account and authentication data

Your name, email address, password credential, optional profile image, email-verification state, linked sign-in provider details, and session records. Session records can include an IP address, browser or device user agent, and expiry time. We also keep onboarding answers, newsletter preference, beta-seat or waitlist status, and API-key metadata. API keys are stored as hashes with a prefix and last four characters for identification.

Deployment and service data

Project and service names, container images, ports, public visibility, domains, status, deployment configuration, environment values, secret hashes, and registry image records. Your containers may process the application data you choose to send them. Container logs contain whatever your app writes to standard output or error; AgentPort reads those logs when you request them and the runtime keeps bounded rotated log files.

Payment and billing data

Credit balances, spending limits, ledger entries, invoice amounts and status, project or service references, and Stripe checkout, setup, customer, and payment identifiers. Stripe hosts card verification and payment checkout and handles full card details. AgentPort stores verification results, card funding type, and a Stripe card fingerprint to prevent duplicate beta grants. A fingerprint claim may remain after account deletion to prevent repeated grants; it does not contain your full card number or security code.

Feedback and support data

Feedback text, an optional email address, the page path where feedback was sent, support ticket subjects and messages, priority and status, and timestamps. Please do not include passwords, API keys, private keys, or unnecessary personal information.

How the information is used

  • Provide accounts, sessions, authentication, deployment, domains, logs, and support.
  • Process beta access and payments, maintain balances, and prevent duplicate charges.
  • Protect the service, investigate failures or abuse, and maintain operational records.
  • Respond to feedback and support requests and improve AgentPort.
  • Send sign-in or recovery email only when email delivery is configured and requested.

Cookies and external providers

Necessary cookies

AgentPort uses necessary cookies to keep you signed in, maintain session continuity, and protect account actions. Cloudflare Turnstile may run on protected sign-in, registration, magic-link, or password-recovery actions when that protection is enabled.

Stripe processes checkout. Optional GitHub, Google, or ChatGPT sign-in sends you to the provider you choose. Google hosts the web fonts loaded by the site. When sign-in or recovery email is enabled, the configured email-delivery provider receives the recipient address and message needed to deliver it. That provider is used only to send the requested account email.

Advertising measurement

If you accept advertising cookies, AgentPort loads the X pixel on its production website to measure visits from X ads. X may receive browser and device information, your IP address, and cookie or advertising identifiers, and may use cookies for attribution and advertising. We configure the pixel to hide the page URL and do not add your account email, API keys, deployment data, or payment details to pixel events. You can manage X's personalized-ad settings through the advertising preferences link below.

Advertising tracking is off until you accept. We remember your choice in a necessary preference cookie for 180 days. You can reject advertising without losing access to AgentPort, or change your choice below. Withdrawing consent reloads the page to stop the pixel; it does not undo data already sent to X.

Storage, disclosure, and retention

AgentPort shares information with service providers only as needed to provide functions such as hosting, authentication, fraud prevention, email delivery, payment processing, and advertising measurement, or when disclosure is required to protect the service or comply with applicable law.

We do not publish one fixed retention period for every category. Records are kept for as long as needed to operate and secure AgentPort, maintain billing and deployment history, resolve support requests, and meet applicable obligations. Different records may therefore be retained for different lengths of time.

Your choices and contact

You can choose not to use an optional OAuth provider, not to join the newsletter, and not to include an email address with feedback. You can remove deployed resources with the service controls available to you. For questions or requests about your account or personal information, email [email protected]. We may need to verify your identity before acting on an account request.