Terms of Service
In short
- Sessionly is operated by Kristiyan Ivanov, an individual. These terms are an agreement between you and me.
- The software is open source. When you run it yourself, its software licenses govern, not these terms. These terms cover this website, the licenses I sell, and the hosted service, which is not open yet.
- Sessionly records the work of people. You are responsible for having the right to collect your engineers' sessions and for telling them. Its figures are measurements with stated limits, not a verdict on anyone.
- The Service is provided “as is”. My liability is limited to what you paid me in the three months before a claim.
Please read these Terms of Service (the “Terms”) carefully. The website at
sessionly.dev and its subdomains (the “Website”), the hosted Sessionly
service, when I offer it, including its dashboard and API and the
sessionly command-line program and GitHub Action when they talk to it (the
“Hosted Service”), and the Business and Enterprise license files I issue
(“Licenses”) (together, the “Services”) are operated by
Kristiyan Ivanov, a self-employed individual registered in Bulgaria (BULSTAT 180490275)
(“I,” “me,” or “Sessionly”). These Terms, together
with the Privacy Policy, the
Data Processing Agreement and any supplemental terms presented to you
for acceptance (together, the “Agreement”), govern your access to and use of
the Services. By creating an account, buying a License, or otherwise accessing or using
any of the Services, you represent that (1) you have read, understand and agree to be
bound by the Agreement, (2) you are of legal age to form a binding contract with me, and
(3) you have the authority to enter into the Agreement personally or on behalf of the
organization you named when registering or ordering, and to bind that organization.
“You” refers to that individual or organization. If you do not agree, you
may not use the Services.
Section 12 (Disclaimer of Warranties) and Section 13 (Limitation of Liability) limit what I am responsible for. Section 3 (The People in Your Sessions) sets out what you are responsible for when you collect other people's sessions, and Section 5 (What the Figures Are and Are Not) explains what Sessionly's numbers do and do not show.
The Hosted Service is not open yet. The parts of these Terms about the Hosted Service apply from the moment I give you an account on it.
Changes. I may change the Agreement. When I do, I will post the updated version on the Website and update the “Last updated” date. For material changes I will also email the address on your account. Changes take effect immediately for new users and, for existing account holders, 30 days after the new date unless you accept them earlier through a mechanism I provide. If you do not agree to the updated Agreement, stop using the Services before it takes effect; continued use after that date is acceptance.
- 1. The Services and the Software
- 2. Accounts
- 3. The People in Your Sessions
- 4. Your Data
- 5. What the Figures Are and Are Not
- 6. Acceptable Use
- 7. Fees and Purchase Terms
- 8. Limits, Retention and Changes to the Services
- 9. Ownership and Feedback
- 10. Communications
- 11. Third-Party Services
- 12. Disclaimer of Warranties
- 13. Limitation of Liability
- 14. Indemnification
- 15. Term and Termination
- 16. Dispute Resolution and Governing Law
- 17. General Provisions
1. The Services and the Software
1.1 What Sessionly is
Sessionly is a ledger of AI coding agent sessions. A program on a developer's machine records what coding agents such as Claude Code, Cursor and Grok were asked, which tools they ran, which files they changed and what it cost, and measures how much of what they wrote is still there later. It can upload a record of each session to a Sessionly server, which shows the same figures for a team. The Hosted Service is my installation of that server, which you use through your account.
1.2 Open-source software and self-hosting
The Sessionly software is published at
github.com/KIvanow/sessionly.
Everything outside the ee/ directory is licensed under the Apache License
2.0; the ee/ directory is licensed under the separate LICENSE-EE and
requires a License to use beyond evaluation. Those software licenses, not these Terms,
govern your use of the software itself when you run it on your own machines and
infrastructure. These Terms govern the Website, the Hosted Service and the issuing of
Licenses. Where an open-source license and these Terms conflict regarding the software,
the open-source license controls.
1.3 Licenses
A Business or Enterprise License is an Ed25519-signed file, verified offline by your
install, that enables the ee/ features for the org, the number of people
and the period it states. A License is issued when the corresponding invoice is paid
and is valid to the end of the paid period. After it expires, its features keep working
for a 14-day grace period and then become read-only; capture, the local ledger, upload,
the server, the dashboard and all other Apache-2.0 features keep working regardless.
You may not share, resell or alter a License, or attempt to circumvent its
verification.
1.4 Updates
The Services are evolving. I may update the Hosted Service at any time, with or without
notice. You may need to update the sessionly program, the GitHub Action or
other software from time to time to keep using the Hosted Service.
2. Accounts
2.1 Registration
To use the Hosted Service you need an org and an admin token, issued to an email address. You agree to (a) provide true, accurate, current and complete information, and (b) keep it that way. You represent that you are at least 18 years old, of legal age to form a binding contract, and not barred from using the Services under any applicable law. If you provide information that is untrue, inaccurate or incomplete, or I have reasonable grounds to suspect so, I may suspend or terminate your account.
2.2 Tokens
Access is by token. Each token belongs to one person and is an admin, a member or a ci token: an admin sees every session in the org and manages tokens, a member uploads and sees their own sessions, and a ci token reports pull requests and does nothing else. Tokens are credentials: anyone holding one can act as its owner. You are responsible for keeping them secret, for every request made with them, and for everything that happens under your account, including the actions of automated agents and of the people you give tokens to. Notify me immediately at kristiyan@sessionly.dev of any unauthorized use, and revoke the affected tokens in the dashboard.
2.3 Teams
An org's admins create tokens for other people, choose their role and revoke them. The admin giving someone access is responsible for having the right to share the org's data with that person. Keep at least one admin token you can use.
2.4 Your account
You have no ownership or property interest in your account or org identifier; they exist for the purpose of providing you the Services. You may close your account at any time (Section 15.3).
2.5 Equipment
You must provide all equipment, software and connectivity necessary to use the Services, and you are responsible for any fees you incur doing so, including what the makers of your coding agents and their models charge you.
3. The People in Your Sessions
Sessions describe the work of people. A session record names the person whose machine it came from (their git name and email address) and shows when they worked with an agent, on which repository and files, for how long, at what cost and, if previews are on, the start of what they typed. Where you collect sessions from anyone other than yourself, you:
- represent that you are entitled to collect and upload those sessions, and that you have a lawful basis for doing so;
- are responsible for telling the people concerned, before their sessions are collected, what is collected, what is uploaded, who can see it and what it is used for, and for meeting any duty to inform or consult employees or their representatives that applies to you;
- decide the content level. The default upload contains no text; previews and line hashes are switched on per machine, and you are responsible for the choice to use them, including for anything a preview turns out to contain;
- remain bound by your agreements with the makers of your coding agents and with your own customers and employers, including any confidentiality obligations about the repositories your sessions come from.
Sessionly is designed so that this can be done fairly: capture is visible in the
agent's settings file, sessionly export shows anyone exactly what their
machine would upload, and full content never leaves the machine. That is not legal
advice; you are responsible for your own compliance with employment, privacy and
data protection law.
4. Your Data
4.1 What I store
The Hosted Service stores your tokens (as hashes) with the email address, name and role each belongs to; the session records your machines upload; and the pull request reports the GitHub Action sends. With the default content level a session record contains counts, timings, tool names, relative file paths, models, tokens, cost, rewrite figures and the git name, email and remote, and no text from prompts, commands or files. Previews and line hashes are stored only if the uploading machine switched them on. It never stores full prompts, file contents, command output or source code. The Privacy Policy has the details.
4.2 Ownership and license
You own your data. You grant me a non-exclusive, worldwide, royalty-free license to host, store, process, transmit and display it only as needed to provide the Services to you and your org, and as described in the Privacy Policy. Where your data includes personal data of your engineers or others, you are the controller and I process it on your behalf under the Data Processing Agreement, which forms part of this Agreement; you are responsible for having a lawful basis to do so.
4.3 Your responsibility for what you send
You, and not I, are responsible for everything your machines, agents, workflows and team members upload to the Hosted Service. I have no obligation to monitor it, but I may inspect metadata to operate the Services, enforce this Agreement and keep the Services secure.
5. What the Figures Are and Are Not
Sessionly's value is in its numbers, so this section states plainly what they do and do not show.
- Cost is a measurement, not an invoice. Where a coding agent records its own cost, Sessionly reports it; elsewhere it estimates cost from token counts and the model makers' published prices, and marks the result as an estimate. Prices change, some usage does not appear in any transcript, and a subscription is not billed by the token. For some agents the figure covers only part of a session, and Sessionly says which part. Your provider's bill is the authoritative record of what you spent.
- The rewrite rate measures survival, not quality. It counts how many of the lines an agent added are still in the file. Code is rewritten for reasons that have nothing to do with how it was written, and a session that just ended scores 100%.
- The agent share of a pull request is a floor. A line counts as an agent's only when an uploaded session added it; people without Sessionly, sessions uploaded without line hashes, changes made by shell commands and generated files all count as not an agent's. Lines are matched by short hashes, so a common line can match by coincidence.
- Comparisons between models, agents and people are descriptions, not rankings. Harder work goes to stronger models and to more experienced people, and small samples say little.
- Identity is a label. The name and email on a session come from git configuration on the machine and are not verified. On a server, uploads are filed under the owner of the token that sent them.
- Coverage depends on the agents. Sessionly reads what the coding agents record. They change their formats without notice; an update to an agent may stop Sessionly from seeing some or all of its sessions until Sessionly is updated.
Accordingly, you should not use Sessionly's figures as the sole basis for a decision about a person's employment, pay or performance, and I make no warranty that any figure is complete or accurate (Section 12).
6. Acceptable Use
As a condition of use, you agree not to use the Services for any purpose prohibited by this Agreement or by law. You shall not, and shall not permit any third party or automated agent to:
- collect or upload the sessions of people who have not been told, or whose sessions you have no right to collect;
- upload special categories of personal data, credentials or other people's secrets to the Hosted Service, for example through previews;
- resell, sublicense, rent or otherwise commercially exploit the Hosted Service itself, or offer it to third parties as a service, without my written consent (running your own self-hosted install under the software licenses is fine);
- attempt to bypass, disable or interfere with access controls, roles, limits or License verification, or to read another org's or another person's data;
- share one account between unrelated organizations, create accounts with false information, or create a new account after I have terminated one for breach;
- infringe or misappropriate anyone's intellectual property, privacy or other rights, or send unlawful, threatening, defamatory, fraudulent or otherwise objectionable content through the Services;
- probe, scan or test the vulnerability of the Services without permission, introduce malware, or interfere with any other user's use of the Services, including by overloading or flooding them;
- use the Services for any purpose prohibited by applicable sanctions or export laws.
7. Fees and Purchase Terms
7.1 What is free and what is paid
The open-source software is free of charge under its licenses. Licenses and, once it opens, paid plans on the Hosted Service are sold by written order: an order form, an accepted quote or an invoice (an “Order”) that states what you are buying, for how many people, for what period and at what price. Prices exclude taxes.
7.2 Payment
Fees are due as the Order states, and otherwise within 30 days of the invoice date, by the payment method the Order or invoice names. If I use a payment processor, its terms govern your use of that payment method (Section 11.2).
7.3 Price changes
I may change prices. A price change does not affect a period you have already paid for; it applies to a renewal only if I told you at least 30 days before the renewal date.
7.4 Taxes
Fees do not include sales, use, value-added or similar taxes. If I am legally obliged to collect such a tax from you, it will be added to the charge. You are responsible for any taxes you owe on your purchases and for paying fees free of withholding; if withholding is required, you will gross up the payment so that I receive the full fee.
7.5 Renewal
A License or plan does not renew automatically unless its Order says so. Where an Order provides for automatic renewal, it also says how to cancel, and cancellation takes effect at the end of the period already paid for.
7.6 Refunds
Except where required by law or stated otherwise in writing, fees are non-refundable. If you are charged in error, contact me and I will put it right.
7.7 Enterprise terms
Terms agreed in writing for an Enterprise License take precedence over this Section 7 where they conflict.
7.8 Free use and promotions
Any free plan, trial or promotion on the Hosted Service is provided at my discretion and may be changed or withdrawn with notice.
8. Limits, Retention and Changes to the Services
The Hosted Service keeps your sessions and pull request reports while your account exists, unless your Order or plan states a retention period, in which case older records are deleted. An upload is limited in size, and I may set other reasonable limits on storage, request rates and similar resources to keep the Services working for everyone. I may modify, suspend or discontinue any part of the Services, and will give reasonable notice of discontinuing a paid feature.
9. Ownership and Feedback
9.1 The Services
Except for your data and the open-source software covered by its own licenses, I and my licensors own all rights, title and interest in the Services, including the Website's content and design, the Hosted Service and documentation. You agree not to remove or obscure any proprietary notices.
9.2 Trademarks
“Sessionly” and the Sessionly logo may not be used in connection with your or any third-party products or services without permission, except to say truthfully that you use or are compatible with Sessionly. Claude Code, Cursor, Grok, GitHub and other product names are trademarks of their owners. Sessionly is not affiliated with, endorsed by or sponsored by any of them.
9.3 Feedback
If you send me ideas, suggestions or feedback about the Services, you do so at your own risk, I have no obligation of confidentiality with respect to them, and you grant me a perpetual, irrevocable, worldwide, royalty-free license to use them for any purpose without obligation to you. Contributions to the open-source repository are governed by its CONTRIBUTING file and DCO sign-off instead.
10. Communications
By using the Services you agree to receive electronic communications from me related to your account and the Services: tokens and License files, invoices, security notices and notices of changes to this Agreement. These are operational, not promotional. I do not currently send marketing email. If I start, it will be opt-in with an unsubscribe link in every message.
11. Third-Party Services
11.1 Coding agents and GitHub
Sessionly reads sessions recorded by coding agents made by third parties, and its Action runs on GitHub and reads pull requests through GitHub's API with the permissions you give it. Those products and services are not under my control, I am not responsible for them, and your use of them is governed by their own terms and privacy policies. Links on the Website to third-party sites are provided as a convenience and are not endorsements.
11.2 Payment processor
If an Order or invoice is paid through a payment processor, you agree to be bound by that processor's terms and privacy policy, and you consent to the processor and me sharing the information and payment instructions you provide to the minimum extent required to complete your transactions.
12. Disclaimer of Warranties
12.1 As is
You expressly understand and agree that, to the extent permitted by applicable law, your use of the Services is at your sole risk, and the Services are provided on an “as is” and “as available” basis, with all faults. I expressly disclaim all warranties, representations and conditions of any kind, whether express or implied, including the implied warranties or conditions of merchantability, fitness for a particular purpose and non-infringement arising from use of the Services.
(a) I make no warranty, representation or condition that: (1) the Services will meet your requirements; (2) your use of the Services will be uninterrupted, timely, secure or error-free; (3) the results that may be obtained from use of the Services, including costs, cost estimates, token counts, rewrite rates, pull request attribution and any comparison between people, agents or models, will be accurate, complete or reliable; or (4) every session of every coding agent will be captured.
(b) No advice or information, whether oral or written, obtained from me or through the Services will create any warranty not expressly made herein.
(c) From time to time I may offer new “beta” or experimental features or tools. Such features are offered solely for experimental purposes and without any warranty of any kind, and may be modified or discontinued at my sole discretion. This Section applies with full force to them.
12.2 No liability for conduct of third parties
You acknowledge and agree that I am not liable, and you agree not to seek to hold me liable, for the conduct of third parties, including the makers of coding agents and models, GitHub, hosting and payment providers, and other users of the Services, and that the risk of harm from such third parties rests entirely with you.
Where the law of your country gives you consumer rights that cannot be excluded, nothing in this Section limits them.
13. Limitation of Liability
13.1 Disclaimer of certain damages
You understand and agree that, to the fullest extent provided by law, in no event shall I be liable for any loss of profits, revenue or data, indirect, incidental, special, exemplary or consequential damages, or damages or costs due to loss of production or use, business interruption, or procurement of substitute goods or services, in each case whether or not I have been advised of the possibility of such damages, arising out of or in connection with the Agreement or the Services, on any theory of liability. Without limiting the foregoing, I am not liable for charges billed to you by the maker of any coding agent or model, for any decision you take about a person, a team, a tool or a budget in reliance on Sessionly's figures, or for anything a preview you chose to upload turns out to contain.
13.2 Cap on liability
To the fullest extent provided by law, my total liability to you for all claims arising out of or relating to the Agreement or the Services will not exceed the greater of (a) the total amount you paid me for the Services during the three (3) months before the act, omission or occurrence giving rise to the liability, and (b) fifty United States dollars (US$50).
13.3 Exceptions
The exclusions and limitations above do not apply to liability for death or personal injury caused by my negligence, for my fraud or fraudulent misrepresentation, or for any other liability that cannot be excluded or limited under applicable law. Some jurisdictions do not allow the exclusion or limitation of certain damages; if those laws apply to you, some or all of the above may not apply and you may have additional rights.
13.4 Basis of the bargain
The limitations of damages set forth above are fundamental elements of the basis of the bargain between you and me. The Services would not be provided, at these prices or at all, without them. This matters all the more because Sessionly is run by an individual, not a company.
14. Indemnification
You agree to indemnify and hold me harmless from any losses, costs, liabilities and expenses (including reasonable attorneys' fees) relating to or arising out of: (a) the sessions, pull request reports and other data you, your machines or your agents upload to the Services; (b) your use of the Services in violation of the Agreement; (c) your collection of other people's sessions, including any claim by those people or their representatives; (d) your violation of any rights of another party; or (e) your violation of any applicable laws or regulations. I reserve the right, at my own cost, to assume the exclusive defense and control of any matter otherwise subject to indemnification by you, in which case you agree to cooperate with me in asserting any available defenses. This provision does not require you to indemnify me for my own fraud, gross negligence or willful misconduct. This Section survives termination of your account, the Agreement and your access to the Services.
15. Term and Termination
15.1 Term
The Agreement starts on the earlier of the date you first use the Services or the date you accept it, and remains in force while you use the Services, unless terminated earlier in accordance with the Agreement.
15.2 Termination or suspension by me
I may suspend or terminate your access to all or part of the Services, immediately and without notice, if fees are not paid when due, if you materially breach the Agreement, if your use threatens the Services or other users, or if the law requires it. In other cases I will give you at least 30 days' notice by email before terminating a paid account. I may also stop operating the Hosted Service altogether; if so, I will give at least 60 days' notice and refund any prepaid fees for the period after shutdown. Termination for cause is at my reasonable discretion and I am not liable to you or any third party for it.
15.3 Termination by you
You may stop using the Services at any time. To close your account, run
sessionly disconnect on your machines and email
kristiyan@sessionly.dev from an admin's
address asking me to delete the org.
15.4 Effect of termination
On termination your right to use the Hosted Service ends immediately and your tokens
stop working. I will delete your org's data, including sessions, pull request reports
and tokens, within a reasonable time after termination, except what I must keep for
legal, tax or security reasons and copies in backups until they rotate. What the
sessionly program keeps on your own machines is not affected. A License
that has been paid for stays valid to the end of its period unless I terminate for your
breach. Sections that by their nature should survive, including Sections 4.2, 5, 9, 12,
13, 14, 16 and 17, survive termination.
15.5 No subsequent registration
If I terminate your account for breach, you agree not to re-register or access the Services under another name without my consent, and you are not entitled to a refund of fees for the terminated Services.
16. Dispute Resolution and Governing Law
16.1 Talk to me first
If you have a dispute with me, email kristiyan@sessionly.dev with your name, the email on your account and a description of the problem. I will do the same before starting any proceeding against you. We each agree to try in good faith to resolve the dispute informally for at least 45 days after that notice before starting a court proceeding, except where urgent relief is needed to protect intellectual property or confidential information.
16.2 Governing law
The Agreement and any dispute arising out of or relating to it or the Services are governed by the laws of the Republic of Bulgaria, without regard to its conflict-of-law rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply.
16.3 Venue
Subject to Section 16.1, the courts of Sofia, Bulgaria have exclusive jurisdiction over any dispute arising out of the Agreement or the Services, and each of us submits to their jurisdiction. Either of us may bring an eligible claim in a small-claims court where that is available. If you are a consumer in the European Union or the United Kingdom, nothing in this Section deprives you of the protection of mandatory law of your country of residence or of the right to bring proceedings there.
17. General Provisions
17.1 Electronic communications
Communications between you and me take place electronically, whether you use the Services, email me, or I email you or post notices on the Website or in the dashboard. You consent to receive communications from me in electronic form and agree that all agreements, notices, disclosures and other communications I provide electronically satisfy any legal requirement that they be in writing.
17.2 Assignment
You may not assign or transfer the Agreement or your rights under it without my prior written consent, and any attempt to do so is void. I may assign the Agreement without your consent to a company I form to operate Sessionly or to a successor that acquires the Services, provided the assignee assumes my obligations; I will notify you of any such assignment.
17.3 Force majeure
I am not liable for any delay or failure to perform resulting from causes outside my reasonable control, including acts of God, pandemics, war, terrorism, riots, embargoes, acts of civil or military authorities, fire, floods, accidents, strikes, failures of hosting, network, payment or email providers, or shortages of transportation, fuel, energy, labor or materials.
17.4 Notices
Notices to you will be sent to the email address on your account or Order; you are responsible for keeping it current, and a notice sent to the last address you provided is effective even if it is not delivered. Notices to me go to kristiyan@sessionly.dev or by post to Kristiyan Ivanov, ul. Vasil Petleshkov 31-33, apt. 17, 1510 Sofia, Bulgaria, and are effective when received.
17.5 Export and sanctions
You may not use or export the Services in violation of applicable export control or sanctions laws, and you represent that you are not located in a country or on a list that would prohibit me from providing the Services to you.
17.6 Waiver and severability
Any waiver or failure to enforce any provision of the Agreement on one occasion is not a waiver of any other provision or of that provision on another occasion. If any portion of the Agreement is held invalid or unenforceable, it will be construed to reflect the original intention as nearly as possible, and the rest remains in full force and effect.
17.7 Questions and complaints
If you have questions, complaints or claims about the Services, email kristiyan@sessionly.dev. I will do my best to address them.
17.8 Entire agreement
The Agreement, including the Privacy Policy, the Data Processing Agreement, any Order and any written Enterprise terms, is the final, complete and exclusive agreement between you and me with respect to its subject matter and supersedes all prior discussions between us about it.