YOUR DATA
Privacy Policy
What Botuni uses, where your university session goes, and the choices you have.
Last updated: 2026-11-15
1. Who is responsible
Botuni is operated by Ivan Diulher. The operator is responsible for personal data processed to provide Botuni.
Contact: dulgervanya@gmail.com
2. Data we use and why
Account data includes your email, a hash of your Botuni password, app authentication records and account identifiers. This supports your app account and protects access. University passwords and authenticator setup keys are never sent to Botuni’s server in readable form. The optional on-device authenticator stores setup keys, account labels and website mappings in native secure storage. Saved university logins and authenticator accounts are kept in account-scoped secure storage on your device, available only to the Botuni account that owns them. Browser integration transfers only a selected 2FA authenticator; university usernames and passwords are not transferred to the browser.
Registration data includes course and group selections, scheduled times, execution mode, readiness, outcomes and safe diagnostic timestamps. New Lite trials are offered through Apple or Google subscriptions to eligible subscribers: one month free, then EUR 3.99 per month in EUR storefronts, with localized prices in other currencies. The store shows eligibility, price and renewal terms before purchase. Trials renew into paid subscriptions unless cancelled under the store terms. Legacy in-app Lite grants remain valid only until their original expiry and do not renew. Their claim ledger retains account / installation UUIDs and activation / expiry dates to prevent repeated grants, like the introductory credit ledger. Device or installation identifiers link jobs to the right phone, support session synchronization and prevent repeated introductory credit and Lite free-month claims.
Purchases may involve store transaction identifiers, encrypted purchase tokens, entitlements, credit reservations and subscription status. Apple or Google handles payment details; Botuni does not receive your full payment-card number.
If you enable notifications, Botuni processes your push token and delivery status through Expo and platform push services. Notifications include registration and account-readiness updates and probable new coursework alerts. Safe session observations record status and freshness, not cookie contents.
When you submit the support form, we store your email address, message, submission and update times, and an internal ticket status so we can review and answer your request. You do not need an account. The form does not verify your email address; a message alone does not establish account ownership. Replies are handled by the operator through email. If you request support for another university, we store its name and link the request to your Botuni account to review demand and contact you about availability. Service requests may involve IP addresses and technical request information for security, throttling and infrastructure operation. Please never send passwords, MFA codes, university cookies or session tokens to support.
During ordinary foreground TUWEL course synchronization, Botuni sends your enrolled course identifiers, course types and titles to its server. When your phone detects a newly visible activity after its first complete course read, it sends a course-level signal and observation time, authenticated with your Botuni account. Activity identifiers and names, descriptions, grades and university cookies are not included. Other enrolled users may receive a probable-new-work alert displaying the course type and title; they do not receive your identity. Signals for one course are grouped for thirty minutes. Coursework memberships expire after sixty days without refresh; disconnecting TUWEL requests removal, and account deletion removes them. Membership cleanup requires the configured maintenance worker.
Forum posts, replies and files
When you use the forum, we process your forum username, account identifier, posts and replies, reply targets, votes, joined subject discussions, notification preferences, reports and author blocks. Uploaded photographs, voice recordings and documents include file metadata such as format, size and, where applicable, recording duration. We store forum records in the application database and attachments in Cloudflare R2. Authorized participants in the relevant university discussion can see your username, posts, replies and attachments. Your account email is not published as a separate forum field; text, usernames and files you choose to post may themselves reveal personal information. Forum content is not end-to-end encrypted: the service and authorized moderators can process it. Do not post credentials, verification codes or another person's private information.
To personalize For you, requests can include your subject identifiers and upcoming exam dates within the next two weeks. Ranking also uses joined discussions, recent positive votes, recency and engagement. This provides relevant study discussions, not advertising. We process reports, blocks and moderation records to address abuse. Hiding a post on your device only changes your own view; it does not delete the publication for other users. Recipients may copy, share or save content they can access, and Botuni cannot erase those independent copies.
Photographs may first be available as uploaded while a background worker converts them to an optimized format; after successful replacement the original is scheduled for removal. A failed conversion may leave the original available. Temporary attachment download links may remain usable until they expire. Forum and reply notifications are optional and can be controlled per discussion and in notification settings.
3. University authentication and session handling
Manual sign-in takes place in the university login interface. If you separately enable automatic sign-in on the phone, its saved login and verification code are sent directly to the university. The resulting TISS session is normally kept in secure storage on your phone. Routine mobile validation goes directly from your phone to TISS.
Local Mode uses your phone for registration. Standard Server Mode can store a valid encrypted session copy temporarily so an authorized registration can run when the phone is unavailable. In Private Server Mode, the backend requests a job-bound temporary copy near registration and deletes it when it is no longer needed, subject to bounded reconciliation and expiry cleanup. Server copies have a maximum configured lifetime of 24 hours; Private copies use a shorter, job-bound window.
University sites and identity providers process your authentication under their own privacy notices. Botuni cannot access unrelated Safari or Chrome sessions or password-manager secrets.
Desktop Chrome AutoFill and Secure Storage
Authenticator account management, manual code copying, device protection and on-device automatic TU Wien sign-in are free. Optional desktop Chrome AutoFill requires Botuni on your phone and an active Lite or Pro subscription. You choose one TOTP authenticator and confirm its transfer. University usernames and passwords are not transferred to the extension. Account identifiers, display names, authenticator labels and website mappings accompany the selected authenticator; labels may contain an email address.
The phone encrypts the selected account before sending it through the Botuni relay. The transfer key is included in the extension QR and is not sent to the relay. The extension stores an encrypted vault in Chrome local storage and temporary unlock material in Chrome session storage, not Chrome Sync. The relay temporarily processes encrypted transfer data; the backend stores connection metadata, token hashes, subscription access and, in browser-storage modes, an encrypted server key share. A server share alone cannot decrypt the authenticator.
Automatic unlock retains a local share that can request the server share online. A copied browser profile may therefore unlock the vault while its connection is active. Passkey mode encrypts the local share using WebAuthn PRF and requires user verification once per browser session or after Lock; the browser chooses the passkey provider, which may synchronize the passkey through its own account. A compatible PRF authenticator is required. The extension recovery password is processed locally and provides another way to unlock the vault; its strength matters even when a passkey is configured. The connection is rechecked when its fifteen-minute unlock lease expires; the passkey-unlocked client share can remain in session memory until Lock or the browser session ends.
If you choose System storage and a compatible utility is available, the extension transfers the account and its vault key to that separately installed local utility through Chrome Native Messaging. After verifying the system copy, it removes its browser vault and retires the browser server-share capability. macOS uses Keychain; Windows uses user-scoped DPAPI. During normal filling the utility returns current verification codes and account metadata, not the TOTP setup key. This protects storage but does not isolate it from malware controlling your unlocked account or a compromised extension. Availability of public utilities is shown on the download page; a described storage mode does not mean an installer is already released for every platform.
To decide where to fill, the extension processes the current supported TU Wien login URL, form destination, verification-code input and local input, focus and submit events. It keeps limited tab/document identifiers and submission-expiry metadata in session storage to avoid overwriting manual input and reusing a submitted code. It does not send those page contents or a general browsing history to Botuni, collect keystroke contents for analytics, or automatically submit the form. A URL may contain university sign-in state, so it is handled as authentication-related browsing data. The native utility may receive the supported page URL to verify that filling is allowed. A code inserted into a page is accessible to that page's scripts.
Subscription checks return entitlement status, not payment-card details or transaction history, to the extension. Public website/API infrastructure processes IP addresses and technical requests for delivery, security and rate limiting; the extension does not request GPS location. Botuni uses Chrome extension data only to provide and secure the disclosed features, in accordance with the Chrome Web Store User Data Policy, including Limited Use. It is not sold or used for advertising or creditworthiness decisions. Transfers are limited to the providers needed for the service and applicable legal or security requirements; human access is limited to policy-permitted circumstances, such as your explicit consent for support or legally required access.
Lock clears the extension's unlock material and locks the system record when applicable. Disconnect attempts both server revocation and local deletion; offline or failed cleanup remains pending and can be retried. Revocation is detected on the next connection check and cannot erase a TOTP seed already copied. If a seed is exposed, replace it at the university. Uninstalling the extension alone is not a confirmed server revocation or deletion of the separately installed utility. Reconnecting your phone is required to move from system storage back to browser storage.
Device authentication can protect the authenticator. Allowing background sign-in creates a separate device-encrypted copy of the selected login and key that can be used without a biometric prompt after the first device unlock; this requires a separate in-app choice. Turning off automatic sign-in or signing out removes that background copy. QR scanning is performed on the phone without uploading the image or setup key.
4. Legal bases
Account operation, forum publication and delivery, discussion personalization, your requested registration workflow and purchase management rely on performance of the service contract, Article 6(1)(b) GDPR. Security, forum abuse prevention and moderation, authentication throttling and prevention of duplicate introductory benefits rely on legitimate interests under Article 6(1)(f): protecting accounts and the service from misuse. Records required by applicable law rely on Article 6(1)(c). Optional notifications rely on your choice and, where consent is required, Article 6(1)(a). You can disable them in the app or device settings.
Support necessary to provide your requested service relies on Article 6(1)(b); handling general enquiries relies on Article 6(1)(f), our legitimate interest in answering questions about Botuni. Without required account and registration information, Botuni cannot provide the corresponding features. Optional notifications are not required to use the app. Botuni does not use your information for advertising profiles or automated decisions with legal or similarly significant effects.
Community timetable times
Your personal timetable time changes stay in the calendar on your phone. To look up suggestions, Botuni receives the course, semester, weekday, scheduled start/end and room for eligible blocks in the visible week. Optional community reports require a separate choice for each submission, based on consent under Article 6(1)(a) GDPR. We store a hash identifying the timetable group, the start and end shifts, your account ID to count one current report per person, the consent notice version and timestamp. Reports expire after 90 days or at the end of that semester, whichever is earlier, and are deleted by maintenance. Others receive only combined suggestions supported by at least three other accounts. Names, notes, subscription links and your full timetable are not included in reports. Withdraw and delete your reports through Calendar → Filters → Remove my time reports; this leaves your personal changes intact. Account deletion also removes these reports. Existing backups follow their own retention. Suggestions never change your timetable automatically and are not university-confirmed corrections.
5. Recipients and processing locations
The operator uses the following providers and systems to deliver Botuni. A provider receives the information needed for the feature you use; using the public support form does not require an Apple, Google or university sign-in.
- Hetzner — application hosting and storage. The Botuni API and database run on a Hetzner virtual server in Falkenstein, Germany. This infrastructure stores account and registration records, support tickets and, when Server Mode is used, encrypted university-session copies. See Hetzner’s privacy information.
- Cloudflare R2 — forum attachments. R2 stores uploaded photographs, voice recordings, documents and optimized photos. Cloudflare processes attachment content and request information needed for storage and delivery. A storage region restricted to one country is not promised; Cloudflare processing and international transfer arrangements are described in its notices below.
- Cloudflare — website/API delivery and security. Public website and API traffic passes through Cloudflare before reaching the server. Cloudflare processes connection and request information, including IP addresses, requested URLs, headers and traffic content needed to proxy HTTPS requests, which can include support submissions. Cloudflare’s network operates internationally. See its Privacy Policy and Data Processing Addendum.
- Expo, Apple APNs and Google FCM — optional push notifications. When notifications are enabled, delivery uses push tokens, notification text and event metadata such as account, device or registration identifiers, depending on the notification. University passwords, MFA responses and session cookies are not included in these payloads. See Expo’s Privacy Policy.
- Apple and Google — sign-in and purchases. If you use their sign-in methods, these providers handle authentication and supply the identity information needed to establish your Botuni account. If you make a store purchase, the store handles payment and Botuni verifies transaction and entitlement information. Their own privacy notices apply to their services: Apple and Google.
- TU Wien / TISS — university access and registrations. TISS and the university’s identity systems receive the authenticated requests needed for your chosen registration workflow. In Local Mode these requests originate from your phone; in Server Mode they can originate from the Botuni server. University authentication and university records are governed by the university’s own privacy information.
- Google Gmail and your email provider — support correspondence. The support form first saves your request in Botuni’s database. If the operator replies by email, your email address and the correspondence are processed through the operator’s Google Gmail account (dulgervanya@gmail.com) and your own email provider. Google’s Privacy Policy describes its processing of Gmail data. The form itself does not automatically send an email.
The public website does not load third-party analytics, advertising scripts or fonts and does not itself set cookies. Cloudflare security features may set essential security cookies. The private administration area uses authentication cookies and is restricted to the operator; its Cloudflare Access sign-in is separate from the public support form.
Hosting the application database in one country does not restrict all processing to that country. International providers may process information outside the European Economic Area. The linked provider notices describe their processing and transfer arrangements. Contact dulgervanya@gmail.com for information about the safeguards applicable to your data or to request a copy where available.
6. Retention and deletion
Forum publications remain available until you delete them, delete your account, or they are removed by moderation. Deleting your own post clears its text and hides its attachments from normal forum access; a structural record can remain to preserve reply relationships. Account deletion clears your authored text and removes account-linked forum records through the account deletion process. R2 object removal is asynchronous, depends on maintenance workers and only selects objects older than one day. Attachments retained as evidence for an unresolved moderation report can be kept until that review is resolved; deleted-account attachments are reclaimed by cleanup. Abandoned uploads are also reclaimed by maintenance. Existing backups and copies saved by other participants are not immediately erased. Contact Support about content or evidence retained for moderation.
Authenticator setup keys and saved university logins are stored locally in secure storage scoped to the owning Botuni account. Signing in to a different Botuni account does not transfer or expose those secrets. The Botuni server does not back up your authenticator keys in readable form, and deleting a server account does not constitute a secure erase of every device copy. Save recovery codes or export the authenticator accounts before deleting your Botuni account, replacing or resetting the phone; do not rely on a newly created account recovering the old account's local secrets. Account deletion disables paid integrations and removes the optional background sign-in copy when deletion completes in the app.
Chrome transfer ciphertext is removed from the live database when the browser acknowledges receipt; an unclaimed transfer expires after five minutes and is removed by cleanup. Connection grants remain until disconnected or account deletion and can be revoked from the phone; revoked metadata are removed by cleanup. Subscription eligibility is cached until its expiry. Connection revocation is checked separately with a maximum fifteen-minute client unlock lease. Further filling stops if that lease expires and the server cannot be reached. Revocation is detected at the next connection check; it cannot erase previously copied data. Disconnecting cannot remotely erase a previously copied key on another computer. Remove the local connection there, or rotate the university key and password if the computer is no longer trusted.
University session copies expire and are wiped through the session lifecycle and maintenance tasks. Notification delivery records are scheduled for deletion after seven days. Expired app authentication and throttle records are cleaned by maintenance. These cleanup processes depend on the configured workers running.
Account and registration history, purchase records and identifiers needed to prevent repeated introductory credit claims can have different retention needs. The introductory-claim record is designed to survive account deletion; deletion does not automatically make the same installation eligible again. Closed support tickets are scheduled for permanent deletion from the live database 14 days after their most recent closure. Reopening a ticket cancels that countdown; closing it again starts a new 14-day period. Open tickets remain available while the request is being handled. This cleanup requires the maintenance tasks to run and does not automatically remove email correspondence or existing backups. Support tickets are stored separately from accounts and are not automatically removed when an account is deleted. You can request their deletion through Support; we verify requests where needed and assess any applicable retention obligations. Live database deletion does not immediately erase existing backups.
You can delete your account from Profile → Delete account in the app, or request deletion without the app. Visit Delete your account. Required financial, legal or anti-abuse records may be retained where there is a lawful basis; the response to your request explains any applicable exceptions.
7. Your rights
Subject to the GDPR conditions, you can request access, correction, erasure, restriction, portability and object to processing based on legitimate interests. You can withdraw consent for optional processing without affecting its prior lawfulness. Use our support form or dulgervanya@gmail.com and identify the request as concerning Botuni.
You may complain to your competent supervisory authority, including the Austrian Data Protection Authority. We may need to verify account ownership before fulfilling a request; we will not ask for university credentials.
8. Security, eligibility and updates
Botuni uses authenticated account and device access, hashed app passwords, secure native storage, encrypted backend university-session storage and HTTPS for production session transfers. No security measure can eliminate every risk. Botuni is intended for people eligible to use the relevant university systems; minors must have any permission required by applicable law.
Material changes to this notice will be communicated through the service or another appropriate channel. The date above identifies the current version.