Privacy Policy

1. Who we are

Clockitlive is a service of Kooemma Digital Holdings LLC, a limited liability company based in Arizona, United States. In this policy, "we", "us" and "our" mean Kooemma Digital Holdings LLC, which is the company responsible for the information described here.

For anything on this page, write to support@clockitlive.com.

The service is operated from the United States. If you use it from elsewhere, you are sending your information to the United States, where privacy law differs from the law where you live.

2. Three kinds of people use this

Organizers hold an account. They set an event up, run the desk during it and keep the album afterwards.

Guests do not hold an account and are never asked for one. A guest scans a code, gives a name to be known by, and posts. That name is the only thing we ask a guest for. We do not ask a guest for an email address or a phone number, and we have no way to contact a guest outside the event.

People in a watch party hold no account either. Somebody recording sends them a link, they give a name and ask to come in, and if they are let in their camera and microphone go into that person's recording. It is the shortest relationship of the three and the most personal, which is why it gets its own section below.

3. Information we collect

From an organizer, on creating an account:

• Name and email address.
• A password, which is never stored. What is stored is a scrypt hash, from which the password cannot be recovered.
• If they use Continue with Google instead: the email address, name and account identifier in the token Google issues. We never receive their Google password, and we ask Google for nothing beyond those three things.
• The date these terms were accepted, and the date the email address was proven.

From an organizer, running an event: its title, venue, dates, time zone and settings, and any cover image uploaded.

From a guest, on joining:

• The display name they choose.
• The photographs and videos they post, at the size their phone recorded them, with the dimensions and the time posted.
• Which moments they liked and which they have seen, so a count can be shown and so their own likes come back to them next visit.

Location. Where a moment was taken is shown beside it only if the organizer of that event turns it on, and it is off unless they do. A guest's whereabouts is theirs to give.

Automatically. Ordinary server logs, including IP address, browser and device type, and the pages requested. We use them to keep the service up and to work out why something broke.

In the categories California law uses, that is: identifiers, internet activity, approximate location, audio and visual information, and, for organizers, commercial information. We do not collect Social Security numbers, financial account numbers, precise geolocation from a device, health information, or information about race, religion, sexual orientation or union membership. We do not ask for any of it, and there is nowhere in the product to enter it.

4. How we use it

• To run the service. Opening an event, showing the feed and the wall, and compiling the album afterwards.
• To keep accounts secure. Proving an email address, hashing passwords, spotting abuse.
• To publish an event where an organizer has asked us to. See section 7.
• To answer you when you write to us.
• To meet legal obligations and to enforce our Terms of Use.

5. We do not sell or share your information

We do not sell personal information, and we do not share it for cross-context behavioral advertising, as those terms are defined by California law. We have not done so in the preceding twelve months, including for anyone under sixteen.

We do not use what you post to advertise, we do not build advertising profiles, and we do not train machine learning models on the photographs and videos shared inside events.

6. No face recognition, no biometric identifiers

This product is full of photographs of people and does nothing to identify anyone in them. We do not run face detection or face recognition. We do not generate faceprints, face templates, face geometry or any other biometric identifier, and we do not collect biometric information as Illinois, Texas and Washington define it.

Photographs are resized so a phone and a projector can both show them. Nothing analyses who is in them. Moments are attributed to the guest who posted them, by the name that guest chose, and by nothing else.

7. Who can see a moment

A moment posted at an event is visible to the people in that event: on guests' phones, on the venue screen, and at the organizer's desk. The organizer can take anything down from that desk, and can freeze every screen at once.

The invite link is a credential. Anyone holding the link or the printed code can join the event and see what has been posted to it. The link carries a random tail so it cannot be guessed, but it cannot tell one holder from another. Treat it the way you would treat a key.

An album's reach is the organizer's to set: either the guests who joined, or anyone holding its link.

Events listed publicly. An event is private unless its organizer lists it, and listing is off by default. A listed event appears on our public events page showing its title, venue, date and the name of the organizer who opened it. The printed join code is never published there. Turning the setting off removes it.

8. Watch parties

Somebody with an account can open a watch party and send the link round. Whoever opens the link asks to come in, and if they are let in their camera and microphone go into the recording being made, alongside anything being shared on screen. Up to six faces fit in the picture.

What we collect from somebody who joins one: the name they type, and for as long as they are in the room, the fact that they are. Nothing else. We do not ask for an email address or a phone number, and we have no way to reach them afterwards.

Where the picture and the sound actually go. They go straight from one browser to the other. Video and audio in a watch party do not pass through our servers and we never hold a copy: what our servers carry is the handful of messages two browsers use to find each other, which we pass on without reading. If a direct path cannot be made, the connection can fall back to a relay we operate, which forwards the stream without storing it. Either way there is no recording of a watch party on our side. The only recording is the one being made on the organizer's own machine.

Who is responsible for what. The person recording decides that there is a party, who is let in, who is taken out and what happens to the file afterwards. For what goes into their recording, they are the one in charge of it and we are acting on their behalf. For the account they hold with us, and for the site itself, we are. If you were in somebody's recording and you want something done about it, they are the first person to ask, and section 11 says what we will do if you ask us.

How long the room lasts. A party link is good for six hours and the room behind it is held in memory rather than in a database. Names in it go when it goes, whether that is the six hours running out, the organizer closing it, or our systems restarting. Nothing about a watch party is kept afterwards.

What we cannot undo. Leaving a party stops anything further being recorded of you, and the organizer can take you out of the picture at any point. Neither reaches into a recording that has already been made, and once the organizer has downloaded the file it has left this service entirely. We will act on anything still held here and pass on a request we cannot act on ourselves. We would rather say that plainly than describe a right we have no way to deliver.

9. Who else handles it

We disclose information to service providers who work on our instructions:

• Hosting and database providers, which store the service and its records.
• Object storage, where uploaded photographs and videos are kept when the service is configured to use it.
• Google, for Continue with Google, and for venue autocomplete on the setup page. Venue lookup runs in the organizer's own browser and sends Google what they type into that one field. It sends Google nothing about guests and nothing about moments.
• Google Analytics, and only if you accepted it. It receives the pages you visited on this site, an identifier for your browser, and the general location and device details any web request carries. It receives nothing you recorded, nothing you uploaded and no event you joined. Google is in the United States, so this transfer relies on the EU and UK standard contractual clauses and the Data Privacy Framework. Section 14 says how to turn it off.

We may also disclose information when the law requires it, when we must to protect somebody's safety or our rights, and to a buyer if the Clockitlive service or the business is sold or reorganised within our group, in which case this policy follows the information.

Kooemma Digital Holdings LLC runs other things besides Clockitlive. What is shared inside an event stays inside Clockitlive: we do not move it to another product in the group, and we do not combine it with information held by one.

10. How long we keep it

• Moments and albums are kept while the event exists. Deleting an event deletes its stored media with it.
• Guest records are part of the event and go when it does.
• Watch party rooms last six hours and are held in memory rather than in a database. The names in one go when it goes. We keep no record that a party happened, and no recording of one: the only recording is on the organizer's own machine.
• Organizer accounts are kept until the account is closed, and then for a short period in case it is reopened.
• Server logs are kept for a limited period and then rotated away.

Backups are not erased the instant a deletion happens. Deleted content falls out of them on the ordinary backup cycle.

11. Your privacy rights

Depending on where you live, you may have the right to know what personal information we hold and how we use it, to get a copy of it in a portable form, to correct it, to delete it, and to be free of discrimination for asking. California, Colorado, Connecticut, Virginia, Utah, Texas, Oregon, Montana and a growing number of other states give some or all of these rights.

To exercise any of them, write to support@clockitlive.com from the address on the account, or tell us enough about your involvement in an event that we can find the records. We will confirm who you are before we act, because handing somebody else's photographs to the wrong person is the failure that matters here. We answer within forty-five days and will tell you if we need longer.

An authorized agent may act for you with written permission. If we refuse a request, you may appeal by replying to our answer, and we will review it and give reasons.

If you are in a photograph you did not post, you do not need an account to have it taken down. Tell the organizer of that event, who can remove it from every screen at once, or write to us and we will act on it.

California residents may also ask, once a year and free of charge, for the list of any personal information disclosed to third parties for their direct marketing purposes under California's Shine the Light law. There is nothing to report: we disclose nothing for that purpose.

12. Children

Clockitlive is not directed to children under 13, and we do not knowingly collect personal information from them. Holding an organizer account requires being 18 or older.

Children are at the events this is built for. An organizer who invites them takes on responsibility for what is shared of them, and a parent or guardian who wants a child removed from a feed should tell that organizer, who can take it down in seconds. If you believe we hold information from a child under 13, write to support@clockitlive.com and we will delete it.

A watch party link is made to be forwarded, which means it can reach somebody it was never sent to. We cannot tell how old the person opening one is, and we do not try to work it out: doing so would mean collecting more about them than the name they typed. So it rests with the person recording, who sees who is asking to come in and decides. If a child has ended up in a recording, ask the person who made it, and write to us as well.

13. Security

Passwords are hashed with scrypt, a memory-hard function, and are never stored in a form we could read. Sign-in failures return the same message whether the address is unknown or the password is wrong, so the service cannot be used to work out who has an account. Traffic is served over HTTPS. Stored media keys carry a random identifier, so a file cannot be found by guessing.

No service is perfectly secure, and this one is candid about where its edges are. If you find a weakness, please tell us at support@clockitlive.com before telling anyone else.

14. Cookies, tracking and Do Not Track

We use the storage in your browser to keep you signed in, to remember which event you joined, and to hold recordings on your own device until you upload or discard them. None of that is optional, because without it the thing you asked us to do does not work. We do not ask permission for it and we do not use it to follow you anywhere.

One thing is optional, and we ask first. We use Google Analytics to count visits and see which pages get used. It sets cookies on your device named _ga and _ga_<id>, which last up to two years and hold a randomly generated number that lets Google tell one browser from another. It does not load at all until you accept it. If you refuse, or if you never answer, no Google script is requested and no such cookie is set.

Change your mind whenever you like: Cookies at the foot of any page reopens the choice. Turning it off deletes those cookies as well as stopping them being set again. We ask again after a year, so an answer you gave once does not stand forever.

We use no advertising cookies and we run no advertising trackers. Google's advertising signals are switched off explicitly on our side, so what we send is used to count visits and not to build a profile or to target anything at you.

Because we do not sell or share personal information, there is nothing for a Do Not Track signal to opt you out of. We do act on Global Privacy Control: if your browser sends it, we treat that as a refusal of analytics, we do not load Google Analytics, and we do not ask you the question.

15. Changes

If this policy changes we will update the date at the top of this page, and for anything significant we will say so in the product rather than leaving you to notice.

16. Contact

Kooemma Digital Holdings LLC
support@clockitlive.com

One address for all of it: privacy requests, security reports and everything else. Say in the subject line which it is and it reaches the right person.