Accounts
How PortModels accounts work, what they hold, and how one account serves every app in the gallery.
One PortModels account gives you access to the whole gallery. Apps do not have their own sign-up, their own password, or their own subscription.
What an account holds#
- Identity — your PortModels email address, username, and display name.
- Credit balance — the shared balance every app draws from.
- Connected apps — the apps you have authorized, and the scopes each holds.
- App data — per-app key/value entries and files stored on your behalf.
- History — the runs made on your account and what each cost.
Signing in to an app#
You never give an app your PortModels password. When an app needs your account it redirects you to a PortModels screen, you approve it there, and the app receives a token limited to the permissions it asked for. That flow is Connect with PortModels.
A downloadable app that cannot open a browser redirect uses the device flow instead: it shows a short code, you enter that code on a PortModels page, and the app is authorized once you approve.
Developer accounts#
Publishing requires a developer profile with a publisher namespace — a unique
handle that prefixes every app you publish. Your app's identifier is
publisher/app-name, so two developers can both publish an app called
summarizer without colliding, and a name you own cannot be taken over later.
See Publish an app.
Deleting your account#
Contact [email protected] to delete your account. Deletion removes your profile, your stored app data, and your authorizations. Unused credits are not refundable — see the Terms.