Privacy policy

1. Who runs EntryHut

EntryHut is built and operated by Hyunwoo Oh. For anything in this policy, including a request to see or delete your data, write to gamgabat@gmail.com. That address is read by a person, not a ticketing system.

EntryHut is a small, new service run by one person. This policy describes what it actually does today rather than what a larger company would typically promise.

2. Minimum age

You must be at least 13 years old to use EntryHut. Accounts belonging to children under 13 are not permitted. If we learn that an account belongs to someone under 13, we close it and delete its data.

If you are between 13 and 16 and in the European Union or the United Kingdom, we rely on your parent, guardian or school having agreed to your use of EntryHut. We do not collect proof of that consent, and we do not verify anyone's age. If you are a parent, guardian or teacher and want an account closed, write to the address in section 1 and we will close it.

3. What we collect, and it depends who you are

Three people can be represented in EntryHut's database, and they give up different amounts. Being specific about this is the point of the section.

A team leader, who created a project. Everything in the next section, plus the project's name and description, the email addresses they type in when inviting people, and a record of every action they take in the project.

A teammate, who was invited and signed in. Everything in the next section, plus the files they upload, the links they add, the comments they write, and a record of every action they take in the project.

Someone who was invited and has never signed in. Only their email address, which their team leader typed. See section 5.

4. What comes from your Google account

Signing in to EntryHut uses Google. It is the only way to sign in. When you do, Google gives us, and we store in our database:

• Your name as it appears on your Google account. It is shown to the other members of any project you join, next to the files you upload and the comments you write.
• Your email address. This is what grants you access: a project opens for you because your address is on its member list. Your team leader can see it in the project's member list.
• A link to your Google profile photo. We store the web address of the picture, not the picture itself. Your browser loads it directly from Google when it is shown beside your name. We ask your browser not to tell Google which page it was shown on.
• Sign-in tokens issued by Google. These are what let the sign-in work. They are stored in our database, which is hosted by Supabase. We do not add an encryption layer of our own on top of the hosting provider's. We do not use these tokens to read anything from your Google account: EntryHut asks Google only for the three items above, and has no access to your Gmail, your Drive, your Calendar or your contacts.

Your display name inside a project is copied from your Google name the first time you open that project. Changing your name at Google afterwards does not change what is already shown in projects you have joined.

5. Email addresses of people who have not signed up

EntryHut works by invitation. A team leader types the email addresses of the people they want to work with, and we store each address so that when someone signs in with it, the project opens for them. The address is the permission. Nothing else grants access, which is why the address has to be stored before that person arrives.

We hold that address on the basis of legitimate interest: someone who knows you has asked to collaborate with you, and an address is the minimum needed to make that possible. We do not use it for marketing, we do not sell it, we do not add it to any list, and we send exactly one message to it, telling you that you have been invited and by whom.

If you do not want your address held, write to gamgabat@gmail.com and we will remove it. You do not need an account to ask, and you do not need to explain why. See section 9 for what removal does and does not reach.

6. Your files, and everywhere they go

Files you upload are stored by Cloudflare R2, an object storage service. They are not kept on EntryHut's own servers. Because our providers operate internationally, your files and the rest of your data may be stored and processed outside the country where you live.

Your browser uploads and downloads files directly to and from storage, using a temporary signed web address that we generate for that one action. An upload address stops working after 15 minutes. A download or preview address stops working after 5 minutes. Anyone holding one of those addresses within that window can reach that one file, which is why they are short lived and are never included in a page that gets cached.

A version can also be a link you paste rather than a file you upload. We store the web address as text. We never open it, and whoever controls the document at the other end controls who can see it, not us.

7. Who can see a project

Only the email addresses invited to a project can open it. That is checked against the member list on every single request, not once when you sign in, so removing someone takes effect immediately rather than the next time they log in.

Projects are not public and cannot be reached by a link alone. We ask search engines not to index any project, dashboard or sign-in page, both in robots.txt and in a header sent with every one of those pages. This privacy policy, the terms of service and the front page are the only pages meant to be found by search.

8. The activity log

It records events such as a project being created or renamed, a file being created, uploaded, renamed, downloaded, given a deadline or deleted, a comment being added, and a member being invited, joining or being removed. Each entry records which member did it and when.

Two of those entries contain an email address in full: the one written when someone is invited, and the one written when someone is removed. This means that removing a person from a project does not by itself erase their address from EntryHut. Deleting it requires deleting those log entries by hand, which we will do if you ask us to under section 9.

9. How long we keep things, and what deleting actually does

We keep your data for as long as your account exists. We do not currently run any automatic clean-up: an account that is abandoned and never used again is not deleted on a schedule, and neither are its projects or files. If that changes, this page will say so before it happens.

Some things in the product are called deleting but do less than the word suggests, and you should know which:

• Deleting a file hides it from the project and stops anyone opening it. The stored file itself stays in our storage provider, and it still counts against the project's storage limit.
• Deleting a project archives it. It disappears from your dashboard and stops counting toward your project limit. Its files, versions, comments and activity log all remain, and none of the stored files are removed from storage.
• Removing a member revokes their access immediately and permanently. Their record of membership is kept, along with their address in the activity log, as described in section 8.
• Deleting a comment hides it. The text remains in the database.

There is no button anywhere in EntryHut that deletes your account or erases your data. Real deletion is done by hand, by the person named in section 1, when you ask for it. We will act on a deletion request within 30 days of receiving it, and that means removing the underlying records and stored files, not simply hiding them.

10. Who else receives your data

EntryHut is built on other companies' services. Each of these receives some of your data in order to do its job. We do not sell your data to anyone, and none of these receive it for their own advertising.

• Google, for sign-in. Google knows you signed in to EntryHut, and gives us the information in section 4.
• Supabase, which hosts our database. It holds everything described in this policy except the file contents themselves.
• Cloudflare R2, which stores your uploaded files.
• Vercel, which runs the website. Our application servers run in the United States. All traffic between you and EntryHut passes through Vercel.
• Resend, which sends the invitation emails. It receives the recipient's address, the project name, and the name of the person who invited them.
• Microsoft, which receives Word, Excel and PowerPoint files in order to display them. See section 6.
• PostHog, our product analytics, described in section 11. Its servers are in the United States.
• Google Analytics and Vercel Analytics, on the front page only, described in section 11.

11. Analytics, and what we deliberately do not collect

We measure how the product is used so we can tell which parts work. The tools differ depending on which page you are on, and that split is deliberate.

Inside the product (your dashboard, your projects), the only analytics tool is PostHog. It records a fixed list of actions, each one written deliberately into the code: opening a project, creating a project, inviting a member, removing a member, uploading a file, adding a link, opening the share panel, opening project settings, signing in, and reaching the free project limit. Each carries the identifier of the project it happened in, and nothing else. It also records the address of the page you are on, which for a project is its identifier and not its name.

It does not record your name, your email address, file names, the text of comments, or the contents of anything you upload. PostHog offers a feature that automatically records what you click, including the text on screen, and we have turned it off. Session recording, which would replay what you did on screen, is turned off as well.

Location tracking is switched off for every one of those events, explicitly, on every request. The reason for all of this is that the people using a project board are often students at school, and often minors, who never chose to be measured.

On the front page only, we also use Google Analytics and Vercel Analytics to see how many people find the site. Both of these work out an approximate location, such as a city or country, from your IP address, and neither offers a way to turn that off. That is exactly why they run on the front page and nowhere else: a visitor there arrived by choice, and someone opening a project board did not.

12. Cookies and browser storage

• A sign-in cookie, which keeps you signed in. It lasts 30 days. Without it you would have to sign in again on every page.
• Two short-lived cookies used during the sign-in process itself, which protect the form and remember where to send you afterwards.
• A PostHog cookie, which gives your browser an anonymous identifier so repeated actions are not counted as separate people. It lasts one year.
• Google Analytics cookies, on the front page only. They last up to two years.
• One entry in your browser's session storage, which records that we have already counted this sign-in. It is discarded when you close the tab.

Vercel Analytics does not use cookies.

13. Your rights

You can ask us for a copy of the data we hold about you, ask us to correct it, or ask us to delete it. Write to gamgabat@gmail.com. We will respond and act within 30 days.

This applies whether or not you have an account. If your address was invited to a project and you never signed in, you still have every right listed here, and section 5 explains how it came to be here in the first place. Tell us the address and we will find and remove it.

One limit worth stating rather than discovering: files, comments and activity in a shared project are not only about you. If you ask us to delete your data from a project you shared with other people, we will remove your account, your identifying information and the files you uploaded. We may keep the project itself intact for the other members, with your contributions attributed to a removed member.

Depending on where you live, you may also have the right to complain to a data protection authority.

14. Security

Traffic between your browser and EntryHut is encrypted in transit, as is traffic to our storage provider. Access to every project is checked against the member list on every request. Beyond that, EntryHut relies on the security of the providers listed in section 10 rather than on protections of its own, and we are not in a position to promise more than that. No service can guarantee it will never be breached, and we are not going to be the first to claim otherwise.

15. Changes to this policy

If we change this policy we will update the date at the top of the page. If a change materially affects what we collect or who receives it, we will email the address on your account before it takes effect.

Our Terms of Service cover the rules for using EntryHut itself.