Privacy Policy

This Privacy Policy explains how Wetapoint collects, uses, and shares personal information when you use our website at wetapoint.com, our mobile applications, and any related APIs (together, the “Service”).

We act as a data controller for account holders who sign up directly. For personal data about end-users of an organisation that uses the Service (field operators, volunteers, staff), we act as a data processor on behalf of that organisation.

1. Who controls your data

MB "Wetapoint", Papiškių g. 19-1, LT-06282 Vilnius, Lithuania. Registration number: 308011788. For any privacy-related question, contact privacy@wetapoint.com.

2. What we collect

Account information

• Name, email address, and protected account credentials.
• Organisation name at registration.
• Optional profile details you choose to add: phone number, role description, profile photo.

Device location

• Real-time GPS coordinates while you are signed in and location sharing is enabled. If you grant background-location permission, sharing may continue while the app is in the background or your screen is locked, until you stop sharing, sign out, or disable the permission. Each location update includes latitude, longitude, altitude, accuracy, heading, speed, the network type in use (Wi-Fi, cellular, or unknown), the time it was recorded, the identifier(s) of any operation or event it relates to, and a device identifier (a stable random identifier generated when the app is installed), and general device information such as operating-system and device model.

Push notifications

• Device push tokens issued by Apple (APNs) and Google (Firebase Cloud Messaging), stored so we can deliver notifications to your device.
• When a notification is sent, its title, body, and a reference to the related record (for example, a task identifier) pass through Apple's or Google's push-notification infrastructure to reach your device.

Uploaded files and media

• Images, videos, and documents you attach to tasks, incidents, or messages.
• Push-to-talk (PTT) radio audio transmissions you record and send through organisational channels.
• Live video streams you broadcast via the mobile “Go Live” feature and talkback audio sent by dashboard operators. Live streams are relayed in real time through our media server and are not stored, unless your organisation enables Stream recording — see the next section.
• Camera feeds from customer-connected devices that are relayed through the Service.

Stream recording

Stream recording is an optional feature that is off by default. Only an administrator of your organisation can turn it on, and only for that organisation. Where it is off, nothing in this section applies and live video is not stored.

• What is recorded: when your organisation enables Stream recording, a broadcast you make through “Go Live” is stored — the video and the audio it carries, together with the location track recorded while you were broadcasting. Camera feeds from customer-connected devices are not recorded.
• Who decides: your organisation. It is the data controller for recordings, it decides whether to switch the feature on, and it is responsible for the legal basis and for informing the people it records. Wetapoint acts as processor and stores recordings on the organisation's instruction.
• Who can see them: administrators of your organisation, and any other role your organisation grants the recordings permission to. Recordings are not shared outside your organisation.
• How long they are kept: for the recording-retention period your organisation's plan carries, after which they are deleted automatically. The location track stored inside a recording is part of that recording and follows the recording's retention, not the location-history schedule in section 4.
• What you see: while you are broadcasting and recording is on, a REC indicator is shown in the app, and the first time it applies to you the app shows a notice explaining what is recorded and who can watch it. People watching the live stream see a REC badge on the player.
• If it is switched off again: no new broadcasts are recorded. Recordings already made are kept and continue to expire on the retention schedule above, unless your organisation deletes them sooner.

Audit logs and metadata

• IP address, browser user-agent, and device information in server-side audit logs.
• Authentication events (sign-ins, token refreshes), request IDs, and operational telemetry.

Organisation-managed accounts

If your account is managed by an organisation (for example, as a field operator, volunteer, or staff member), the organisation is the data controller and determines what data is collected about you. Authorised administrators and operators in your organisation may be able to see your real-time location while you are on duty, messages you send in organisational channels, PTT radio transmissions, task or incident activity attributed to you, and — where the organisation has enabled Stream recording — recordings of the live video you broadcast. Wetapoint processes this data on the organisation's behalf as a data processor.

Your organisation may create your account or provide account and role information about you. Ask your organisation for its own privacy notice and the legal basis on which it uses the Service.

Billing information

• Plan, billing email, and subscription history. Payment card details are collected and stored by Stripe — we never see full card numbers.

Advertising and conversion data

• If you consent to advertising cookies on our marketing website: interactions with our Google Ads (ad clicks and the click identifiers Google attaches to them), the conversion events that follow (for example reaching the sign-up page), and the advertising identifiers Google uses for remarketing. This applies to wetapoint.com only, never inside the signed-in Service. See section 9.

3. Why we use data and our lawful basis

For organisation-managed data, your organisation determines the purposes and lawful basis and Wetapoint processes the data on its documented instructions. Where Wetapoint acts as controller, the main purposes and bases are:

• Account, identity, device identifiers, service content, and enabled location: to provide the requested Service, authenticate users, support collaboration, and deliver notifications. The basis is performance of our contract or steps requested before entering it.
• Security and operational records: to protect users, prevent misuse, diagnose faults, and maintain reliable service. The basis is our legitimate interest in operating a safe and dependable Service. You may object where the law gives you that right.
• Billing and transaction records: to administer the subscription and meet tax, accounting, and other legal duties. The bases are contract performance and compliance with legal obligations.
• Marketing communications: consent where required. You can withdraw consent at any time.
• Advertising and conversion measurement on wetapoint.com: your consent under Article 6(1)(a) GDPR, given through the cookie banner. Nothing is set or sent before you opt in, and you can withdraw at any time through the Cookie settings link in the site footer.

Name, email, credentials, and the information needed for a selected feature are required to provide that account or feature. Without them, it may not work. Profile details, marketing consent, and features such as location sharing, camera, microphone, or notifications are optional; declining them only limits the relevant feature.

We do not use personal data to make decisions based solely on automated processing that produce legal or similarly significant effects. We do not profile users of the Service for advertising: the only advertising processing we carry out is the consent-based conversion measurement and remarketing on our public marketing website, described in section 9.

4. Retention

• Account and profile data: retained while your account is active. When you request erasure yourself, profile information — name, contact details, credentials, and device tokens — is deleted immediately. When an organisation removes a member, that profile information is deleted after a 30-day administrative window. Limited identifiers may remain in restricted audit records, as described under “Disabling, deletion, and erasure” below.
• Location pings: retained according to your organisation's configured retention schedule, capped by the history-retention window your plan carries (shown on the Billing page in the app), then deleted from primary storage. Location history remains personal data until it is actually deleted. Copies may persist in encrypted off-site backups until those backups age out (up to six months).
• PTT radio audio: content is deleted 30 days after recording. Minimal event metadata may be retained where needed for security, accountability, or legal obligations, no longer than the applicable audit-record period.
• Live video: not stored, unless your organisation enables Stream recording. Otherwise streams are relayed in real time and discarded when the broadcast ends. When recording is enabled, the recorded broadcast — video, audio, and the location track captured while it was live — is kept for the recording-retention period the organisation's plan carries, then deleted automatically. The location track stored inside a recording follows the recording's retention, not the location-ping schedule above, and is deleted with it.
• Audit records: identifiers are removed from audit records on a categorised schedule — after 1 year for authentication and technical security events, after 3 years for operational activity records, and after 7 years for administrative, account, and billing governance records. The event record itself (action type and timestamp) is retained append-only.
• Backups: rolling 14-day window of on-server database backups, plus encrypted off-site backups kept on a rolling snapshot schedule of 14 daily, 8 weekly, and 6 monthly snapshots (approximately six months at most). Data inside a backup is purged when the snapshot itself ages out. If a backup is restored, our retention and deletion processes are re-applied to the restored data.
• Billing records: retained for the period required by the accounting and tax legislation applicable to us.
• Organisation data after subscription ends: when an organisation's subscription is terminated or deactivated, its administrators retain export-only access for 30 days. After that window an automated process permanently deletes the organisation's data from primary storage, keeping only a minimal billing and audit record. Copies in encrypted off-site backups age out on the snapshot schedule above (up to approximately six months).

Disabling, deletion, and erasure

Three different actions have three different effects:

• Disabling a user: when an organisation administrator disables a user, access is revoked immediately — active sessions and refresh tokens are invalidated, push and device tokens are removed, sign-in is blocked, and location reporting and realtime connections stop. Disabling an account does not by itself delete the user's historical activity. Who disabled the account, and when, is recorded.
• Profile deletion: when you request erasure from your account settings, profile information that is no longer required — name, contact details, credentials, and device tokens — is deleted immediately. When an organisation removes a member, the same profile information is deleted after a 30-day administrative window. Recordings of your broadcasts, where your organisation enabled Stream recording, are deleted with your profile — they show your face and voice, so they are not merely detached from your name. Other content previously contributed to the organisation's workspace (tasks, incidents, message threads) may remain under the organisation's retention instructions and may be displayed as contributed by a deleted user.
• Organisation deletion: as described under “Organisation data after subscription ends” above.

Limited identifiers may remain in restricted audit records where necessary for security investigations, compliance with applicable law, or the establishment, exercise or defence of legal claims; these records are retained only for the periods in the audit-record schedule above and are not used for ordinary product functionality. Location history, audio recordings, and other operational data are deleted according to the organisation's configured retention schedule. Removing a user's profile does not make such data anonymous where the individual may still be identifiable from the remaining information.

You can download a machine-readable export of your data and request erasure of your account from your account settings inside the Service.

5. Recipients and sub-processors

We share personal information only with the service providers listed on our Sub-processors page. Each is bound by contract to process data only on our instructions. The one exception sits outside the Service: where you consent to advertising cookies on our marketing website, Google receives ad interaction and conversion data as described in section 9. Google is not a sub-processor of Service data and receives no customer content, location data, or account data through that channel.

Push notifications are delivered through Apple Push Notification service (for iOS devices) and Google Firebase Cloud Messaging (for Android devices). Your device push token and the content of each notification (title, body, and a reference to the related record) pass through Apple's or Google's infrastructure for delivery only.

We do not sell personal information.

6. International transfers

The Service is hosted in the European Union. Some service providers may process data outside the EEA. Where a restricted transfer occurs, we require an applicable lawful safeguard in the provider's terms, such as an adequacy decision or recognised framework, or the European Commission's Standard Contractual Clauses, as appropriate to that provider and transfer.

7. Your rights

Subject to applicable law, you have the right to:

• Access the personal information we hold about you.
• Have inaccurate information corrected.
• Have your information deleted where no overriding legal ground requires retention.
• Restrict or object to certain processing.
• Receive a portable copy in a structured, machine-readable format.
• Withdraw consent at any time where processing is consent-based.
• Lodge a complaint with your local supervisory authority, including Lithuania's State Data Protection Inspectorate (VDAI).

How to exercise your rights

Email privacy@wetapoint.com. We respond without undue delay and normally within one month. Where permitted, we may extend this by up to two further months because of the request's complexity or number; we will tell you within the first month and explain why.

Where your account is managed by an organisation, that organisation is the controller and we act on its instructions. Requests about operational data it controls — including any recordings of your broadcasts — are routed to that organisation, and we support it in answering you. You can also delete your own account from your account settings, which removes recordings of you as described in section 4.

8. Cookies

See our Cookie Policy for the full list and your options.

9. Advertising and conversion measurement (Google Ads)

We advertise Wetapoint through Google Ads. On our public marketing website at wetapoint.com — and nowhere inside the signed-in Service — we load Google's tag to measure whether visits arriving from our ads lead to sign-ups, and to show our ads again to people who visited (remarketing).

• What is processed: ad interaction data (which ad click brought you to the site and the click identifier attached to it), conversion events on our site, remarketing identifiers stored in cookies, plus the technical data any web request carries, such as IP address, browser user-agent, and the page visited.
• Lawful basis: your consent, Article 6(1)(a) GDPR. The tag is not loaded — no script, no cookie, no request to Google — until you accept advertising cookies in our banner. We use Google Consent Mode v2 to signal your choice to Google.
• Recipient: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, acting as an independent controller for this processing under its Privacy Policy. Google may transfer data to the United States and other countries; such transfers rely on the EU–US Data Privacy Framework, to which Google LLC is certified, or on the European Commission's Standard Contractual Clauses.
• Retention: the advertising cookies we set on wetapoint.com expire after up to 90 days, as listed in the Cookie Policy. Data held by Google is retained under Google's own advertising data-retention schedule; we see only aggregated conversion reporting in the Google Ads interface.
• Withdrawing consent: use the Cookie settings link in the site footer at any time. Withdrawal takes effect immediately — we signal it to Google, delete the Google cookies reachable from our domain, and reload the page so the tag is gone. Withdrawal does not affect the lawfulness of processing carried out before it. You can also manage Google's own ad personalisation in Google My Ad Center.

We do not upload customer lists, email addresses, or any Service data to Google for advertising purposes.

10. Children

The Service is not intended for children under 16. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact privacy@wetapoint.com and we will delete it.

11. Changes to this policy

Material changes will be announced to active account holders by email at least 30 days before they take effect. The “Last updated” date at the top reflects the most recent revision.

12. Contact

MB "Wetapoint", Papiškių g. 19-1, LT-06282 Vilnius, Lithuania.
privacy@wetapoint.com