Security

All data transmitted between your browser and Agency Assistant is encrypted using TLS (HTTPS). Database connections are also encrypted. We do not allow unencrypted connections to the platform.

Google Calendar OAuth access and refresh tokens are encrypted before storage. Hosting-provider encryption at rest is part of the security commitments in our Data Processing Agreement; contact us for information about the infrastructure relevant to your workspace.

Account authentication is handled by Clerk, a dedicated identity provider that supports secure session management. Staff accounts have role-based permissions, meaning team members only see and can change what their role allows. Artist portal access is separately controlled and scoped to each artist's own data.

The platform runs on Replit's cloud infrastructure. Database access is restricted to application-level queries. There is no direct public access to the database. We use environment-isolated secrets for all credentials and API keys; these are never stored in code.

Your business data (artists, bookings, contracts, invoices, and financial records) is logically isolated to your agency. Staff at other agencies cannot access your data. Workspace members, artists, promoters and document recipients see information according to their access and the documents or links you share. Someone who receives a public or bearer link can access its shared content.

We do not sell personal data. Service providers include Replit for hosting, database and file storage, Clerk for authentication, Resend for transactional email, and Stripe for subscription billing and optional online invoice payments. Optional Google Calendar sync and AI processing are described below. The Privacy Policy also describes legally required disclosures and other permitted sharing; the DPA sets out our processing obligations.

After you authorize Google Calendar, we read calendar identifiers, names and access permissions so you can select a writable calendar. We create, read, update and remove Agency Assistant booking and hold events there. Synced events can include titles, dates, times, locations, descriptions and links. We store encrypted OAuth tokens, the selected calendar identifier, event references and synchronization status.

Google Calendar information is used to provide and maintain requested calendar features, not for sale, advertising or training generalized AI or machine-learning models. Human access is limited to consent for a specific purpose, necessary security or abuse investigations, or applicable law. See the Google Calendar privacy disclosure, including our commitment to the Google API Services User Data Policy and its Limited Use requirements.

When you use the assistant, your request and relevant workspace content may be sent to OpenAI through the Replit AI integration. This can include conversation context, workspace records needed to answer the request and extracted text from authorized contract attachments when you request document review. Uploading a file alone is not a request for AI review.

Only submit information appropriate for the requested feature. The Google Calendar purpose limitation above applies separately; it is not a claim about all workspace content submitted to AI tools. See our Privacy Policy for service-provider disclosures.

Google Calendar controls are temporarily hidden. This does not delete stored connection data or itself stop an existing authorized sync. When the controls are restored, disconnection attempts to remove events the app created for your workspace before deleting the stored connection and tokens. If Google cannot be reached or cleanup fails, disconnection can remain pending and require a retry. We do not intentionally remove unrelated events. Disconnecting does not delete your workspace bookings.

Revoking access through your Google Account connections stops future authorized access, but does not itself remove stored Agency Assistant data or existing Google Calendar events. Contact hello@agency-assistant.app for deletion requests, including stored connection information.

Account deletion, legally required records and backup retention are described in the Privacy Policy. The DPA retains its data return and deletion commitments; disconnecting a service is not a substitute for a workspace deletion request.