← studiyo
Rolit Privacy Policy
한국어 · English · 日本語 · 简体中文
Effective date: October 7, 2026
This is a translation of the Korean original. If anything differs, the Korean version prevails.
The developer who operates Rolit (the "Service"; the "Operator") treats users' personal information with care and complies with applicable laws. This Privacy Policy explains what information the Service collects, how it is used and retained, and what rights you have.
1. Personal information we collect
The Service creates accounts and collects information in the following ways, without a separate sign-up procedure.
1.1 Account information
- Guest (anonymous) use: If you choose "Start as guest" in the app, a random unique identifier (UID) is issued automatically through Firebase Authentication, with no input required.
- Sign in with Apple (iOS): If you optionally use "Sign in with Apple", we may collect the user identifier provided by Apple and, if you agree to share them (only the first time), your name and email address. The email may be a relay address provided through Apple's "Hide My Email".
- Sign in with Google (Android): If you optionally use "Sign in with Google", we may collect the unique identifier of your Google account, name and email address.
1.2 Information generated while using the Service
- Project information: goals, deadlines, participant list, invite codes
- Task information: title, details, progress status, assignee, attachments (if you upload them yourself)
- Profile information: display name (nickname) and self-introductory information you enter yourself, such as "what I'm good at"
- Device token (FCM token) used to send push notifications
- Document files: PDF and image files you choose and upload when creating a new project. The contents are used only to create the project name and task list and are not stored on the Service's servers. However, they are sent to an AI (Google Gemini API) for analysis (see Section 2). Please make sure files do not contain personal information.
1.3 Information collected automatically
The Service includes the Meta Platforms (Facebook) SDK to measure ad performance. While you use the app, the following information may be sent to Meta.
- Basic events such as app install and launch
- Service usage events: figures such as whether you created a project, whether you created tasks with AI, and the number and creation method of tasks. Names and contents of projects or tasks are not included.
- Device and app information: device model, OS and app version, language settings, and the IP address associated with network requests
- Advertising identifier: On iOS, the app is configured not to collect the advertising identifier (IDFA). On Android, if the device has a Google advertising ID, the Meta SDK may collect and send it; you can delete or reset the advertising ID in your device's ad settings.
The Service does not currently show ads inside the app. Information sent to Meta is processed under Meta's privacy policy.
2. Purposes of collection and use
Collected information is used only for the following purposes.
- Identifying users and keeping you signed in
- Storing project and task data and real-time synchronization between participants
- Using AI (Google Gemini API) to generate task plans, analyze uploaded documents, assign tasks, detect uneven workload distribution and duplicate tasks, and judge whether deadlines are approaching
— In this process, the project goal, task titles and contents, participants' names (nicknames), self-introductory information (strengths, etc.) and progress, and the contents of documents (PDF/images) you upload are sent along when the AI model is called. - Sending push notifications (task completed/assigned, participant joined, deadline approaching)
- Measuring ad performance (Meta SDK, see Section 1.3)
- Responding to errors and handling inquiries
3. Provision to third parties and outsourced processing
As a rule, the Service does not sell your personal information. However, to operate the Service, data processing is outsourced to, or information is sent to, the following external companies.
| Company | Task | Information processed |
|---|
| Google (Firebase: Authentication, Firestore, Cloud Functions, Cloud Storage, Cloud Messaging / Google Sign-In) | Sign-in, data storage and synchronization, server logic, attachment storage, push notifications | Account identifier (name and email when using Google Sign-In), project and task data, device push token |
| Google (Gemini API) | AI features: task generation, document analysis, assignment, checks | Project goal, task titles and contents, participants' names, self-introductory information and progress, contents of uploaded documents |
| Apple (Sign in with Apple) | Sign-in authentication through an Apple account | Apple user identifier, name and email (if you consent to share) |
| Meta Platforms (Facebook SDK) | Ad performance measurement | App install/launch and usage events (excluding contents), device and app information, (Android) advertising ID |
These companies process information under their own privacy policies and security standards.
4. Retention and use period
- When you "Leave" a project, your participation information is deleted and tasks you were responsible for become unassigned. When the project host deletes a project, its tasks and participant information are deleted. Attachments uploaded to a project may remain in storage separately; to have them deleted, request it through [10. Contact].
- Account deletion: You can delete your account yourself from [Account deletion] at the bottom of the [My] tab in the app. Deleting removes your sign-in account, push notification token and project participation information. Projects you used alone as host are deleted entirely, including tasks, attachments and invite codes; projects with other participants remain, and the host role passes to the participant who joined first. Deletion cannot be undone. If you cannot access the app, request deletion through [10. Contact] and we will process it without delay.
- Deleted information may remain for a period in backups and logs of service providers (such as Google) and is deleted under those providers' policies.
- Retention and deletion of information sent to Meta follow Meta's privacy policy.
- If any information must be retained under applicable laws, it is stored separately only for the period required by those laws and then destroyed.
5. Procedure and method of destruction
Personal information whose retention period has passed or whose purpose has been fulfilled is destroyed without delay. Information stored as electronic files is deleted using technical methods that make recovery impossible.
6. Your rights and how to exercise them
You may exercise the following rights at any time.
- Request access to, correction of, or deletion of your personal information
- Request suspension of processing
- Delete your entire account (withdraw) — you can do this in the app or by request
You can edit your profile information (name and strengths) in the app, and delete your account from the [My] tab. For other requests, contact us by email at [10. Contact]; the Operator will act within the period set by applicable law.
7. Children's personal information
The Service is not mainly directed at children under 14, and we do not intentionally collect personal information from children. If we learn that personal information of a child under 14 has been collected, we will destroy it without delay.
8. Security measures
- Access is controlled on the server side through Firestore security rules so that users can access only the data of projects they belong to.
- All data is transmitted over encrypted communication (HTTPS/TLS).
- Sensitive credentials such as AI API keys are stored and used only on the server (Cloud Functions), not in the client.
9. Transfer of personal information abroad
To provide the Service, personal information is transferred to, processed in, or stored in other countries as follows. The project and task database (Firestore) and server logic (Cloud Functions) operate in the Republic of Korea (Seoul) region, while authentication and push notifications (Authentication, Cloud Messaging) are processed on Google's global infrastructure.
| Recipient | Country | Items | Purpose | Timing and method |
|---|
| Google LLC (Firebase Cloud Storage) | United States (US East region) | Attachments you upload | Storing attachments | Sent over encrypted communication when you attach; kept until deleted |
| Google LLC (Gemini API) | United States and other Google infrastructure | Project goal, task titles and contents, participants' names, self-introductory information and progress, contents of uploaded documents | Providing AI features | Sent over encrypted communication when you use AI features; not stored separately by the Service |
| Meta Platforms, Inc. | United States and others | App install/launch and usage events (excluding contents), device and app information, (Android) advertising ID | Ad performance measurement | Sent automatically while using the app; retention follows Meta's policy |
If you do not want your information transferred abroad, you may stop using the relevant feature or delete your account. For other inquiries, contact us at [10. Contact].
10. Contact
For privacy-related inquiries and requests for access, correction or deletion, please contact us below.
11. Changes to this Privacy Policy
This policy may be revised due to changes in laws, policies or the Service, and we will notify you of changes through an in-app notice or by updating this document.
- Announcement date: October 7, 2026
- Effective date: October 7, 2026
Revision history
- October 7, 2026: Reflected use of the Meta (Facebook) SDK, Google Sign-In (Android), document (PDF/image) analysis, in-app account deletion, and transfer of information abroad.
- August 26, 2026: First enacted