Privacy Policy
Last updated: October 13, 2026
This policy explains what information Daimor collects, why we collect it, how long we keep it, and the choices you have. It covers the Daimor iPhone app and the website at daimor.app.
The short version
- Daimor is free and non-profit. We don't show ads, we don't sell your personal information or share it for advertising, and we don't track you across other apps or websites.
- We collect what we need to run the app: your account and profile, what you post, and basic technical and safety records.
- Your phone number, email address and school email are never shown to other members. Phone numbers and school emails are stored encrypted.
- You can delete your account in the app at any time.
- We don't use identifiable personal information for academic research.
Who we are
Daimor is a free, non-profit service operated by Hamin Lee, an individual ("we," "us"). It is built and run together with student members of Social Networking Labs (SNL), a student organization at the University of Wisconsin–Madison. Daimor is not an official service of, and is not endorsed by, the University of Wisconsin–Madison.
Daimor is not a business. It has no ads, no payments and no in-app purchases, and nothing is sold. For any privacy question or request, email [email protected].
What we collect and why
Account and verification
- Sign-in details. Your email address, and a password if you sign up with email (we store only a secure Argon2id hash of it). If you use Sign in with Apple or Google, we receive an account ID and email address from them, and from Apple your name if you choose to share it. We use these to create and protect your account.
- Phone number (required). Daimor accepts US (+1) mobile numbers only. Google Firebase sends the text-message code, and we ask Firebase to delete its record of the verification right after the check. We store your number encrypted (AES-256-GCM) together with a salted hash, which we use to allow one account per phone number and to stop banned users from signing up again.
- Birthdate (required). Used to confirm you are 18 or older. Other members may see your age, never your birthdate.
- School email (optional). If you verify a .edu email to get a student badge, we email a code to that address and store it encrypted with a salted hash, so one school email can't be used on several accounts. It is not used to sign in. Other members see a student badge with your school's short name (for example, "UW–Madison") on your profile, in room member lists, and on chat and DM cards. They never see the email address itself.
- Agreements. Which terms you accepted and when, your 18+ confirmation, and the IP address used when you confirmed your age. We keep these as records of your consent.
Your profile
- Profile. Your nickname, up to 8 profile photos, bio, hobbies and interest tags, and any optional details you choose to add, such as gender, height, body type, where you live, MBTI, school, major, job, religion, drinking and smoking. Other members can see your profile.
- Sensitive details are optional. Details like religion are sensitive under some state laws. You never have to add them, and we use them only to show on your profile.
- Your state. The US state you pick, used to show rooms and people near you.
What you post and do
- Rooms. If you create a room: its title, vibe, category, meeting days, photo, and the meeting address and map location you enter.
- Messages. What you send in room group chats and DMs (chats are text only), DM requests, and event cards you share into a chat.
- Activity. Rooms you join, likes, activity points you earn, invite codes you share or use, and the people you block.
- Reports. Reports you send (reason and details) and reports about you. When a message is reported, we keep a copy of it (up to 2,000 characters) with the report as evidence for moderation. We also keep records of moderation actions.
- Feedback. Feedback you send in the app, with your rating, app version and platform.
Location
Daimor asks for location permission only while you are using the app, to show rooms and events near you. You can say no and still use Daimor, and you can change this at any time in iOS Settings. We never collect location in the background.
- Map. Your location is used on your device to center the map. To load rooms, the app sends us the area of the map on your screen, which can show roughly where you are. We don't save it.
- Your state. After you sign up, if you haven't picked a state yet, the app may send your approximate location (coordinates rounded to about 1 km) to our server to suggest one. We pass only these rounded coordinates to Google's geocoding service to look up the state, and we do not save them in our database.
- Room addresses. When you search for a meeting address while creating a room, the address you type is sent through our server to Google Maps. The address you choose is saved with the room.
Our own server logs record only the path of each request, never search text or coordinates. Our load balancer's access logs record full request addresses, so rounded coordinates and map areas can appear there. Both are deleted on a schedule (see How long we keep information).
Device and technical information
- Sessions and security logs. For each device you're signed in on, we keep its IP address, user agent (a short description of the app and device) and when it was last used. We also log sign-in events, such as successful and failed logins and password changes, with IP address and user agent, to protect accounts and investigate abuse.
- Push notifications. Your device's push token (used with Firebase Cloud Messaging and Apple Push Notification service) and your notification settings. Notifications pass through these services, and a chat notification can include the sender's nickname and the start of the message.
- Device settings. Your device's region, language and time zone, to set up the app for you and keep the service US-only.
- In-app events. A small number of usage events (for example, how you answered the in-app feedback prompt), with a random ID stored on your device and, when you're signed in, your account. We use them only to understand and improve the app.
- Crash reports. If the app crashes, Firebase Crashlytics sends a report with technical details such as device model, iOS version, app version and our internal user ID. We don't add your name, email or phone number to crash reports.
- App integrity. Firebase App Check uses Apple's App Attest and DeviceCheck to confirm that requests come from the genuine Daimor app.
- Server logs. Our servers and load balancer record requests (such as the address requested, IP address and time) for security and troubleshooting.
Daimor doesn't access your contacts, camera or microphone. Photo library access is used only to pick the photos you upload. We don't use the advertising identifier (IDFA), and the app contains no advertising or third-party analytics SDKs.
The daimor.app website
The website is hosted by Cloudflare. When you open the home page or a daimor.app/go/ link, we record the time, the link code, the type of device (iPhone, Android or computer), whether the link was opened inside another app's browser, your country, and the referring page. We don't store your IP address with these records, and they are deleted after 100 days. The home page loads fonts from Google Fonts and jsDelivr, which receive your IP address when your browser requests them. The legal and support pages load nothing from third parties.
How we use information
- To run Daimor: create your account, show your profile, rooms, chats, DMs, events and the map, and send the notifications you have turned on.
- To keep people safe: confirm members are real, 18 or older and in the US; allow one account per phone number; automatically check messages, room titles and descriptions, nicknames, bios and profile details for slurs and child-exploitation terms before they are posted; review reports (the operator gets an email alert for each new report, with no personal information in it, and reviews the report in a private moderation console); block, suspend and ban accounts; and prevent spam, fraud and account takeovers.
- To suggest people and rooms: for example, daily suggestions of other members in your state. These use simple rules (such as your state and whether your profile has a photo), not profiling.
- To contact you: sign-up, password-reset and school verification codes by email, replies to your support requests, and important notices about Daimor or these policies. We don't send marketing emails or marketing notifications.
- To improve Daimor: fixing crashes, seeing which features are used, and reading your feedback.
- To follow the law and respond to valid legal requests.
Research and statistics
We may use de-identified, aggregated statistics (for example, how many rooms were created in a month) to improve the service and to share general insights with SNL members. These statistics do not identify anyone. We do not use identifiable personal information for academic research. If that ever changes, we will first obtain any required review (for example, from a university Institutional Review Board), update this policy, and notify you before it starts.
Who can see or receive your information
Other people
- Other members can see your profile (nickname, photos, age, bio, hobbies and the details you add), your student badge with your school's short name if you verified a school email (on your profile, in room member lists, and on chat and DM cards), and the messages you send in chats they are in.
- Anyone using the app, even without signing in, can see rooms, including the room photo, meeting address and map location, and the host's main profile photo.
- Never shown to other members: your phone number, email address, school email address and birthdate.
Service providers
We use these providers to run Daimor. They handle information on our behalf, only to provide their services to us.
- Amazon Web Services (AWS), US East (Ohio): our servers; the database (Amazon RDS, encrypted); photo storage and delivery (Amazon S3 and CloudFront, with private photos available only through short-lived signed links); transactional email (Amazon SES, for sign-up codes, password resets and school verification codes); and security logging.
- Google Firebase: phone number verification (Firebase Phone Auth), push notifications (Firebase Cloud Messaging), crash reports (Crashlytics) and app integrity checks (App Check).
- Google: Google Sign-In, and Google Maps Platform for the map, address search and looking up your state.
- Apple: Sign in with Apple, Apple Push Notification service, and App Attest and DeviceCheck.
- Cloudflare: hosting the daimor.app website.
Legal and safety reasons
We may disclose information when the law requires it (for example, a valid subpoena or court order), or when we believe in good faith that it's needed to protect someone's safety, investigate abuse or fraud, or enforce our Terms of Service. In particular:
- Child safety. As federal law requires, we report apparent child sexual exploitation (including child sex trafficking and enticement) to the National Center for Missing & Exploited Children (NCMEC), which may share reports with law enforcement. A report can include the content and information about the account involved, such as nickname, email address, phone number and IP addresses.
- Removal requests. When someone asks us to remove an intimate image shared without consent, or sends a copyright (DMCA) notice, we act on it as described in our Terms. If we remove your content because of a DMCA notice, we may share the notice with you, and if you send a counter-notice, we share it, including your contact details, with the person who sent the notice, as the law requires.
If responsibility for Daimor ever moves to another operator (for example, a non-profit organization formed to run it), we will tell you before your information is transferred.
No selling, no ads
We do not sell your personal information, and we do not share it for cross-context behavioral advertising (as those terms are used in California law). We don't show ads, don't use your information for targeted advertising, and don't track you across other companies' apps or websites.
How we store and protect information
- Your information is stored in the United States, in AWS's US East (Ohio) region. Some providers listed above, such as Google and Apple, may process information in other locations.
- Information is encrypted in transit (HTTPS) and at rest: the database, private photo storage, backups and logs are encrypted with AWS Key Management Service keys. Phone numbers and school emails are also encrypted individually, and passwords are stored only as Argon2id hashes.
- Profile photos are delivered only through signed links that expire within a few hours. Photos you upload are re-encoded, which removes hidden metadata such as the GPS location where a photo was taken.
- Access to personal information is limited to the people who need it to run and moderate Daimor.
- No system is perfectly secure. If a breach affects your personal information, we will notify you as required by law.
How long we keep information
| Information | How long we keep it |
|---|---|
| Account, profile and photos | Until you delete your account or we close it. |
| Messages you sent | Kept so conversations stay readable for the other people in them. After you delete your account, they show as sent by "Deleted user". |
| Rooms you created | Shown while the room still has members, even after you delete your account. When the last member leaves, the room is closed and hidden and its photo is deleted; the rest of the room record stays in our database. |
| Unfinished sign-ups | Deleted after 7 days: email sign-ups whose address is never confirmed, and Apple or Google sign-ups that never verified a phone number, accepted the terms or created a profile. |
| Sign-in security log (IP address, user agent) | 180 days. |
| Session records (IP address, user agent) | Until 30 days after the session ends. |
| Push token | Until you log out, delete your account, or the token stops working (for example, after you delete the app). |
| Server logs (request paths, no search text or coordinates) | 30 days. |
| Load balancer access logs (IP address and full requested address, which can include rounded coordinates or map areas) | Up to 1 year. |
| Website link records | 100 days. |
| Database backups | Point-in-time backups for 14 days, plus monthly snapshots kept for 180 days. Deleted information can remain in backups until they expire. |
| Reports (including copies of reported messages, up to 2,000 characters), blocks and moderation records | As long as needed for safety, including after an account is deleted. |
| Material we report to NCMEC, and related account information | Preserved for 1 year after the report, as federal law requires (longer if law enforcement asks us to keep it). |
| Phone number hash of a banned account | For as long as the ban lasts (permanent bans: indefinitely). |
| Terms acceptance and 18+ confirmation records | Kept as proof of consent, including after an account is deleted. |
| Phone and school email verification records (the number or email in encrypted form, a hash, and the IP address used) | 30 days, or right away when you delete your account. |
| Completed invites (who invited whom, and a hash of the invited member's phone number) | Kept after account deletion, to help prevent invite abuse. |
| In-app events | 400 days. After you delete your account they are linked only to an internal ID, not to your name, email or phone number. |
| Feedback | Kept to improve Daimor. After you delete your account it is linked only to an internal ID, not to your name, email or phone number. |
Deleting your account
In the app, go to Profile › Settings › the gear icon › Delete account. You can also email [email protected] from the email address on your account. See Delete your account for step-by-step instructions.
When you delete your account, we immediately clear your profile (nickname, photos, bio, profile details, birthdate and gender), delete your photos from storage, remove your phone number, school email and sign-in methods, delete your push tokens and your phone and school email verification records, sign you out on every device, and remove you from all rooms. Some information is kept as described in the table above: for example, messages you sent remain visible to the other people in those chats as sent by "Deleted user", and earlier system notices (such as "joined the room") may still show the nickname you had at the time.
Your choices and rights
- See and correct: you can view and edit most of your information in the app (your profile, account info and settings).
- Get a copy: email us and we will send you a copy of the personal information we hold about you.
- Delete: delete your account in the app, or ask us by email.
- Notifications: turn notification types on or off in Settings › Notifications, mute individual rooms, or turn off notifications in iOS Settings.
- Location and photos: allow or deny access at any time in iOS Settings.
US state privacy rights
Laws in California and several other states give residents rights over their personal information. Because Daimor is a non-profit project run by an individual and is far below those laws' size thresholds, the California Consumer Privacy Act and most similar state laws likely don't apply to us. We offer these rights to every user anyway, voluntarily, wherever you live: the right to know and access the personal information we hold about you, to correct it, to delete it, to receive a portable copy, and to opt out of the sale or sharing of personal information, targeted advertising and certain profiling.
We don't sell or share personal information, show targeted ads, or profile you in ways that produce legal or similarly significant effects, so there is nothing to opt out of. If your browser sends a Global Privacy Control signal, we treat it as an opt-out request anyway. We use sensitive information (such as location, account log-in details and any optional details like religion) only to provide the features you use.
How to make a request
- Email [email protected] from the email address on your account. We may ask you to confirm your identity, and you may use an authorized agent.
- We will confirm that we received your request within 10 business days, and respond within 45 days. If we need more time, we will tell you why within those 45 days and may take up to 45 more days.
- If we deny your request, you can appeal by replying to our answer with "Appeal." We will decide your appeal within 45 days; if we need more time, we will tell you why and may take up to 60 more days. If you disagree with our decision on your appeal, you can contact your state attorney general.
- We will never treat you differently for using your rights.
Children
Daimor is only for people 18 and older. We do not knowingly collect information from anyone under 18. If we learn that a user is under 18, we will close the account and delete its information as described above. If you believe someone under 18 is using Daimor, please email [email protected]. We report apparent child sexual exploitation to NCMEC as described in Who can see or receive your information.
Other websites
Event pages in Daimor may link to ticketing or organizer websites, which can open inside the app. Those sites are run by others, and their own privacy policies apply.
Changes to this policy
We may update this policy as Daimor changes. We will post the new version here with a new "Last updated" date. For material changes, we will tell you in the app or by email at least 30 days before they take effect, unless a change is required by law sooner.
Contact
Daimor is operated by Hamin Lee. Email [email protected] with any question or request about your information. We answer weekdays, 9 AM – 5 PM Central Time.