UNELMA TaskUNELMATask

Privacy Policy

Last updated: August 8, 2026

UNELMA Task ("we", "the service") is a company task-management tool by UNELMA Technology, available at task.unelma.tech and as a mobile application. This policy describes what data we process and why.

Data we collect

  • Account data: name, e-mail address, avatar, system role, interface language.
  • Work content: tasks, comments, requests, attachments and reactions you create in the service.
  • Technical data: device push-notification tokens, session data (cookies), last sign-in time.
  • Integrations (opt-in): Telegram chat identifier when you link the bot.
  • Meeting recordings (opt-in): when you start a recording, our bot joins the video call — participants see it in the attendee list by name and are notified of the recording that way. Audio and video capture, speech transcription and its analysis run on our own self-hosted infrastructure; recordings and transcripts are not shared with third parties and are not used to train third-party models. A recording is visible to its owner and to whoever they share it with, and can be deleted at any time.

How we use it

  • providing the service features: tasks, discussions, notifications;
  • delivering notifications to the channels you choose (push, e-mail, Telegram);
  • authentication and account security;
  • support and failure diagnostics.

We do not sell personal data and do not use it for advertising.

"Unelma Task — Meet Recorder" browser extension (Chrome and Safari)

The extension adds a recording button to meet.google.com pages. It communicates exclusively with task.unelma.tech; nothing is sent to third parties. For authentication the Chrome version relies on your existing service session (cookie), while the Safari version uses a personal access token that you explicitly create on the platform's "Extension" page; the token is stored inside the extension and can be revoked by contacting support. The extension does not read meeting content and does not capture audio or video in the browser — recording is performed by our bot on our own infrastructure, as described above. Meeting details (link, title, project, language, recording format) are sent to the platform only after your explicit confirmation. Locally the extension stores only technical preferences (server address, card position) and collects no usage analytics.

Google Calendar data

The meeting-scheduling module lets you connect Google Calendar at your explicit choice (via OAuth 2.0). We request the following permissions and use them strictly for the purposes listed:

  • Calendar events (calendar.events): creating events with a Google Meet link for confirmed bookings, and rescheduling or cancelling them. We only create and modify events that belong to the service's meetings.
  • Free/busy (calendar.freebusy): reading busy intervals to compute available time slots. We do not read the content, titles or attendees of your events.
  • Calendar list (calendar.calendarlist.readonly): so you can choose which calendars count towards availability and where events are written.
  • E-mail and profile: linking the connected Google account to your service account.

Access tokens are stored on our servers encrypted (AES-256-GCM) and are never shared with third parties. You can disconnect the calendar at any time under Profile → Scheduling — disconnecting deletes the tokens.

Unelma Task's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is not sold, is not used for advertising, and is not used to train models.

Service providers

We rely on third-party processors to run the service:

  • Firebase Cloud Messaging / Apple Push Notification service — push delivery;
  • Resend — e-mail notifications;
  • Telegram — messenger notifications (only if you link your account).

Storage and security

Data is stored on our servers and transferred over secure channels (HTTPS). Access is restricted by the service's role model.

Retention and account deletion

Data is kept while your account is active. You can delete your account yourself: Profile → Delete account. On deletion, personal data (name, e-mail, avatar, device tokens, integration links) is removed or anonymized and the account is deactivated. Work content created within projects is preserved in anonymized form for team data integrity.

Your rights

You may request access to, correction of, or deletion of your data — use the profile settings or contact us.

Contact

Data questions: [email protected]