The rules, in plain words.

Last updated: 4 October 2026

These terms are an agreement between {legal entity name} ("devreport", "we", "us") and you, the person or business using devreport. By creating an account or using the service you accept them. If you use devreport for a business, you accept them on its behalf.

1. The service

devreport turns files you give it (uploads such as CSVs, notes, logs, images and zips, or a link to a public git repository) into a typeset PDF deck or report with its LaTeX source. Charts are drawn from your data; the text is written by third-party AI models.

2. Your account

You sign in with a link we email you; there is no password. Keep access to that email address secure, because anyone who can read it can sign in as you. You must be at least 16 years old. You are responsible for activity in your account and in any team workspace you own.

3. Your content

You keep all rights to the files you upload and to the documents devreport makes for you. You can use them for any lawful purpose.
You give us permission to store and process your files only as needed to run the service for you, including sending them to the AI model providers listed in the Privacy Policy.
You confirm you have the right to use every file and repository you give us, and that doing so doesn't break any law or agreement you are bound by.
Don't upload sensitive personal data (health, financial or government ID data, or other people's personal data beyond what is incidental) unless you are allowed to and it is necessary.

4. AI output

Documents are written with the help of AI models and can contain mistakes. Check every document before you rely on it or send it to anyone. Nothing devreport produces is legal, financial, tax or other professional advice.

5. Share links

A share link lets anyone who has it view the PDF, without signing in. Treat it like the document itself. Commenting needs a sign-in, and the part of a commenter's email before the @ is shown next to their comment. You can revoke a link at any time and it stops working at once.

6. Credits and payment

Builds are paid for with prepaid credits. New accounts get 5 free credits once per person. Current costs are shown on the pricing section and in the app.
Credit packs are one-time purchases (no subscription): 20 credits for $9, 60 for $24 and 200 for $69 (USD; applicable taxes may be added). Prices may change, but never for credits you have already bought.
devreport sells the credit packs. Payments are processed by Razorpay, our payment gateway, which handles your card, UPI and other payment details. We issue invoices and handle any applicable taxes.
Credits belong to a workspace. In a team workspace all members build from one balance. Credits don't expire while the service runs, have no cash value, and can't be transferred or resold.
A build that fails before it produces a PDF gives its credit back automatically. Refunds of purchases are covered by the Refund Policy.

7. Referrals

You can share your referral link. When someone signs up through it and their first build succeeds, both of you get 5 credits, up to 50 referral credits per referrer per month. Self-referrals and duplicate accounts don't count, and we may remove credits obtained by abusing the programme.

8. Acceptable use

Don't use devreport to process material you have no right to use, to make unlawful, infringing or harmful content, to probe or break its security or sandboxes, to overload it, or to resell it as a standalone service without our written agreement.

9. Suspension and termination

You can stop using devreport at any time and ask us to delete your account. We may suspend or close an account that breaks these terms or puts the service or other users at risk. If we close the service or your account without cause, we will refund unused purchased credits.

10. Disclaimer

The service is provided "as is" and "as available". To the extent the law allows, we disclaim all implied warranties, including merchantability, fitness for a particular purpose and non-infringement.

11. Limitation of liability

To the extent the law allows, we are not liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue or data, and our total liability for any claim is limited to the amount you paid us in the 12 months before it. Nothing here limits liability that can't be limited by law.

12. Changes

We may update these terms. For material changes we will email account holders at least 14 days before they take effect. Using devreport after that date means you accept the new terms.

13. Governing law

These terms are governed by the laws of {jurisdiction}, and disputes go to its courts, unless the law where you live gives you a right to bring them elsewhere.

14. Contact

{legal entity name}, {address}. Email [email protected].

What we keep, and why.

Last updated: 4 October 2026

{legal entity name} runs devreport and is responsible for the personal data described here. For the contents of files you upload, you decide what goes in, and we process them only to make your documents.

What we collect

Account: your email address, the workspaces you belong to, and who referred you, if anyone.
Your files and documents: uploads, clones of public git repositories you link (which include commit author names and emails), the answers and revision notes you give, and the PDFs and LaTeX source we produce.
Sharing and comments: share links you create, view counts, and comments (with the commenter's email).
Credits and payments: your credit ledger (grants, purchases, builds, refunds, referrals). Card and payment details go to Razorpay and never reach us.
Technical data: IP addresses for rate limiting and abuse prevention, and usage records for each build (model, token counts, duration).

How we use it

To run the service: sign you in, build and store your documents, show share links, keep balances, process purchases, prevent abuse, and send the emails described below. We do not sell your data, show ads, or use your files to train AI models.

Who processes it

AI model providers (such as Anthropic, OpenAI, Google or OpenRouter, depending on configuration) receive the parts of your files, notes and data that the model reads while writing your document.
Razorpay, our payment gateway, handles checkout, payment details and refunds to your payment method.
Our hosting and email delivery providers store the service's data and deliver its emails.
Anyone with a share link you create can view that PDF. They never see your source files or the .tex.

Some of these providers are outside your country, so your data may be transferred internationally.

Emails

We send sign-in links, team invites, and, from the 1st of each month, a reminder with a link to re-run each document due an update. Every reminder has an unsubscribe link, and you can also turn reminders off in the Library.

Cookies

We use two cookies, both strictly necessary, and no tracking or advertising cookies:

dr_sid keeps you signed in. It lasts 30 days and is removed when you sign out.
dr_ref remembers who referred you when you arrive through a referral or share link (?ref=), so both of you can get referral credits. It lasts 30 days and is only set if you aren't signed in.

Your browser's local storage also remembers your light/dark theme choice and whether you dismissed the cookie notice. This never leaves your device.

How long we keep it

We keep your account and documents until you delete them or ask us to delete your account. Deleting a document from the Library removes its files and PDFs. Payment and ledger records are kept as long as tax and accounting law requires.

Your rights

You can ask to access, export, correct or delete your personal data, or object to how we use it, by emailing [email protected]. Depending on where you live you may also complain to your data protection authority.

Security

Builds run in a sandbox limited to that document's folder, uploads and repository contents are treated as untrusted, and connections use HTTPS. If a breach affects your data, we will tell you without undue delay.

Contact

{legal entity name}, {address}. Email [email protected].

Refund Policy

Pay for what works.

Last updated: 4 October 2026

Failed builds

If a build, re-run or revision ends without producing a new PDF, its credit goes back to your balance automatically. You don't need to ask.

Unused credits

Unused purchased credits are refundable on request within 14 days of purchase. Email [email protected] from your account's address with the purchase date. If you have used some credits from a pack, we refund the unused part in proportion to the price you paid.

How refunds are paid

Refunds go back to your original payment method through Razorpay, our payment gateway. The refunded credits are removed from your balance. Free sign-up and referral credits have no cash value and are not refundable.

Chargebacks

Please email us before disputing a charge with your bank. If a dispute is decided against us, the credits from that purchase are removed.

Nothing here limits any refund rights you have under the law where you live.