Privacy Policy
Last updated: 2026-10-18
This Privacy Policy explains how Latent Software LLC, a Wyoming limited liability company, 30 N Gould St, Ste N, Sheridan, WY 82801, United States ("we," "us" or "our"), handles personal information in AccountingYear, including the website at accountingyear.com, the approval pages at issuer.accountingyear.com, and the related services (together, the "Service").
By using the Service, you confirm that you have read this Privacy Policy. It is information that we owe you. It is not a request for your consent, and we do not treat your acknowledgment as consent to anything else.
1. DEFINITIONS
"Customer" means a person or an entity that uses the Service for its books, calendar and filings. A Customer works through an organization in the Service.
"Account Data" means data about a person who has an account: the name, the email address, the password hash, and the records of sign-in and use.
"Books Data" means the data that a Customer puts into the Service to keep its books and prepare its filings, as Section 2.2 lists.
"Processor" means a third party that processes data for us to provide the Service (Section 5).
2. DATA WE COLLECT
2.1 Account Data
| Data | Examples |
|---|---|
| Account details | Name, email address, password (stored only as a hash), profile picture if you add one |
| Sign-in method | If you choose to sign in with Google, the identifier and the verified email address that Google gives us |
| Sessions and devices | For each session: the time, the IP address, the user agent (browser and device type), the approximate location derived from the IP address, and whether the session is active |
| Login history | Successful and failed sign-ins, with the time, the IP address, the user agent, the sign-in method and approximate location |
| Membership | The organizations that you belong to, your role in each, and the entities that you may reach |
| Billing | Your plan and subscription status. Our payment processor, Stripe, collects your payment details. We do not store a full card number |
| Acceptance records | A record of each time that you accept or acknowledge a legal document: the document and its version, the time, who accepted, and for whom (see Section 2.5) |
| Messages | The emails that the Service sends you, their time and status, and the messages that you send to us |
2.2 Books Data
Customers put the following into the Service:
| Data | Examples |
|---|---|
| Entities and their legal facts | Legal name, registration numbers, tax identifiers, addresses, jurisdiction, fiscal year |
| Owners and parties | Names, identifiers, addresses, ownership shares, acquisition dates, and the relationship of each party to an entity |
| Evidence | Bank exports and documents that you upload (for example statements, invoices and contracts) |
| The ledger | Entries, accounts, amounts, dates, descriptions, reversals and restatements, with the reason and the person who made each change |
| Filing packages | The forms and attachments that the Service prepares, the reviews of them, and the questions and answers that came with them |
| Signatures | Drawn or typed signature images and typed names that you add to a package |
| Approvals and receipts | Each approval, with a digest of the exact content approved, the person, the session and the time; delivery receipts and delivery evidence |
| Calendar and metrics | Your deadlines, the runs of the calendar, and the figures that the Service derives for each entity |
| Agent run logs | The tasks given to the agent, the tools that it used, and its explanations and outcomes |
Books Data often contains personal data about people other than the Customer's user: for example owners, directors, signers and counterparties. The Customer is responsible for having the right to give us that data (see Section 6).
2.3 Data collected automatically
We collect:
- Log data: IP address, browser type, device type, referring page, pages requested and time stamps;
- Authentication security data: sign-in events, session lifecycle and revocation, and approximate location from the IP address;
- Cookies (see Section 8).
We do not use third-party advertising trackers. We do not run third-party analytics scripts in the Service.
2.4 Data from other sources
If you sign in with Google, we receive from Google the data that you allow it to share, which is normally your name, your email address and your profile picture. If another member of your organization invites you, we receive your email address from that member.
2.5 Acceptance records
When you accept the Terms or the Accounting Terms, or acknowledge this Privacy Policy, we record the document and its exact version, the time, who accepted and for which organization. We also record technical details of the request, such as the IP address, the browser and an approximate location. We use the record to prove what was offered and accepted. Deleting your account does not delete this record. We keep it for as long as a claim about the agreement could arise, and we have set no fixed deletion date.
3. HOW WE USE DATA, AND OUR LEGAL BASES
| Purpose | Legal basis (where GDPR or a similar law applies) |
|---|---|
| Create and run your account, sign you in, keep your sessions secure | Contract |
| Keep the books, run the calendar, prepare, review, approve and record filing packages | Contract |
| Send service emails: invitations, approval requests, questions, reminders, receipts and security notices | Contract; our legitimate interest in running the Service |
| Process payments and manage plans | Contract; legal obligation |
| Protect the Service and its users: detect abuse, fraud and unauthorized access, keep audit logs | Legitimate interest; legal obligation |
| Keep the records of the books and legal evidence for seven years | Legal obligation; our and your legitimate interest in intact records |
| Prove agreements, handle disputes and legal claims | Legitimate interest; legal obligation |
| Support you and improve the Service | Contract; legitimate interest |
What we do not do. We do not sell personal information. We do not share it for advertising. We do not use Books Data to build advertising profiles. We do not train models on Books Data, and we have not authorized any Processor to do so (see Section 5.2 for the model provider).
Automated processing. The Service uses an agent and an automated review (Section 5.2). They prepare and check work. They do not decide anything that has a legal effect on a person: nothing posts, files, signs or sends without the approval of a person, and the agent never approves. You can ask us for a human to look at any automated result at [email protected].
4. WHO SEES BOOKS DATA IN THE SERVICE
People reach only the entities that they are granted. The organization's owners and admins decide who has access and at what level. Every access to the books is logged.
We (the staff of Latent Software LLC) do not read the content of Books Data, except to support you at your request, to keep the Service secure, to investigate abuse, to fix a fault, or to meet a legal duty. Only a few of our people have access to systems that hold Books Data.
5. HOW WE SHARE DATA
5.1 Processors
We use these Processors to operate the Service. Each processes data under a written agreement that limits its use of the data to providing its service to us.
| Processor | Purpose | Data | Location |
|---|---|---|---|
| Hetzner (Hetzner Online GmbH and its US subsidiary) | Servers that run the Service and its database | All data in the Service | Ashburn, Virginia, USA |
| Amazon Web Services (Amazon Web Services, Inc.) | The books' document store (Amazon S3, with a retention lock), and email sending (Amazon SES) | The documents, evidence, signed records, receipts and filing packages of the books; the emails that the Service sends | us-east-1 (N. Virginia), USA |
| Backblaze (Backblaze, Inc.) | Encrypted off-site backups of the database, kept for 30 days | A copy of the database | USA |
| Cloudflare (Cloudflare, Inc.) | DNS, proxy and protection against attacks for our domains; object storage for profile pictures; a bot check at sign-up, if enabled | Web traffic to the Service (it passes through Cloudflare); profile pictures | USA and its global edge network |
| Stripe (Stripe, Inc., and its affiliates) | Payments and subscriptions | Your name, email, plan and payment details | USA and other countries where Stripe operates |
| Anthropic (Anthropic PBC) | The language model for the agent and the automated review of filings | Books Data of the period that the task covers (for example entries, entity facts and the text of documents), sent to prepare and review the work | USA |
| Phaxio | Sending a filing by fax, only when a filing is faxed and only when the fax provider is enabled | The pages of the filing package and the destination fax number | USA |
| Google (Google LLC) | Optional "Continue with Google" sign-in only | Your sign-in identity (name, email address, picture) | USA and other countries where Google operates |
We may add or change a Processor. We will update this Privacy Policy before a new Processor receives Books Data, and we will tell you of a material change by email or in the Service.
5.2 About the model provider
The agent and the automated review send Books Data to Anthropic through its commercial API. We send only what a task needs. Anthropic's commercial terms say that Anthropic does not train its models on API inputs and outputs by default, and we have not agreed otherwise. The review treats text in documents as data and not as instructions, and a model can still be wrong, which is why a person approves every filing.
5.3 Your organization and the people you name
We show Books Data to the members of your organization, according to the access that you give them. If you engage a delegated signer, the signer sees the filing package that you approve for it and the evidence that it needs. When a filing is sent, the package goes to the authority or the carrier that you or the signer choose.
5.4 Legal requirements and the business
We may disclose data to comply with law or legal process, to respond to lawful requests from authorities, to protect the rights, safety or property of us or others, or to enforce our Terms. Where the law allows, and where it is practical, we will tell you before we disclose Books Data of your organization. We may transfer data in a merger, acquisition or sale of assets, and we will tell you if that happens.
5.5 Aggregated data
We may use data that is aggregated and does not identify a person or a Customer, for example the number of entity years or the speed of the Service.
6. ROLES: WHO IS RESPONSIBLE FOR WHAT
Account Data. We decide why and how it is processed. We are the controller of Account Data.
Books Data. The Customer decides why and how its Books Data is processed. We process Books Data on behalf of the Customer, on its documented instructions, which are the Terms, the Accounting Terms and the Customer's use of the Service. For Books Data we act as a processor (or "service provider"), and the Customer is the controller (or "business"), or a processor for its own clients if it acts for them.
When we act as a processor, we:
- process Books Data only on the Customer's instructions, unless the law requires otherwise;
- make sure that the people who handle it owe a duty of confidentiality;
- use the security measures in Section 9;
- use the Processors in Section 5.1, under written terms with data protection duties at least as strong as ours, and stay responsible for them;
- help the Customer to answer data subject requests and to meet its security and breach notice duties, taking into account the nature of the processing;
- tell the Customer without undue delay after we become aware of a personal data breach that affects its Books Data;
- delete or return Books Data when the services end, except what Section 7 requires us to keep; and
- give the Customer the information that it needs to show that we meet these duties.
If you need a signed data processing agreement, write to [email protected].
The Customer's duties. The Customer is responsible for having a lawful basis and the right to put personal data of owners, parties and others into the Service, for giving those people the notices that the law requires, and for answering their requests. A Customer should enter only the identifiers that a filing or a record needs.
People named in Books Data. If you are an owner, a party or another person named in a Customer's books and you want to use your rights, write to the Customer. We will help the Customer to answer you, and we will refer your request to it.
7. RETENTION
| Data | How long we keep it |
|---|---|
| The books, the evidence and the filing packages (ledger, documents, signed records, receipts, approvals, packages) | Seven years. The document store holds them under a compliance-mode retention lock. Nobody can delete them earlier, even on request, because the law requires the records. |
| Account details | While the account is active. After you ask us to delete the account, we delete them, except what the books and the legal evidence must keep (such as the name and email address on an approval or on a change in the ledger). |
| Sessions | While the session is active, and then until the account is deleted. |
| Login history | 12 months, on a rolling basis. |
| Acceptance records | As long as a claim about the agreement could arise (Section 2.5). |
| Billing records | As long as the law requires us to keep them, normally seven years. |
| Emails sent and support messages | As long as needed to support you and to prove what we sent, unless they form part of the books' evidence. |
| Database backups | 30 days. A backup is not edited. It is replaced as it ages out. |
| Server logs (IP addresses and requests) | In a size-capped log on the host. Older lines are overwritten as the log fills. |
| Agent run logs | As long as the books that they relate to. |
Deletion on request. If you ask us to delete your account data, we will do it, within one month where the law sets that time, except for the records that Section 7 says we must keep. Those records stay locked until the retention ends. After the retention ends, we delete them within a reasonable time, unless a law, a legal hold or an open dispute requires us to keep them longer.
Ledger changes. The ledger is insert-only. An entry is never edited or deleted. A change is a reversal or a restatement that stays on record. For this reason, we cannot correct or remove a person's name from a closed record of the books. Where a law gives you a right to correct data, we will add a correction to the record instead.
8. COOKIES
We use only the cookies that the Service needs.
| Cookie | Purpose | Duration |
|---|---|---|
| Session cookie | Keeps you signed in and protects each request | Until you sign out or the session expires |
Device cookie (sessions_device_id) |
A signed, random value, set after you sign in, that recognizes a browser so that repeated sign-ins do not look like new devices, and shows the sign-in method last used. It contains no account identifier and no credential. It is not a fingerprint | Up to five years, unless you delete it |
We do not use advertising cookies. We do not use third-party analytics cookies. We do not respond to "Do Not Track" signals, because we do not track you across other sites. Your browser lets you block or delete cookies. If you do, you cannot sign in.
9. SECURITY
We use measures that suit the risk, including:
- encryption in transit (TLS), and encryption at rest of the document store;
- passwords stored only as hashes;
- separate access for each part of the Service: the approval pages run apart from the rest, and each part holds only the credentials it needs;
- re-authentication on the issuer's confirmation page before an approval;
- an insert-only ledger with hash-chained and signed records, and a retention lock on the document store;
- access limited by role and by entity, with every access logged; and
- an off-site database backup.
No system is perfectly secure. You must keep your password and your devices secure. If a breach affects your personal data, we will notify you and the authorities as the law requires.
10. INTERNATIONAL TRANSFERS
We are based in the United States, and our servers and most Processors are in the United States. If you use the Service from outside the United States, your data is transferred to and processed in the United States and in other countries where our Processors operate. Those countries may have different data protection laws than yours.
For transfers from the European Economic Area, the United Kingdom or Switzerland, we rely on the transfer safeguards of the Processors (such as the EU Standard Contractual Clauses and their UK and Swiss addenda, or participation in the EU-US Data Privacy Framework, where the Processor is certified), and on other lawful mechanisms. You can ask us for details at [email protected].
11. YOUR RIGHTS
Depending on where you live, you may have the right to:
- access the personal data that we hold about you;
- correct data that is wrong;
- delete your data (subject to Section 7);
- receive your data in a portable format;
- restrict or object to some processing;
- withdraw consent, where we process on the basis of consent; and
- complain to your data protection authority.
To use a right, write to [email protected]. We may need to confirm your identity first. We will answer within the time that the law sets. You can delete some data in the Service yourself. You can export your records in the Service while your account is active.
If your request concerns Books Data of a Customer, we may refer it to the Customer (Section 6).
We do not discriminate against a person for using a privacy right.
12. REGION-SPECIFIC INFORMATION
12.1 California (CCPA/CPRA)
- Categories collected (in the last 12 months): identifiers; commercial information (plan and billing); internet and network activity (logs, sessions); approximate geolocation; professional information; signature images; and the contents of the documents that you upload.
- Sources: you, your organization, and Google if you use it to sign in.
- Purposes: as in Section 3.
- Disclosure: to the Processors in Section 5.1 for business purposes.
- Sale or sharing: we do not sell personal information, and we do not share it for cross-context behavioral advertising.
- Rights: to know, delete, correct, and limit the use of sensitive information. To use them, see Section 11.
12.2 European Economic Area, United Kingdom and Switzerland
- Controller: Latent Software LLC for Account Data. A Customer is the controller of its Books Data, and we are its processor (Section 6).
- Legal bases: Section 3.
- Rights: Section 11.
- Transfers: Section 10.
12.3 Other places
We try to meet the privacy laws that apply to us. If you have a question about your location, write to [email protected].
13. CHILDREN
The Service is for businesses and is not for anyone under 18. We do not knowingly collect personal data from children. If we learn that we hold it, we will delete it, except what the law requires us to keep.
14. LINKS TO OTHER SITES
The Service may link to the sites of authorities and other third parties. We are not responsible for their privacy practices. Read their policies.
15. CHANGES TO THIS POLICY
We may update this Privacy Policy. For a material change, we will give notice by email or in the Service before the change takes effect, and we will ask you to acknowledge the new version. The date at the top shows when we last changed it.
16. CONTACT
Latent Software LLC 30 N Gould St, Ste N Sheridan, WY 82801 United States
Privacy questions and requests: [email protected] General support: [email protected] Legal notices: [email protected]
Last updated: October 18, 2026