Privacy policy

Tigran Avakov, a self-employed individual, Mirzo-Ulugbek 45A, 100007 Tashkent, Uzbekistan, trading as OffRentAudit, decides how the data described here is processed. Write to support@offrentaudit.com with any question about it.

• Your email address, to know your account and to send sign-in links.
• Your password, stored only as a salted hash that cannot be turned back into the password.
• The name of your company, as you enter it, and the addresses of the people you add to it.
• Invoices you send: the files you upload or forward to your company's forwarding address, the sender and the subject of each forwarded email, and what is read from the invoices: the rental company, the dates, the equipment, the rates and the amounts, each with the line of the page it was taken from. The address is one for the whole company and is shared by its members.
• Emails that reach the forwarding address. For every email that reaches the address, including one we turn away, we keep a record: the sender addresses, the subject, the time it arrived, the size of the email, a fingerprint of its Message-ID, the results of the sender checks, and how it ended, with the reason. An email over the hourly or daily limit of the address, or over the size limit, is turned away without a record. We also keep the list of senders your company has allowed, until the company is erased. We accept an email only from a sender your company has allowed, and only when the platform's sender checks (SPF or DMARC) of that sender's domain pass. Any other email is turned away and its body is not read. If the email is Gmail's confirmation of forwarding, we read its text to take out the confirmation link, and we show that link to your company's members for seven days; the link stays in the record described above.
• Your contract terms and your answers: the terms you enter or confirm for each rental company, the answers you give to our questions, and the documents you attach as the source of a term.
• The name that signs a letter. You type it in your account when a credit request is prepared, and it is kept in the text of the request.
• Your off-rent log: the date, the confirmation number, who the notice went to, and the copy of what you sent, which you attach.
• Findings and credit requests we prepare from the invoices, and the outcomes you record when the rental company answers.
• Technical records needed to run the service: the time of a request, the address it came from while limiting abuse of the sign-in form, and the state of your plan.

We process this data to perform the contract you entered into when you signed up: without your address there is no way to sign you in, and without the invoices there is nothing to check. Technical records rest on our legitimate interest in keeping the service secure and working.

• Invoice files, the files of proof you attach, what is read from them, your terms and answers, your off-rent log, findings and credit requests stay until you close the account. We remove no invoice file and no file of proof on a timer: a file is the evidence behind a credit request.
• The mail journal, the line that says who wrote and about what, is removed after 13 months.
• A forwarded email or an archive that could not be taken apart is removed after 7 days.
• On request. The person who created the company can also ask us by email to close the account: we check that the message comes from that person, and then erase the data in the same order as when you close the account yourself. The erasing is real deletion, not a hidden flag.
• When you close the account, everything above that the company kept is erased, usually within an hour, at the latest within a day. What stays is an empty row of the company, with no name, and the record that the account was closed, as the proof that the erasing happened. The record of the closing holds: when it was asked and when each step was done (the cancel, the export made ready, the emails, the erasing); how many rows of each kind and how many files there were, as numbers; the billing period of the subscription that was cancelled, month or year, and whether we could confirm that the closing cancelled it; how many times a cancel at Paddle failed, and when the closing was marked as waiting for a person; a hash of the id of any subscription that turned up after the closing was asked, which only tells that its notice went; and a log of the steps that failed, each with its time, the step (the cancel at Paddle or one of the closing emails) and what went wrong, in words of ours. The id of a cancelled subscription is kept only until the notice that lets us check its refund has been sent to us. The record holds no email address, no company name and no key: the address and the name it was made with are blanked when the erasing ends. A request to close the account by email leaves a record of its own: when it came, the date and Message-ID of the email in our mailbox, how many times we tried, and how it ended, in words of ours. It holds no text of the email, and the address it came from is erased with the rest of the company.
• Billing records are held by our payment provider for as long as tax law requires, which is outside our control.

• Cloudflare runs the application, the database, the object storage that holds your files, and the outgoing email.
• Paddle is the merchant of record and handles payment, tax and receipts. We never see your card details.
• A language-model service receives the text of the pages of an invoice, so that its items can be read: Claude Haiku (claude-haiku-5-5), a language model of Anthropic. We use it under Anthropic's Commercial Terms of Service, which cover how it handles the data. Its Data Processing Addendum is part of those terms by reference. Anthropic does not train its models on your files. Each value that comes back must be found in the text of the page, or it is not used.

That is the entire list. We do not sell data and do not share it with advertisers.

One cookie of ours, set after you sign in, which keeps you signed in. The checkout frame of Paddle, on the payment pages, sets cookies of its own. There is no analytics tracker and no advertising pixel on this site, and no third party script on any page except the payment pages (/billing and /pay), which load the checkout script of Paddle. That is why you were never asked to dismiss a consent banner on our own pages.

We serve Geist and Geist Mono from our own domain. Loading these fonts does not contact a third-party font service.

You can take your data away yourself, on the Export and close page of your account. Your data comes as JSON and CSV, and the files you sent come as ZIP archives. The export does not give the sessions and sign-in links, which are keys to the account, the delivery log of payments, or mail that has not been read yet and archives you sent. You can also ask us, and we will correct anything wrong in it.

The owner of the company can close the account on the same page: that erases the data, as set out above. Closing is not the same as cancelling the subscription, which only stops the next renewal.

We answer within 30 days and usually within one business day. If you are in the UK, the EU or another region with a data protection authority, you may complain to it, though we would rather you told us first and gave us the chance to fix the problem.

The application runs on Cloudflare infrastructure distributed across regions, so data may be processed outside your country. Cloudflare and Paddle both operate standard contractual clauses for international transfers. Anthropic's Data Processing Addendum, which is part of its Commercial Terms of Service by reference, includes the standard contractual clauses of the EU and the addendum of the UK for international transfers. The text of an invoice that we send for reading is processed by the language-model provider named above, on its own infrastructure.