Access Controls Policy

Last updated: Apr 17, 2026

Softserve Software LLC
Purpose and Scope

This Access Controls Policy describes how Softserve Software LLC (“we,” “our,” or “us”) governs logical and administrative access to the car storage facility management software and related services (the “Service”), the systems that run the Service, and the data stored within them.

This policy applies to all personnel, contractors, and third-party providers who access the Service, its production infrastructure, source code, or customer data, and to all customer users who access the Service through their accounts.

This policy supports and should be read together with our Information Security Policy, Privacy Policy, and Terms of Service.

Guiding Principles
  • Least privilege: users, systems, and service accounts are granted only the minimum permissions required to perform their role.
  • Need to know: access to customer data and production systems is limited to personnel with a documented business need.
  • Segregation of duties: where practical, sensitive operations (for example, payments, user role changes, and production deployments) are separated from routine development activities.
  • Tenant isolation: the Service is multi-tenant and every customer-facing record is scoped to a team identifier, so one customer cannot access another customer's data through the application.
  • Auditability: access to production systems and changes to user privileges are logged.
  • Default deny: access that is not explicitly granted is denied.
User Access (Customer Accounts)

Authentication

  • End users authenticate to the Service using magic-link email authentication (no long-lived passwords are stored).
  • Sessions are established with signed, time-limited session cookies marked HttpOnly and Secure.
  • All authentication traffic is transmitted over TLS.
  • Expired or invalidated sessions are rejected on the server side.

Authorization and Roles

  • Users belong to a team (the customer organization) and may optionally be scoped to a specific facility location within that team.
  • Role-based permissions control which features a user can access within their team (for example, administrator, operator, read-only).
  • Server-side checks enforce that every read and write is restricted to the authenticated user's team and, where applicable, their location.
  • Customer-facing endpoints always filter by team identifier so that a user of one customer can never retrieve another customer's data.

Account Provisioning and Deprovisioning

  • Team administrators are responsible for inviting, suspending, and removing users within their own team.
  • Removing a user terminates their access to the Service and invalidates their sessions.
  • Customers are responsible for promptly removing access for personnel who change roles or leave their organization.
Administrative and Infrastructure Access

Who Has Production Access

Production access is restricted to authorized Softserve Software LLC personnel with a documented business need. Access is granted on a named-user basis through each underlying provider and is reviewed periodically.

Authentication for Administrators

  • All administrative consoles used to operate the Service (hosting, database, email, SMS/voice, AI, payments, error monitoring, source control) require named user accounts.
  • Multi-factor authentication (MFA) is enabled on all administrative accounts where the provider supports it.
  • Shared administrator credentials are prohibited.

Application-to-Infrastructure Access

  • The application connects to its managed Postgres database over TLS with full certificate verification.
  • Credentials, API keys, and secrets are stored in the hosting provider's encrypted environment variable store, scoped per environment (development, preview, production).
  • Secrets are never committed to source control.
  • Third-party API credentials (for example, for payments, AI, SMS, email) are scoped to the minimum capabilities required and can be rotated or revoked independently.

Source Code and Deployment

  • Source code is stored in a private repository with access limited to authorized contributors.
  • Deployments to production are performed through the integrated CI/CD pipeline from protected branches.
  • Environment variables in production are only visible to authorized administrators.
Password and Credential Standards
  • The Service itself does not require end-user passwords; it uses email-based magic links for authentication.
  • Where the underlying infrastructure providers issue passwords to administrators, those passwords must be unique, generated by a password manager, and protected by MFA.
  • API keys, webhook secrets, and database credentials are treated as sensitive secrets and are rotated promptly if they are suspected to be compromised or when personnel with access depart.
  • Credentials are never transmitted over insecure channels (for example, unencrypted email or chat).
Access Reviews
  • Administrative access to each production provider is reviewed at least annually, and after any material personnel change, to confirm that only current authorized personnel retain access.
  • Customer team administrators are encouraged to review their own user list on a regular cadence and remove accounts that are no longer required.
  • Unused or dormant administrative accounts are disabled.
Offboarding and Revocation
  • When a person with administrative access leaves or changes roles, their access to all production systems, repositories, and secret stores is revoked promptly.
  • Any shared infrastructure secrets that the departing person could have known are rotated.
  • Customer-side offboarding of end users is performed by the customer's own team administrator through the Service.
Logging and Monitoring
  • Authentication events (for example, sign-in attempts and session creation) are logged by the Service.
  • Application and platform logs are retained by our hosting and database providers in accordance with their standard policies and are used to detect and investigate suspicious activity.
  • Application errors are captured and reviewed to identify anomalies that may indicate misuse or compromise.
Exceptions and Enforcement

Any exception to this policy must be approved in writing by Softserve Software LLC management, documented with a justification, and reviewed periodically. Violations may result in revocation of access, termination of the relationship, and legal action where appropriate.

Changes to This Policy

We may update this Access Controls Policy from time to time to reflect changes in our practices, the Service, or applicable law. The “Last updated” date at the top of this page indicates when it was most recently revised.

Contact Us

Questions about this Access Controls Policy, or requests related to access to your data, can be directed to:

Softserve Software LLC

Email: matt@softservesoftware.com

Address: 3343 Port Royale Dr S, Fort Lauderdale, FL 33308