Privacy Policy

This Privacy Policy explains how Kodeln Inc. (“Logtryl”, “we”, “us”, or “our”) collects, uses, and shares information through the Logtryl web dashboard, desktop app, mobile apps, and website (together, the “Service”).

Two kinds of data, two roles. For your account data (like your name, email, and login) we are the data controller: we decide why and how it’s processed, as described below. For the content your team creates — tickets, comments, attachments, and diagnostic/debug data captured while reproducing an issue — your organization (the Account owner) is generally the data controller, and we act as its data processor, following its instructions and this policy. If you’re an end user whose data was captured by one of our customers (for example, in a bug report or debug recording), your request about that data should usually go to that organization first; we’ll assist them as needed.

Account & profile information. Name, email address, mobile number (optional), password (stored as a salted hash, never in plain text), role, and notification preferences. If you sign in with Google, we receive your Google account’s basic profile information (name, email) from Google.

Ticket & project content. Titles, descriptions, comments, statuses, priorities, tags, and file attachments that you or your team create, upload, or store in the Service.

Diagnostic & debug data. Logtryl includes optional tools for reproducing bugs — a desktop Debug Tool and in-app screenshot/screen-recording capture. When used, these can collect: browser/app console logs; network requests and responses (including headers and, where applicable, request and response bodies) for the page or app being debugged; JavaScript exceptions and stack traces; a structured record of clicks, inputs, and navigation during a recording session; device and OS information; and screenshots, screen recordings, or other attachments you choose to add to a ticket. This data can incidentally include anything visible on screen or present in a network request at the time of capture — including personal data or credentials if they happen to be present. Avoid reproducing issues using real customer data, passwords, or payment details where you can use test data instead.

Device & push notification tokens. If you enable push notifications, we store a device token (via Firebase Cloud Messaging) to deliver them.

Usage & analytics data. We use Firebase Analytics in our apps to understand feature usage (e.g. screens viewed, actions taken) at an aggregate level.

Billing information. The Service is currently free and we do not collect payment information today. If and when paid plans launch, billing details will be collected and processed directly by our payment processor (Stripe) — we don’t store full card numbers ourselves.

Support communications. If you email us or otherwise contact us for support, we keep that correspondence to respond to you and improve the Service.

We use the information above to:

• provide, operate, and maintain the Service;
• authenticate you, secure your account, and prevent abuse;
• send transactional communications (e.g. activation codes, ticket notifications, password resets) and, if you opt in, product updates;
• provide customer support, including investigating bug reports using the diagnostic data described above;
• understand aggregate usage so we can improve the Service; and
• meet legal and security obligations.

Where the GDPR or UK GDPR applies, we rely on the following legal bases: performance of a contract with you (providing the Service you signed up for); our legitimate interests (securing the Service, preventing abuse, and improving our product, balanced against your rights); consent (for optional communications or where otherwise required); and compliance with legal obligations.

We don’t sell your personal information. We share it only in these circumstances:

Within your Account. Ticket content, comments, and debug data are visible to other members of your Account/team according to your Account’s own permissions.

Service providers (sub-processors). We use third parties to run Logtryl, currently including:

• Amazon Web Services (AWS) — application hosting, database, and file/attachment storage;
• Google — optional sign-in (Google OAuth), push notifications, and analytics (Firebase);
• Resend — transactional email delivery (e.g. activation codes, notifications); and
• Stripe — payment processing, once paid plans launch.

These providers can only use data as needed to provide their service to us, under their own confidentiality and data protection obligations.

Integrations you choose to enable. If you connect an optional integration (for example, Jira), the data you configure it to sync will be sent to that third party under its own terms and privacy policy.

Legal reasons. We may disclose information if required by law, to enforce our Terms, or to protect the rights, property, or safety of Logtryl, our users, or others.

Business transfers. If we’re involved in a merger, acquisition, or asset sale, your information may be transferred as part of that transaction; we’ll notify you if this happens and results in a materially different use of your data.

Logtryl is operated from the United States and our infrastructure (AWS) currently runs in the US. If you’re accessing the Service from the EEA, UK, Switzerland, or elsewhere outside the US, your information will be transferred to and processed in the US. Where required, we rely on appropriate safeguards for such transfers — such as Standard Contractual Clauses — and we work with providers that offer equivalent commitments (AWS, Google, and Stripe each maintain their own SCC-based transfer mechanisms for their services).

We retain account and ticket data for as long as your Account is active, and for a reasonable period afterward in case you reactivate it or as needed for legal, security, or operational reasons. Diagnostic/debug data attached to a ticket is retained alongside that ticket and deleted when the ticket or Account is deleted, subject to normal backup-cycle delays. You can request deletion of your account at any time — see Section 9.

We use industry-standard measures to protect your data — including encryption in transit, access controls, and hashed password storage — but no method of transmission or storage is 100% secure, and we can’t guarantee absolute security, particularly while the Service is in its free alpha stage (see our Terms & Conditions). If we become aware of a breach affecting your personal data, we’ll notify affected users and relevant authorities as required by applicable law.

Depending on where you live, you may have rights to access, correct, export, restrict, object to, or delete your personal data, and to withdraw consent where processing is based on consent. This includes rights under the GDPR/UK GDPR for individuals in the EEA and UK, which also gives you the right to lodge a complaint with your local data protection authority.

Deleting your account yourself. You can delete your profile and account data directly from the dashboard:

1. Log in to your account at dashboard.logtryl.com;
2. Go to Settings;
3. Select the “Account” tab; and
4. Choose the option to delete your profile and data, and confirm.

To exercise any of these rights, contact us at support@logtryl.com. If your data was submitted by an organization using Logtryl (for example, as part of a bug report), we may direct you to contact that organization first, since they control that content — we’ll still assist as needed.

If you’re a California resident, the CCPA/CPRA gives you the right to know what personal information we’ve collected about you, to request deletion or correction of it, and to not be discriminated against for exercising these rights. We do not sell or “share” personal information as those terms are defined under California law. Residents of other US states with similar privacy laws have comparable rights; contact us to make a request.

Our web dashboard uses browser local storage (not cookies today) to keep you signed in. Our marketing website does not currently set analytics or advertising cookies. If this changes, we’ll update this section and, where required, ask for your consent first.

Logtryl isn’t directed at, or intended for use by, children under 16, and we don’t knowingly collect personal data from them. If you believe a child has provided us personal data, contact us and we’ll delete it.

We may update this policy from time to time, particularly as the Service moves out of its free alpha period or we add new sub-processors or features. We’ll update the date at the top of this page when we do, and, for material changes, will make reasonable efforts to notify account owners in advance.

Questions about this policy or your data? Reach us at support@logtryl.com or 123 Market Street, Suite 400, San Francisco, CA 94105.