Privacy
Privacy for the data needed to run the service.
OpenSlash stores account, session, and usage data to run the service, secure access, and support billing.
What we store
- Basic identity and session data used to sign people in and connect them to the right account.
- Account details such as workspace ownership, team members, issued keys, and account settings.
- Usage records tied to requests, models, timing, and account-level consumption.
- Operational logs used to review account changes, key actions, pricing updates, and admin activity.
Why we use it
- Sign people in and keep each workspace limited to the right account members.
- Attach usage to the correct account, key, and workspace activity.
- Run billing, usage reporting, troubleshooting, and service protection.
- Detect misuse, enforce limits, and review account or admin changes when needed.
Key points
- Public pages
- The homepage, privacy page, and terms page are public. Workspaces stay behind sign-in.
- Credentials
- Issued customer keys stay separate from the upstream provider credentials used to run the service.
- Sessions
- Signed-in areas use managed sessions so account and admin actions stay tied to the right user.
- Retention
- Usage and operational records may be kept as needed for service delivery, security review, and billing support, depending on deployment policy.
Questions
- If you need account access, key control, or billing details, sign in and use the protected workspace pages.
- If you are deciding whether to use OpenSlash, review pricing and terms together with this page.