1. Who we are and what this covers
KipDay (“KipDay”, “we”, “us”) operates KipDay Account at auth.kipday.com (the “Service”), the central sign-in and identity service for KipDay apps. This policy covers the personal data the Service handles. The apps you sign in to are separate and may have their own privacy notices.
Using the Service is also subject to the Terms of Service.
2. What we collect
What you give us
- Email address. You sign in with it and we send one-time codes to it.
- First and last name. Required. We also keep them as your display name.
- Phone number. Optional. Stored in international format together with its country.
- Birthday. Optional.
- Your agreement. The version of these documents you accepted and the time you accepted it.
From Google, if you sign in with or connect Google
- Your Google account identifier, email address, name and a link to your profile picture, and the tokens Google returns for the connection. Your first and last name from Google are used to pre-fill your profile.
Sign-in security
- Passkeys: the public key and related details of each passkey you register, with the name you give it. The private key stays on your device.
- Authenticator app (TOTP): the secret and backup codes used for two-step verification. It is optional for most accounts and required for administrators.
- Last sign-in method: whether you last used Google, an email code or a passkey, so we can suggest it next time.
Security activity
- Security activity log. A record of security-relevant events on your account, such as sign-ins and failed sign-in attempts, changes to your sign-in methods, email, profile or sessions, apps you allowed or revoked, and actions administrators take on your account. Each entry records what happened, when, and the result, together with the IP address, the approximate country, the time zone, a short browser and operating-system summary (for example “Chrome · macOS · desktop”) and the language of the request. The email address of the person who acted is stored as a label with the entry.
- Sign-in device fingerprints. To tell whether a sign-in comes from a device and place we have not seen before, we store a hash of your browser family, operating system and country. Only the hash is kept, not those details.
Sessions
- For each device signed in: a session token, when it was created and when it expires, the IP address and the browser/device description (user agent) it was created from, and whether it is an administrator impersonation session.
Apps you use
- Which apps you allowed, which permissions you gave them and when; the access and refresh tokens issued to those apps; and, if you sign in to a command-line tool or TV app with a code, the pending request for that code.
- Permissions that administrators assign to your email address inside an app (for example a team membership). These can be set before you first sign in.
API keys
- For each key you create: its name, a hashed copy of the key with a short visible prefix, its optional expiry date, any metadata you attach and usage counters. The key itself is shown only once, when you create it.
Account status
- Whether your account is suspended and, if so, the reason and any end date an administrator recorded.
Technical data
- One-time codes (stored in hashed form and expiring after 5 minutes), short-lived counters that limit how many requests can be made (they are keyed by things like IP address and email address), and operational logs on our hosting platform.
We do not have passwords, we do not collect payment details, and the Service does not include advertising trackers. We measure usage with Cloudflare Web Analytics, which is cookieless and does not fingerprint you: it records aggregate page-view data (the page path, the referrer, your country, browser and device type, and page performance timings) that we do not use to identify you. It is not loaded on pages that carry sign-in codes or tokens.
3. How we use it
- To create your account, sign you in and keep you signed in.
- To send you sign-in and email-change codes.
- To let apps identify you, only as described in section 4.
- To protect the Service: limiting request rates, checking that sign-in requests come from a person, spotting abuse, and suspending accounts when needed.
- To keep your account secure: showing you your recent security activity and spotting sign-ins from a new device or place.
- To send you security notifications, such as an alert when your account is signed in to from a new device or when a sign-in method changes.
- To investigate fraud and abuse.
- For administrator accountability: every administrator action is recorded, as described in section 9.
- To provide support and administration, including the administrator access described in section 9.
- To keep a record that you accepted our Terms and this policy.
- To meet legal obligations.
We do not sell your personal data and we do not use it for advertising.
4. What apps receive
An app only receives information about you through KipDay Account when you sign in to it. On the consent screen you see what it asks for. The permissions that can be requested are:
- Confirm your identity: your account identifier.
- Profile: your first and last name, your birthday and your profile picture, where you have them.
- Email: your email address.
- Phone: your phone number.
- Stay signed in: lets the app keep access while you are not using it.
Apps also receive the list of permissions that administrators have granted you inside that app, so that the app knows what you may do.
Your choice is remembered until you revoke it in your account. If an app later asks for more than you allowed, you are asked again. Apps that KipDay runs itself (first-party apps) may skip the consent screen.
If you give an API key to an app or service, that app can check the key with us and then receives your account identifier, email address, name and picture, together with the key’s name, permissions and expiry.
Once an app has received information, how it uses and keeps it is governed by that app’s own privacy notice.
5. Service providers
We use these providers to run the Service. They process data on our behalf, or, for Google, on your choice:
- Cloudflare: hosts the Service and its database (Workers and D1), applies request rate limits, and provides Turnstile, the bot check used when you request a sign-in code or change your email, and Web Analytics, which gives us cookieless, aggregate page-view and performance statistics.
- Resend: delivers our emails. It receives your email address and the content of the message, including the one-time code.
- Google: only if you choose to sign in with or connect a Google account. Google’s own privacy policy applies to what Google does.
These providers may process data in the countries where they operate. We may also disclose information when we are legally required to, or to protect the security of the Service and its users.
7. How long we keep data
- Account details: for as long as your account exists.
- Sign-in codes: expire after 5 minutes, allow a limited number of attempts, and are stored hashed.
- Sessions: valid for up to 30 days and renewed while you use them; removed when you sign out or revoke them. Administrator impersonation sessions last at most one hour.
- Device-code requests (command-line and TV sign-in): valid for 15 minutes.
- App permissions and tokens: until you revoke them, they expire, or your account is deleted.
- Security activity log: sign-in events are kept for 90 days. Security and administrator events are kept for 365 days; their IP address is kept for the first 90 days and is then shortened. An IPv4 address is stored in full and, after 90 days, its last part is cleared. An IPv6 address is never stored in full: only its first 64 bits (the network) are kept, and after 90 days everything after the first 48 bits is cleared. Older entries are deleted automatically every day.
- Notification log (a record that a security email was sent, used to avoid duplicates and to limit how many are sent): 30 days.
- Sign-in device fingerprints: 90 days after the device was last seen.
- “This wasn’t me” links in security emails: expire after 24 hours and work once.
- Request counters and logs: counters track windows of about a minute. Operational logs are kept by our hosting platform for a limited period.
Deleting your account. You can delete your account in security settings; for safety you must have signed in within the last day. Deleting it removes your profile, your sign-in methods (Google link, passkeys, authenticator app), your sessions, your app permissions and the tokens issued to apps, and any app memberships that were assigned to your email address. Your API keys are deleted with the account, so apps using them stop working immediately. Accounts with administrator access cannot be deleted from the self-service page.
What stays: the security activity log is not deleted with your account. Its entries are kept until their own retention period above ends, and still identify the account by its internal identifier and by the email address recorded with each entry. Your notification log, sign-in device fingerprints and “This wasn’t me” links are deleted with the account. Information that apps already received about you remains with those apps under their own policies, and copies in backups kept by our hosting provider can persist for a limited time until they expire.
8. Your choices and controls
Most things you can do yourself, any time:
- See and edit your name, phone number and birthday, and change your email address (confirmed with a code sent to the new address), in your account.
- Connect or disconnect your Google account, in your account. You cannot disconnect your only linked account.
- Manage passkeys and your authenticator app, see which devices are signed in, and sign out other devices, in security settings.
- See your recent security activity, in security settings.
- Review and revoke the apps that have access, and manage your API keys, in your account.
- Delete your account, in security settings.
Security emails, such as new-device sign-in alerts, are part of keeping your account safe and cannot be turned off.
If you need something these controls do not cover, such as a copy of your data, email contact@kipday.com. We will handle your request as required by the law that applies to you.
9. Administrator access and impersonation
A limited number of people designated as KipDay administrators can use an admin area. They can:
- search users and see their email address, name, status and last sign-in method;
- see a user’s sessions, including IP address and browser/device description;
- suspend or reinstate an account (and record a reason), sign a user out of their sessions, and delete users;
- manage which apps and permissions a user has;
- sign in as a user (“impersonation”), to help with support or to investigate abuse.
Every administrator action on your account is recorded in the security activity log, including each action taken while impersonating you. You see some of these entries in your recent security activity, labelled “KipDay administrator” rather than with the administrator’s name: impersonation sessions, actions taken while impersonating you, suspensions and reinstatements, and administrators signing you out of your sessions. Other administrator changes are logged but visible only to administrators.
An impersonation session lasts at most one hour and is marked as an impersonation session in the session record. While it is active, the administrator sees a banner saying they are signed in as you. The admin area requires administrators to enrol an authenticator app and to verify with it before entering.
10. Security
Security measures in the Service include: no passwords to steal or reuse; one-time codes stored hashed, short-lived and limited in attempts; optional passkeys and authenticator-app verification; bot checks and rate limits; secure cookies on the live site; pages that cannot be embedded in other sites; API keys stored hashed; and sessions that you can end yourself.
No system is completely secure, and we cannot promise that your data will never be accessed without permission.
11. Children
KipDay Account is not directed at children. We do not check age at sign-in. If you believe a child has created an account without a parent or guardian’s permission, email contact@kipday.com so we can look into it and remove the account where appropriate.
12. Changes to this policy
We may update this policy. The “Last updated” date at the top shows the current version. When a new version needs your agreement, we ask you to accept it the next time you sign in.
13. Contact
Use the controls in your account and security settings for your data. For anything else, email contact@kipday.com.