What we collect

When you join the early-access list, the form asks for one required value, your email address, and three optional ones: your role, your biggest reporting pain, and how you heard about us. You can leave all three blank. The form has no name field and no company field, so the early-access list holds neither.

Other values are recorded without you typing them. Our server records the IP address the request arrived from, your browser’s user agent string, and the time you submitted. Your browser reports the page that referred you and, if you followed a campaign link, the tracking tags it carries in the address (utm_source, utm_medium and utm_campaign).

The IP address does a second job worth naming: no more than five signups an hour are stored from any one address, which is how we keep bulk automated submissions out of the list.

All of this is stored in our database, hosted on Supabase.

The interactive demo and the tie-out on this site run on fixed sample data in your browser. There is nothing to upload and no save feature, so none of the numbers you touch there reach us. The page itself is counted like any other, through the analytics described under Cookies.

If you have a ClosePack account, we also hold the email address you sign in with, the display name on your profile, which workspace you land in by default, your display preferences for the app, and when your account was created and last changed. We hold your membership of a workspace and the role you hold in it, which is how we know what you are allowed to open.

We hold the financial information you put into ClosePack as well: your chart of accounts, your transactions, and the statements, views and packs you build from them. That information is yours. We use it to run ClosePack for you and to keep your work available the next time you sign in. We do not sell it, and we do not use it to train machine-learning models. The product saves your work to your account as you go, and tells you on screen when a save has not gone through.

ClosePack also keeps a record of what happens in a workspace: who did it, what they did, and when, and for some actions the values before and after the change. That record is append-only, which means it is a history you can rely on rather than one anyone can quietly edit.

Cookies

This site uses one functional cookie to remember whether you prefer the light or dark theme. Signed in to the product, your browser also carries the session cookies that keep you signed in. Neither is used for advertising or cross-site tracking. We count page views with Google Analytics only if you accept it on the bar at the foot of the page; if you do, it sets its own cookies, and if you do not, nothing on this site is sent to it. Your choice is kept in a second functional cookie for a year, and a control at the foot of every page changes it. The home page also embeds a video that loads nothing until you press play; the section below and our Cookie Policy explain what happens when you do.

How we use your information

We use your contact details to respond to your interest and to send occasional updates about ClosePack. We use the optional answers and the campaign tags to understand who is asking and where they found us. If you have an account, we use what is in your workspace to run the product for you and nothing else: to show you your own numbers, to keep your work available between sessions, and to help you if you ask us to look at something. We do not sell or rent your personal information.

Who we share it with

We share it only with the providers that run ClosePack for us, each under its own privacy terms:

Supabase hosts our database and our sign-in, so it holds the early-access list and everything in your workspace.
Vercel hosts this site and the product. Every request passes through it, so it handles your IP address and user agent in its server logs.
Google Analytics measures traffic to the marketing site, and only after you accept it on the bar at the foot of the page, so it sees the page you are on, ordinary interactions with it such as scrolling and clicking away, roughly where you arrived from, and your IP address and user agent as part of the request. If you accept, it sets its own cookies so that a return visit is counted as one; we run it with Google’s advertising features switched off. It is not used in the signed-in product.
Sentry receives error and performance data so we can find and fix failures. It sees the page you were on, your browser and device type, and the technical detail of anything that broke. We do not enable session replay, so it does not record your screen.
Resend sends us one email when you join the early-access list, so it sees the address you typed, the answers you gave, and the campaign tags and referring page your browser reported, and nothing from a workspace.

We do not use a marketing email platform today, so nothing is passed to one; Resend, above, sends us one notification when you join the list and sends you nothing. If we add a marketing platform, we will name it here. Mail you send to hello@closepack.io reaches us through our domain provider’s email forwarding.

Google appears twice above and below, in two different roles, and the difference matters. As a provider it counts page views for us, listed with the others; that happens only after you accept analytics on the bar at the foot of the page, and then it sets its own cookies. Separately, the teaser on our home page is hosted on YouTube and embedded through Google’s youtube-nocookie.com, and nothing is requested from it until you press play. When you do, your browser connects to Google directly and Google sees your IP address, your user agent, and the fact that you arrived from this site, under its own terms, and it may set its own cookies, separately from any analytics cookies you accepted. None of the information you give us is passed along with either. Our Cookie Policy has the detail.

How long we keep it

What you put into ClosePack stays there for as long as your workspace exists. We do not delete anything in a workspace on a schedule, and nothing ages out on its own: your chart of accounts, your transactions, the statements, views and packs you build, any documents you attach, and the activity record all stay until the book or workspace they belong to is deleted. Removing a single item inside the product does not always erase our copy of it: a view or an attached document you remove is hidden rather than erased, and our copy goes when its book or workspace is deleted.

There is no delete button for a whole book or workspace yet. To remove one, email us from the address you sign in with. We delete it by hand within 30 days of your request and tell you when it is done. Before we do, you can ask us for a copy of your chart of accounts and your transactions as a spreadsheet, and we will send it within the same 30 days, before anything is deleted. If you delete a book and keep your workspace, the record of what happened in that book stays in your workspace’s history with the link to the book removed, including the before-and-after values it recorded for some actions, because that record is append-only. If you delete the whole workspace, the record goes with it, and so does your login if you ask for that too. Documents you attached and the thumbnail images of your views are removed in the same job.

Deleting something does not remove it from our backups straight away. We keep daily backups of the database for 7 days and a weekly encrypted copy for 28 days, and both age out on their own, so a deleted row can survive in a backup for up to 28 days after it was deleted. Backups exist to bring the whole service back after a failure, not to bring back something you removed. If we ever have to restore one, we carry out again any deletion you asked for after it was taken.

Records our servers make on their own are short-lived. Request logs, which carry your IP address and the page you asked for, are kept for 7 days by our database host and for one day by our web host. Error reports are kept for no more than 90 days. If you accepted analytics on this site, Google Analytics keeps the page-view data for no more than 14 months; your consent choice itself is kept in a cookie for a year, and the Cookie Policy covers the rest.

The early-access list is different, because you gave it to us so you would hear from us. We keep your entry until you ask us to remove you, and the notification we receive when you sign up stays in our mailbox until then. Email us and both go. The provider that delivered that notification keeps its own record of it under its own terms, like any provider on the list above.

Your choices

You can ask us to access, correct, or delete the information we hold about you, or to stop contacting you, at any time. Email us and we will take care of it. How long we keep it, above, says what a deletion covers, how long we take, and how long a copy can remain in a backup.

Contact

Questions about privacy? Reach us at hello@closepack.io.

Privacy Policy