Privacy
Privacy Policy
This policy explains which personal data is processed when Studiume is used, where it comes from, why it is needed and how to exercise your rights. Acknowledging this policy is not blanket consent to every form of data processing.
Tutor pilot application
When a tutor chooses to submit a pilot application from the public page, Studiume receives their name, Telegram handle or email, approximate learner count, selected workflow, optional comment, page language, referrer domain and sanitized UTM source, medium and campaign. Do not include learner personal data in the comment. The name, contact and comment are encrypted at rest.
These data are used only to reply to the application, arrange and run the pilot, and assess the application source. They do not create an account, subscription or payment and are not linked to the anonymous analytics session identifier. The application is retained for up to 365 days and then automatically deleted. The record includes the consent date and the version of this policy.
Scope and operator
This policy applies to the public website, the Studiume application and related support communications. Studiume is the name of the service. The service operator is ФОП Ярмолюк Сергій Петрович, a Ukrainian sole proprietor.
The operator’s postal address and Ukrainian taxpayer number will be added before public registration opens. Until then, the application remains a controlled beta with restricted access. Privacy requests are already accepted at hello@studiume.com.
Data and its sources
Account data includes name, email or login, language, avatar, role and technical identifiers. If a user chooses Google sign-in, it also includes the stable Google account identifier, Google-verified email address and basic profile name. Learning data includes projects and workspaces, invitations, groups, calendar entries, lessons, attendance, materials, files, assignments, responses, quizzes, grades, progress and messages. If the optional AI assistant is separately available to a user, its messages, generated responses and the limited context needed for the requested guidance or action are also processed.
The public website creates minimized events for views of allowlisted pages, clicks on primary actions and navigation, and FAQ openings. An event contains a random per-tab identifier stored by the server only as an HMAC hash, an allowlisted event and target, page path, language, referrer domain and explicitly supplied UTM source, medium and campaign. A raw analytics event does not include an IP address, user agent, email, account ID, Project names, entered text or page content.
If a visitor follows a tagged registration action and creates a new account, the application sends the server an opaque per-tab UUID. The server verifies it against its own events and stores separate first-party account attribution containing the initial path and language, referrer domain, sanitized UTM source, medium and campaign, selected action, registration method and time. Arbitrary URL parameters, the raw UUID, session hash, IP address and user agent are not included. No attribution is created when there is no matching event or when the browser sends Global Privacy Control or Do Not Track.
Data may come from the user, their legal representative, a tutor, an institution or another authorized workspace participant, and for user-selected Google sign-in, from Google. Authentication, security and error logs, network address, browser data and records of legal-document acceptance may also be created automatically while the service operates. Studiume does not use advertising or cross-site trackers.
Purposes and legal grounds
Data is processed to create and protect accounts, perform these Terms, provide selected learning functions, communicate, provide support, prevent abuse, diagnose errors, restore backups, understand use of the public website and core functions, and comply with law.
Minimized product analytics and bounded first-party registration attribution are processed in Studiume’s legitimate interest in measuring visits, traffic sources, conversion and interface usefulness and improving the beta without advertising profiles or cross-site tracking. Depending on the situation, other processing is based on performing arrangements with the user, complying with a legal obligation, protecting legitimate interests in service security and stability, or consent where consent is actually required. Acceptance of the Terms and acknowledgement of this policy do not replace separate consent where the law requires it.
Tutors, schools and learning workspaces
Studiume determines the purposes and means of processing account, security and platform-operation data. A tutor or institution decides which learners to invite and which learning records to add to its workspace, and must have appropriate authority and a lawful basis to do so.
For an institutional pilot, responsibilities for learner data, retention, data-subject requests and deletion must be set out in a separate agreement or data-processing terms. This public policy does not replace that agreement or transfer Studiume’s own obligations to the user.
Minors
If a user cannot lawfully agree to the processing of their data independently, the involvement or valid consent of their legal representative is required. An institution may separately arrange access and enter a minor’s learning records only where it has appropriate authority and a lawful basis; an invitation or data entry by an institution does not by itself amount to accepting personal Terms or giving consent on behalf of the child or representative.
Tutors and institutions must not add excessive data about children. Until a separate public entry path for minors is launched, Studiume uses only controlled flows involving a legal representative, an invitation or a separately approved institutional pilot.
Access and providers
Learning-workspace users can access data only within their granted permissions. Limited technical access may be available to personnel who need it for support, security or service recovery.
Studiume uses Hetzner, including encrypted off-site backups, Resend for transactional email, Zoho Mail to receive and retain inbound messages sent to hello@studiume.com, and GitLab Integrated Error Tracking for diagnosing failures. Error monitoring is configured without user profiles, request bodies, cookies or user-action logging.
At the user’s choice, Google OAuth may be used for sign-in. Studiume requests only the openid, email and profile scopes. Google returns the stable account identifier, verified email address and basic profile data; Studiume uses the name but does not copy the profile image or other optional profile fields into the external identity record. Studiume stores the link to that identifier, an email snapshot and usage timestamps, but does not store Google OAuth access or refresh tokens and does not receive access to Google Drive, Calendar or email.
A user may optionally connect the Telegram Bot API for selected notifications. In that case, Studiume stores an encrypted Telegram chat identifier and label plus technical delivery status, while Telegram receives the notification title, short body and link selected by the user. The channel can be disabled or disconnected in settings.
The optional AI assistant uses the OpenAI API. After the user separately acknowledges this policy, OpenAI receives the entered message and the minimum context required within current permissions and generates a response. Under current settings, Studiume does not opt in to voluntary use of API data for model training. Responses API requests use store: false, which disables response-state storage for that request but does not eliminate abuse-monitoring logs or other technically necessary processing. Under OpenAI’s standard controls, some messages, responses and related metadata may be retained in such logs for up to 30 days, and longer where required by law or reasonably necessary to protect services or a third party from harm. Engaged providers receive from Studiume only the data necessary for the stated function and process it under applicable agreements, data-processing terms and law. Where a provider independently determines separate purposes and means of processing, its privacy policy also applies to that processing. Processing may take place outside the user’s country.
Browser storage
The application stores a sign-in token, selected language, current learning workspace and onboarding markers in the browser. This is necessary for authentication and interface operation.
The public website stores a random per-tab analytics session identifier in sessionStorage and, when present in the URL, sanitized UTM parameters. These values exist only within that browser tab. UTM parameters may be included in a voluntarily submitted pilot application. When a registration action is followed, the identifier is added to the application address, stored there temporarily in sessionStorage and used only for verified first-party attribution of a new account. Analytics collection and identifier transfer are skipped when the browser sends Global Privacy Control or Do Not Track. Advertising and analytics cookies are not used.
Retention
Core data is retained while an account or learning workspace is active and afterwards only for as long as needed for legal requirements, security, handling requests or preserving learning-record integrity. Data removed from the working system may temporarily remain in protected backups and is not used for ordinary operations.
IP addresses from successful registration, sign-in, email verification and password reset are stored in encrypted form for up to 90 days for account protection, abuse investigation and technical support. The full history is available only to a restricted set of platform administrators and is automatically deleted when the retention period ends.
The link between a Studiume account and a Google identifier is retained while the account is active or as needed for security and legal requirements. A one-time sign-in completion ticket is valid for 10 minutes; after successful sign-in, the Google profile data in it is erased immediately, while unused attempts and limited technical records of consumed attempts are removed by scheduled daily cleanup.
Raw minimized public-site analytics events are deleted after 180 days. Verified first-party registration attribution is retained for up to 730 days after registration or less if the account is deleted earlier. The administrative report does not expose UUIDs or session hashes. Product-usage metrics are calculated from current Studiume domain records and do not create a separate analytics copy with another retention period.
AI assistant message, response and proposed-action content is removed from the operational database no later than 30 days after the session closes or expires. Hashes, statuses, usage accounting and a limited technical trace without the full text may be kept longer for security, dispute handling and cost control. OpenAI-side processing is described in the provider section.
Specific retention periods for other technical logs, backups and particular learning records must be finalized before public opening. Until then, the minimum-necessary retention principle applies, taking account of recovery needs and legal restrictions.
Your rights
You may request information about processing, access, correction, restriction, objection, withdrawal of consent where given, or deletion through the Contact page. Identity and representative authority may need to be verified before a request is fulfilled.
Some records cannot be deleted immediately where retention is required by law, the rights of other participants or academic-record integrity. This does not remove the right to contact a competent authority or court.
Security and incidents
Studiume uses access separation, transport encryption, backups and technical monitoring. Absolute security cannot be guaranteed for an online system, but this does not remove the duty to apply appropriate safeguards.
Where an incident requires notification under applicable law, affected users or the competent authority will be notified as required.
Changes and contact
A material policy change receives a new version and effective date. Where new consent or another confirmation is required, it is not treated as given automatically.
Privacy requests: hello@studiume.com.