Privacy.

Shvydko's operator

Shvydko is provided and maintained by Codebridge Technology, Inc. For questions about the service, terms of access or data processing, email business@codebridge.tech or use the contact page.

Data involved in using the service

Signing in to the console uses your account information. Running an evaluation sends your context, questions and criteria to the service. Creating a shared request is a separate action you take in the console.

Where requests are processed

During the current early-access period, evaluation runs on the service's computing infrastructure in Czechia. Your context, questions and criteria are sent there for processing.

Sign-in and service emails

If you choose Google sign-in, we store your name, verified email address and Google identifier for your account. For corporate OIDC sign-in, we store the provider and user identifiers, name and verified email. Linking to an existing account requires a separate action after you sign in. Twilio SendGrid sends email confirmation and account recovery messages: it receives the recipient's address and a message with a single-use link. Open and click tracking are disabled for these messages.

Workspace invitations are also sent through SendGrid. The message contains the workspace name, role and a single-use link. Mail-provider acceptance is shown separately from the member's acceptance of the invitation.

When signed SendGrid events are configured, we store a random message identifier, an address hash, the message type, timestamp and delivery status for 90 days. The message itself and the full event payload are not stored in this log. Acceptance by the recipient's mail server does not confirm inbox placement or reading. SendGrid processes email-event data in the United States; locally deleted records may remain in seven backups until they rotate out.

Contacting the team

The contact form stores your name, reply address, subject, message, timestamp and inquiry number in the primary database for 90 days. Deleted records may remain in backups until their scheduled rotation; seven daily backups are retained. The message is sent to the team at Codebridge Technology, Inc. through SendGrid; a copy may remain in the support mailbox while your inquiry is handled. The page's confirmation means that your inquiry was saved, not that the team has already read it. Do not send passwords, API keys or customer documents.

Evaluation datasets and reports

JSONL import and viewing a saved report happen in your browser. When you run an evaluation, each example's context and questions are sent to the model; expected answers are not. This feature does not store the dataset or full report on the server. A downloaded report contains your inputs and responses.

What the console stores

The API gateway does not store the context text or questions from ordinary requests. Usage accounting stores technical request data, including timestamps, token counts and costs. If you separately create a shared request, its context and questions are stored. By default, only signed-in members of your organization can see them. If you choose public access, anyone with the link can read them. The author or an administrator can delete the link in the console.

Billing details

Payments are received by Codebridge Technology, Inc. through Stripe's secure checkout page. Your organization name, billing email, amount and payment identifiers are sent for payment processing. The console stores the history of top-ups, usage charges and refunds, with the related Stripe identifiers. Card numbers do not pass through the Shvydko API. You can manage payment methods saved in Stripe through the billing portal linked from the console.

The payment provider's data processing is described in the Stripe Privacy Policy .

Data requests

To request access to your data, deletion or account closure, email business@codebridge.tech from your account's email address. Signing out does not delete data. Agree on any specific retention, deletion and operational-data processing requirements before starting a pilot; use learning scenarios or de-identified data while exploring the service.