UUDO
Privacy Policy
Last updated: October 9, 2026
Introduction
This Privacy Policy explains how UUDO (“UUDO”, “we”, “us”) collects, uses, shares, and protects your personal data when you use the UUDO mobile application for iOS and Android (the “App”) and the UUDO website at uudo.app (the “Site”). UUDO is a community platform for university students. The student experience is delivered exclusively through the mobile App; the Site is informational.
The data controller responsible for your personal data is João Pedro Vartanian, who can be reached at privacy@uudo.app.
UUDO is currently in beta. We may add, change, or remove features during this period, and we will keep this policy current as the product evolves.
This policy is written to comply with the Brazilian General Data Protection Law (Lei Geral de Proteção de Dados, Law No. 13.709/2018, the “LGPD”) and, for users in the European Union and European Economic Area, the General Data Protection Regulation (the “GDPR”).
Personal data we collect
We collect only the data we need to operate UUDO. Depending on how you use the App and Site, this includes:
- Account and identity: your email address and your first and last name.
- Age verification: your date of birth, used once to confirm that you are at least 18. We compute your age on our servers and discard the date immediately — it is never stored in our database and never written to our logs. Only the result of that check is kept.
- Academic profile: your university, your academic program and major, up to two minors, up to five certificate programs, and the year and semester you started your program.
- Profile content: an optional short bio, a profile photo, and the interests you choose to personalize your experience.
- App preferences: interface settings such as reduced-motion and haptics. These are user-experience preferences only — they are not health or disability data.
- Social activity: the connections (“bonds”) you make, accounts you block, the chat rooms you join, the messages you send, the events you sign up for, the articles you save, the student organizations you apply to join or belong to — including your membership status, any position you hold, when you joined or applied, and when that status last changed — and a short-lived record of the content you view.
- Requests to create an organization: when you ask to create a student organization, we store the request: you as the requester and your university; the proposed name, identifier, description and type; the interests you select; an optional logo; the evidence that you accepted the Organization Terms (the version, the time, a digest of the text, and its language); and the decision, with the name of the reviewer who made it, when they made it, and any reason they gave for declining. We keep the logo in private storage and show it to reviewers through short-lived links. If the request is approved, the logo becomes the public logo of the organization.
- Student-government claims: if you ask to become your university’s governing body, the request also stores the position you say you hold and a verification note of up to 500 characters that you write so that UUDO can check the body’s standing. Only UUDO sees a claim, never a governing body. The App does not show the verification note back to you, but it is included in your data export.
- Communications: messages you send through in-app chat, support requests together with any screenshots or files you attach to them, and details you submit through forms on the Site (waitlist, contact, research, institution-request, and add-your-university forms), which may include your name, email, phone number, and any message you write.
- Reports you make: if you report another user or a piece of content, we record who or what you reported, the category you chose, and anything you write to explain it.
- Notifications: the title and body text of the notifications we send you, both the ones shown inside the App and the ones delivered to your phone. If you allow push notifications, we also collect a device push token that identifies your phone for delivery, along with the platform and app version it was registered from.
- Location: an optional map pin that a leader of a student organization places on an event, stored as a latitude and longitude rounded to about 11 meters. If you tap “Use my current location” while you place a pin, the App also reads your device’s precise location once to center the map; we do not store it. See “Location” below.
- Technical and security data: records kept in our security and audit logs to protect the platform. Depending on the event, these may include your IP address and device or browser information, or only reduced details such as your email domain and a one-way hash of your email address.
- Website analytics: on the Site only, and only if you accept analytics cookies, standard usage data through Google Analytics and performance data through Vercel. The mobile App contains no advertising or product-analytics trackers.
We do not use profile photos for biometric identification, facial recognition, facial matching, facial search, biometric-feature extraction, or any other Art. 5 II processing. They are stored only for display in the App and Site.
What we do not collect
To keep your data minimal and safe, UUDO does not collect:
- sensitive personal data under LGPD Art. 5 (such as data on health, racial or ethnic origin, religious or political belief, union membership, sex life, or biometric or genetic data);
- a stored copy of your date of birth — we compute your age from it at sign-up and discard it immediately (see “Age verification” above);
- your location history, or your device’s location in the background — the App reads your device’s location only when you tap “Use my current location” (see “Location” below);
- payment or financial data.
We do not profile you using sensitive data, and we operate no advertising network.
How and why we use your data
We process your personal data for the purposes below, each under a specific legal basis:
| Purpose | Data used | LGPD basis (Art. 7) | GDPR basis (Art. 6) |
|---|---|---|---|
| Create and manage your account; sign you in | Email, name, academic profile | Performance of a contract (V) | Contract (b) |
| Record and prove that you accepted the Terms of Service and Privacy Policy | Email address, IP address, device or browser information, which version of each document you accepted, and when | Legal obligation (II); legitimate interest (IX) | Legal obligation (c); legitimate interests (f) |
| Verify your university and keep each university’s community separate | Email domain, university | Performance of a contract (V); legitimate interest (IX) | Contract (b); legitimate interests (f) |
| Personalize the people and content you see | Interests, academic profile, social activity | Consent (I); legitimate interest (IX) | Consent (a); legitimate interests (f) |
| Enable chat and social connections | Chat messages, bonds, blocks, room membership | Performance of a contract (V) | Contract (b) |
| Let you sign up for events and manage event capacity | Event sign-ups, academic profile | Performance of a contract (V) | Contract (b) |
| Run student organizations: join requests, member rosters, and the management console their leaders use | Organization membership status, any position held, join and status-change timestamps, name and profile photo | Performance of a contract (V); legitimate interest (IX) | Contract (b); legitimate interests (f) |
| Show students the exact place of an organization event | The map pin you add to an event (latitude and longitude rounded to about 11 meters) | Performance of a contract (V); legitimate interest (IX) | Contract (b); legitimate interests (f) |
| Center the map on your position when you ask | Your device’s precise location, read once on your device and not stored | Consent (I) | Consent (a) |
| Submit and review requests to create a student organization | The request content (name, identifier, description, type, interests, logo and, for a student-government claim, the position and verification note), the decision, the reviewer and any decline reason | Performance of a contract (V) for the request content; legitimate interest (IX) for the decision, the reviewer and the decline reason | Contract (b) for the request content; legitimate interests (f) for the decision, the reviewer and the decline reason |
| Keep proof that you accepted the Organization Terms when you submit a request | The version you accepted, when, a digest of the text, and its language | Legitimate interest (IX); regular exercise of rights (VI) | Legitimate interests (f) |
| Send you notifications about events, news and messages | Notification title and body, device push token | Performance of a contract (V); legitimate interest (IX) | Contract (b); legitimate interests (f) |
| Review reports of users or content and keep the community safe | What you reported, the category, your message | Legitimate interest (IX); legal obligation (II) | Legitimate interests (f); legal obligation (c) |
| Send you service and account emails | Performance of a contract (V) | Contract (b) | |
| Protect the platform: security, abuse and fraud prevention, rate limiting | IP address, device information | Legitimate interest (IX); legal obligation (II) | Legitimate interests (f); legal obligation (c) |
| Provide customer support | Your message, email, name, university | Performance of a contract (V); legitimate interest (IX) | Contract (b); legitimate interests (f) |
| Understand product usage in aggregate | Anonymized, grouped statistics (no individual identifiers) | Legitimate interest (IX) | Legitimate interests (f) |
| Measure Site traffic | Analytics cookies (Site only) | Consent (I) | Consent (a) |
Where we rely on consent, you may withdraw it at any time. Our aggregate product statistics are computed with a minimum group size so that no individual can be identified.
Age requirement
UUDO is intended only for university students aged 18 or older. When you sign up we ask for your date of birth, confirm on our servers that you are at least 18, and then discard the date, keeping only the result. We do not knowingly collect personal data from anyone under 18. If you believe a minor has provided us data, contact privacy@uudo.app and we will delete it.
International data transfers
UUDO’s infrastructure and several of our providers are located in the United States, so your personal data is processed outside Brazil and outside the EU/EEA. These transfers are carried out on the basis of our legitimate interests in operating UUDO, subject to oversight by the ANPD (LGPD Art. 33, VIII) and, for EU/EEA users, on the basis of standard contractual clauses or other lawful mechanisms under Chapter V of the GDPR.
How we protect your data
All data is transmitted over encrypted connections (TLS/HTTPS).
Chat messages are encrypted at rest on our servers using AES-256-GCM, with keys held only by our backend, so that access to the database alone does not reveal message content. Extending these protections to message-derived data such as conversation previews, and to locally cached copies on your device, is on our security roadmap.
We offer optional two-factor authentication (TOTP), and we enforce database-level access controls so that each university’s data stays separate.
Chat is not end-to-end encrypted: because messages are encrypted with keys we manage, our systems are technically able to process message content in order to operate the service.
No method of storage or transmission is completely secure, but we protect your data using industry-standard measures.
How long we keep your data
We keep personal data only as long as needed for the purposes described above:
| Data | How long we keep it |
|---|---|
| Account and profile data | Until you delete your account |
| Consent records (proof that you accepted our documents) | Kept for the life of the account; retained separately from security and audit logs and not subject to the platform-protection schedule. If you accept our documents but never finish creating an account, that record is deleted within ten minutes. This row does not cover your acceptance of the Organization Terms, which follows the retention of the request it belongs to (see “Requests to create an organization” below). |
| Data after a deletion request | Most data is erased; chat you sent is anonymized, and a small amount is kept pseudonymized so it no longer identifies you |
| Security and audit logs | Kept indefinitely (needed to detect and investigate abuse) |
| Raw content-view records | Deleted within 48 hours |
| Device push token | Revoked when you sign out; deleted 30 days after revocation |
| Push notification content (title and body) | Deleted 30 days after we send it |
| In-app notifications | Deleted 90 days after the notification is created if you have read it, or after 180 days if you have not |
| Support requests and any files you attach | Until you delete your account |
| Add-your-university requests | Deleted 90 days after the request is reviewed; a request nobody reviews is closed automatically after 180 days |
| Event map pin | Kept with the event it belongs to; your device’s location is never stored |
| Requests to create an organization, with the Organization Terms acceptance evidence they hold | We keep a pending request until it is decided. We delete a declined or withdrawn request 180 days after it closes, counted from the withdrawal, or else from the decision. We keep an approved request while the organization it created exists, and delete it once that organization no longer exists and 180 days have passed since the decision. We delay a deletion while a decision notice for the request is less than 180 days old. A notice you have read is itself deleted 90 days after we created it, so the delay can end at 90 days. |
| Requests to create an organization, if you delete your account | We delete your pending, declined and withdrawn requests. We keep an approved request, unlinked from you, as the organization’s record of origin: its name, identifier, Organization Terms acceptance evidence and link to the organization stay. We remove its description, logo and interest selection, and we replace a verification note with a placeholder. |
| Logo submitted with a request | We keep the logo of a pending request in private storage. We delete the logo of a declined request 30 days after the decision, and the logo of a withdrawn request 30 days after the withdrawal. When a request is approved, the logo becomes the public logo of the organization and we delete the private copy. |
| Aggregate, anonymized statistics | Kept indefinitely (no longer identifies you) |
You can cancel a deletion request within 7 days. After that we complete it within the legal response window (15 days under the LGPD, Art. 18). Most accounts — including every student account — are erased in full; if you are staff, a content author, or hold administrative permissions, some authorship attribution on institutional content is retained and our Data Protection Officer completes your request by hand. See “Delete your account or data” for exactly what is erased and what is kept. We may keep some data longer where necessary to comply with a legal obligation or to resolve a dispute.
Your rights
Under the LGPD (Art. 18), you have the right to:
- confirm that we process your data, and access it;
- correct incomplete, inaccurate, or outdated data;
- anonymize, block, or delete data that is unnecessary, excessive, or processed unlawfully;
- request the portability of your data to another provider;
- delete data we process based on your consent;
- be informed about the public and private entities with which we share your data;
- be informed about the consequences of refusing to give consent;
- withdraw your consent at any time.
If you are in the EU or EEA, the GDPR also gives you the rights of access, rectification, erasure, restriction of processing, data portability, objection to processing, and withdrawal of consent. To exercise any of these rights, email privacy@uudo.app or delete your account directly in the App. We will respond within the timeframes set by law.
Data Protection Officer (Encarregado)
We have designated a Data Protection Officer to serve as the point of contact between you, UUDO, and the data protection authorities on any question about how we handle your personal data. Under the LGPD (Art. 41) this role is the Encarregado; under the GDPR (Arts. 37–39) it is the Data Protection Officer (DPO).
Our designated Encarregado and Data Protection Officer is João Pedro Vartanian, who can be reached at privacy@uudo.app. You may contact this address to exercise any of the rights described above or to raise any concern about how your personal data is handled.
Calendar
When you add a UUDO event to your device calendar, that information is written only to your phone’s calendar. No calendar data is sent to our servers.
Location
UUDO does not track your location. The App uses location in two limited ways, and only when you create an event for a student organization that you lead.
- Map pin on an event: You can add a pin to an in-person or hybrid event. You move the map until the pin sits on the entrance or the place of the event, and then you confirm it. We store the pin with the event as a latitude and longitude rounded to about 11 meters. People who can see the event can see the pin, and it lets them open the place in their phone’s maps app. The pin is optional: you can publish an event without one, and you can remove it before you publish.
- Your current location: When you tap “Use my current location”, the App asks your phone for permission to use your location while the App is open. If you allow it, the App reads your device’s precise location to center the map. That location is not stored and is not sent to our servers; only the pin you confirm is. Because you may be standing at the place, the pin you confirm can be close to where you are. If you decline, you can still move the map by hand and place the pin. You can change this permission at any time in your phone’s settings.
- Map providers: To draw the map and to look up the address shown next to a pin, the App uses Apple Maps on iOS and Google Maps on Android. These providers receive the area of the map you view and the position of the pin, and they process that data under their own privacy policies. The address is shown only on your screen; we do not store it. We do not use location data for advertising.
Push notifications
If you enable push notifications, we register a device token for your phone and use it to deliver notifications directly to your device — for example, event reminders, chat messages, and organization join approvals. We send that token, and each notification, directly to Apple’s Push Notification service (APNs); we do not route push notifications through any third-party push service. Push notifications are currently available on iOS only.
- Device push token: a token identifying your device for notification delivery. It is revoked when you sign out and permanently deleted within 30 days of revocation, or immediately if you delete your account.
- Notification content: the title and body text of the notifications we send you are stored on our servers for up to 30 days so that we can deliver them, and deleted immediately if you delete your account. This is separate from the device token above — it is the content of the message itself, not merely the delivery address. The same notification also appears in your in-app notification list, which we keep for longer; see “How long we keep your data”.
Changes to this policy
We may update this policy as UUDO evolves. When we do, we will revise the effective date at the top of this page. For material changes during beta, we will also notify you in the App or by email.
Contact us
For any question about this policy or your personal data, contact the data controller, João Pedro Vartanian, at privacy@uudo.app.