Duz Privacy Policy
Last updated: 31 October 2026
Duz is built around doing things in the real world. That means some information about you is necessary for Duz to work. For example, we need to verify that you are eligible to join, record the Duzes and Quests you complete, and, when you choose to check in, verify that you are at the right place.
We want the way we use that information to be as understandable as the product itself.
This policy explains:
- what personal information Duz collects and why;
- how we use and protect it, and who we share it with;
- how long we keep it;
- the choices and rights available to you.
For the purposes of UK data protection law, the controller of your personal information is:
- Armaan Kanayalal Kotecha, trading as Duz
- Website: www.duz.events
- Privacy contact: armaan@duz.events
Duz is an independent service. It is not operated by, or part of, Durham University.
1. What Duz is
Duz is a university social experience platform. It helps students:
- discover and take part in Duzes and Quests;
- verify real-world participation;
- collect badges and points;
- take part in college competition;
- receive updates about events they have joined.
Duz is built around real participation, not detailed social profiles, and deliberately keeps identity information lightweight.
2. Information we collect
Account and identity information
When you create or use an account, we process:
- your display name;
- your Durham University email address, and whether it has been verified;
- your university and college;
- your account and verification status;
- an optional personal recovery email address;
- when your account was created and updated;
- any roles or permissions on your account, for example if you host events.
We use your Durham email mainly to prove that you are eligible as a student. A personal recovery email, if you add one, is used only for account recovery. It is never treated as proof that you are a Durham student, and we never use it for marketing.
Sign-in, device and security information
Duz does not use passwords. You sign in with a one-time code sent to your email.
To keep accounts and the service secure, we process:
- sign-in and session records, including session identifiers;
- your device's user-agent (the browser or app version that signed in);
- IP addresses, which appear in our hosting provider's access logs;
- verification records, security and account-recovery events;
- records of logouts, session revocations, suspensions and suspicious activity.
Sign-in codes and session secrets are stored in protected form, never as readable account data, and they expire quickly.
Duz participation information
When you take part in a Duz, we record:
- which Duz you joined, and when you joined, arrived, withdrew or completed it;
- whether you joined solo, with a +1 or as part of a group;
- your temporary party or crew for that Duz;
- invitations you create, accept or redeem;
- your progress through the stops and your completion status;
- other information needed to run that specific event.
Crews and parties exist only for a single Duz. We don't use them to build a friendship network.
Location and check-in information
Duz uses your location only when you actively use a feature that needs it, such as checking in at a venue. Depending on how you check in, we process:
- your current GPS position and its reported accuracy;
- the venue you are checking in to, and the time of the attempt;
- QR-code information, or a host's confirmation;
- device information associated with the attempt;
- whether the check-in was verified or rejected, and information needed to detect duplicate, invalid or suspicious check-ins.
Duz does not track your location continuously and does not use background location.
If you have no signal, the app may keep a check-in attempt on your device briefly and send it when you're back online. Offline check-ins older than 15 minutes are not accepted.
If you don't allow location access, you may be able to check in another way, for example with a host's QR code or with a host confirming you're there.
Quest information
When you take part in Quests, we process:
- which Quests are available to you and your progress towards them;
- the verified activities that count towards a Quest;
- whether and when you completed it, including interactive Quests such as a pub quiz;
- any reward attached to it.
Quest progress can update automatically when you do something that counts towards it.
Badges, Passport and points
To run badges, your Passport and points, we process:
- the badges you have earned, when you earned them, and the Duz or Quest they came from;
- your points transactions, with the reason and source of each;
- your lifetime and monthly totals;
- the college your points counted towards at the time they were recorded;
- individual and college standings;
- corrections made by authorised administrators.
Points are kept in an append-only record, so rewards and corrections stay auditable. Individual and college standings are part of the product.
If you deliberately create a share link for a badge, anyone with that link can see that badge and what its share card shows. The rest of your Passport stays private.
Notification information
If you turn on notifications, we process:
- your device's push token;
- your notification preferences;
- scheduled notifications, and records of delivery attempts and their outcomes;
- what's needed to send you live updates while Duz is open.
On iPhone, push notifications are delivered through Apple Push Notification service. On Android, they are delivered through Firebase Cloud Messaging, which is run by Google. Notifications are optional, and Duz works without them.
How we measure whether Duz is working
Duz does not use third-party analytics or advertising tools, and it sets no tracking cookies.
We look at how Duz is used through the records the service already keeps to work, for example how many people joined, arrived at or completed a Duz. We use them only in aggregate, to understand whether Duz works and to improve it. We also keep technical logs of errors, latency and service health.
If we ever introduce an analytics provider, we will update this policy first and ask for your consent where the law requires it.
3. How we use your information
We use personal information to:
- create and secure your account, and verify that you are a student;
- recover your account if you ask us to;
- sign you in and keep you signed in;
- show you the Duzes and Quests available to you, and let you join and take part;
- create temporary crews and parties;
- verify check-ins and Quest requirements, and work out participation and completion;
- award and show badges and points, and run individual and college standings;
- send you event, safety, operational and reward updates;
- prevent cheating, fraud and abuse;
- investigate technical problems, and respond to support requests and disputes;
- keep the service secure and reliable, with appropriate audit records;
- understand whether Duz works, and improve it;
- comply with the law and enforce our terms.
We will not take information collected for one purpose and quietly use it for a substantially different one.
4. Our lawful bases
UK data protection law requires a lawful reason for each use of personal information.
Performance of our contract with you
Most of what we do is necessary to provide Duz once you choose to use it:
- your account and Durham verification;
- joining and taking part in Duzes, and Quest progress;
- recording badges and points, and your Passport;
- account recovery you request;
- core service and event information.
Legitimate interests
We rely on our legitimate interests, where necessary and proportionate, to:
- protect accounts and the platform;
- prevent fraud, cheating and abuse;
- keep appropriate audit records and diagnose technical failures;
- protect the integrity of rewards and college standings;
- measure and improve Duz's reliability, and keep aggregate statistics.
Before we rely on legitimate interests, we weigh the impact on your rights and reasonable expectations.
Consent
We ask for consent where it is the right basis, for example before your device shares your location or allows notifications. Consent is never bundled into our terms. If you say no, you can still use the parts of Duz that don't depend on it, and you can withdraw consent at any time.
Legal obligations
We may process or keep information where the law requires it, to respond to valid legal process, or to establish or defend legal claims.
5. Location privacy
Location deserves its own explanation.
Duz is not a background location tracker. When you check in somewhere that needs it, Duz asks your device for your current position and its accuracy, and uses them to decide whether the check-in is genuine.
We never use your location:
- for advertising;
- to sell information about where you go;
- to follow you around Durham;
- to build a profile of your movements;
- just because you have Duz installed.
6. Communications and notifications
We send service and event messages about things you've chosen to take part in, such as:
- cancellations, changed instructions and venue changes;
- live updates during a Duz;
- account-security notices and reward confirmations.
Duz does not currently send promotional messages. If we start, we will ask you to opt in separately, and turning them off will never affect security or essential messages.
You can turn off push notifications in your device settings at any time.
7. Who we share information with
We do not sell your personal information, and we do not run advertising.
Service providers
We use these suppliers to run Duz. Each processes information only to provide its service to us.
| Supplier | What it does for Duz | Where |
|---|---|---|
| Railway | Hosts the Duz service and its databases | Servers in the EU; Railway is a US company |
| Postmark (ActiveCampaign) | Sends sign-in codes and account emails | United States |
| Apple (Apple Push Notification service) | Delivers notifications to iPhones, if you turn them on | United States |
| Google (Firebase Cloud Messaging) | Delivers notifications to Android devices, if you turn them on | United States |
| GitHub | Hosts this website | United States |
| Namecheap | Runs our domain and forwards emails sent to our addresses | United States |
| Slack | Receives our internal operational alerts | United States |
Duz administrators and authorised hosts
Authorised members of the Duz team and event hosts can see the information they need to run events, handle support, investigate disputes, prevent abuse, make authorised corrections and keep the service running. Access is limited by role, and sensitive administrative actions are recorded.
Other Duz users
Other users can see limited information where a feature needs it:
- standings;
- your temporary crew or party for a Duz;
- badges you choose to share.
We never show your Durham or recovery email to other users.
Legal requirements
We may disclose information where reasonably necessary to comply with the law, enforce legal rights, protect people from serious harm, or respond to valid legal process.
Durham University
Verifying with your Durham email does not give Durham University access to your Duz participation, location, Quests, Passport or points. We do not give the University this information just because you verified with a Durham address.
8. AI services
Duz does not send your personal information to third-party AI services. If we ever introduce a feature that would, we'll tell you first what would be sent, to whom and why, and ask for your permission where that's required.
9. International transfers
Some of our suppliers process information outside the UK, as the table in section 7 shows. When personal information is transferred internationally, we rely on a transfer mechanism recognised under UK data protection law, together with appropriate contractual and technical safeguards.
10. How long we keep information
We don't keep identifiable information just because we can. We keep it only as long as it's needed for its purpose, taking into account:
- whether your account is still active;
- whether a Duz feature needs it;
- security and fraud prevention;
- disputes and audit;
- the integrity of badges, points and standings;
- the law.
For example:
- Account information is kept while your account exists.
- Push tokens are kept only while they're needed to reach your device.
- Sign-in codes and session secrets are short-lived.
- Raw location and device evidence from check-ins is kept only as long as it's needed for verification, security or disputes, and it is deleted when you delete your account.
- Internal system messages are kept for 7 days. Records of failed deliveries are kept for 30 days, and operational records for 90 days.
- Security and audit records may be kept longer where needed to investigate abuse or establish what happened.
- Anonymous or aggregate statistics may be kept, because they no longer identify you.
11. Deleting your account
You can delete your account from within Duz.
When you do:
- Your account enters deletion and all your sessions are signed out immediately.
- Each part of Duz deletes the personal information it no longer has a reason to keep.
- Records that must remain for aggregate, audit or integrity reasons are anonymised, so they're no longer linked to you.
- Your account is finally removed once every part of Duz has confirmed its deletion.
For example:
- your Durham and recovery email addresses are removed;
- push tokens and identifiable device information are deleted;
- raw GPS and identifiable check-in evidence are deleted;
- historical check-in counts, Duz participation, badge records and points transactions may remain in anonymised form, so badge rarity and past standings stay accurate.
We never use a deletion request as an excuse to keep a hidden copy of your identity.
12. Your privacy rights
Under UK data protection law, you may have the right to:
- access the personal information we hold about you, and receive a copy of it;
- correct inaccurate information;
- ask us to delete it;
- restrict certain processing, or object to processing based on legitimate interests;
- withdraw consent where we rely on it;
- data portability, where it applies;
- complain to a data protection regulator.
Withdrawing consent doesn't make earlier processing unlawful, but we will stop the consent-based processing from then on.
To exercise a right, email armaan@duz.events or use the controls in Duz (see your privacy choices). We may need to confirm the request comes from you before we share or change anything.
You can also complain to the UK Information Commissioner's Office (ICO) at ico.org.uk.
13. Security
We protect personal information with technical and organisational measures, including:
- short-lived sign-in credentials, token rotation and revocation;
- restricted administrative access;
- separation between the parts of the service and their data;
- encryption in transit;
- separate test and live environments;
- audit logging, rate limiting, monitoring and alerting;
- protection against replayed and duplicate requests.
No internet service can guarantee absolute security, but privacy and security are part of how Duz is designed, not something added afterwards.
15. Changes to this policy
We may update this policy as Duz changes. If a change materially affects how we use personal information, we will tell you, and ask for new consent where required, before the new processing begins.
The current version and its date are always at https://www.duz.events/privacy-policy.
16. Contact
Send questions, privacy requests or complaints to armaan@duz.events.