Privacy Policy
Effective date: 2026-11-19
1. Who we are and what this policy covers
Datika LTD, trading as Datika, is a company established in Israel, company registration number 517410411. Our registered postal address is available on request from legal@datika.io and from the Israeli Registrar of Companies. In this policy, “Datika,” “we,” and “us” refer to that entity. Datika is the controller (under Israeli law, the database owner) of the personal information described in this policy, unless a Service-specific section says otherwise.
This policy covers Tutila. The Service is Tutila, a group travel app for iOS and Android, together with its trip and invitation website. It helps organizers plan trips and invite members, who can choose to share their location during a trip.
This notice describes the personal information Datika handles for this Service. Practices described for one Datika product do not automatically apply to another.
You can contact us at privacy@datika.io, or by post at the address we provide on request.
Regional privacy contact. Datika is established in Israel. Contact Datika directly at privacy@datika.io for questions or requests concerning Tutila, including when you use the Service from another country. Your rights and ability to contact a regulator do not depend on using a local Datika office.
2. Our privacy approach
We aim to limit personal information to what a Service actually needs. Even a Service without accounts or analytics can involve technical delivery data or information you choose to send us. The sections below describe what this Service handles, why, with whom, for how long, and what choices you have.
“Personal information” means information relating to an identified or identifiable person. It can include an email address, IP address, device identifier, location, or information about someone other than the person using an app. Removing a name does not necessarily make information anonymous.
The Service-specific sections below explain whether this Service uses advertising or tracking, sells or shares personal information as those terms are defined by applicable law, or combines information across Datika products. A practice disclosed for one Service does not automatically apply to another.
This policy does not itself give permission to collect information. Where consent is needed, we ask separately, and you may withdraw that consent.
3. Information handled by this Service
Information you send us
If you contact us through an available channel, we receive the information you choose to send, such as your email address, name, message, attachments, and information needed to investigate your request. We use it to respond, provide requested support, address complaints or abuse reports, and meet applicable legal obligations. Please do not send unnecessary sensitive information or information about other people.
Providing this information is voluntary, but we may be unable to answer or investigate without the relevant details. If we request a particular field, we explain whether it is required and why.
If you report misuse of a Service, or if we investigate suspected misuse, we use the information available to us to assess the report, take the measures described in our terms, protect people and the Service, and, where the law requires or permits, cooperate with law enforcement, regulators, or courts. We may preserve relevant information for those purposes where the law requires it or it is reasonably necessary.
Feature, delivery and security information
3.1 Location (precise or approximate)
- When: only while you have turned sharing on for an active trip. You give this consent per trip. Your device may give the app precise or approximate location, depending on what you allow in the system settings.
- What is sent: your position (latitude and longitude), its accuracy, speed and direction of travel if the device reports them, and the time it was measured.
- Who sees it: in "everyone" trips, your shared position is visible to the members of the trip. In "organizers only" trips, ordinary members’ shared positions are visible only to organizers and co-organizers; organizers’ and co-organizers’ own shared positions remain visible to the whole group. Only you and the organizers (including co-organizers) can see your position’s accuracy, when it was recorded and how old it is, speed and direction of travel. Other members receive coordinates only while you are sharing and the position is fresh, where the visibility mode permits; they do not receive these position details. The sharing screen tells you who can see you before you start. If the organizer later widens the audience, you are asked again before more people see you. If someone is made an organizer and can now see you, you are told.
- Background: if you choose "keep sharing when the app is not open in front", sharing continues while you use another app or the device is locked, and your device shows that location is in use the whole time (the location indicator on iPhone, an ongoing notification on Android). It stops when you pause, leave or the trip ends, and it does not restart by itself after the device restarts or the app is closed or stopped by the system. The app never asks for "Always" or background-location permission.
- What we keep: only the latest position per member, held in the live trip service. It is deleted when you pause, leave or are removed, and when the trip ends; the live trip data is erased completely 24 hours after the trip ends.
- Arrivals at stops: while you share, the app works out when you arrive at a planned stop. We store that you arrived, when, when you left the stop, how sure the app was, and the accuracy of the position, but not the coordinates. The same record is made when you tap Arrived. Arrival records can remain with the trip after you leave, but your personal arrival records are deleted when you delete your account (section 7).
- Your own distance on this device: you can ask to see your own distance to the meeting point without sharing. This uses location only on your device, only while that card is on screen, and nothing from it is uploaded.
- Distance covered: while you share, your device adds up the distance you cover. Only two numbers (total distance and moving time) are uploaded, and only if you shared during the trip. Only you see your own numbers; the group sees an average once at least 3 members reported, calculated once, a day after the trip ended. This threshold reduces individual visibility but is not a guarantee of anonymity. Your numbers are deleted when you leave the trip, are removed or delete your account; otherwise they are kept with the trip.
- Compass direction: read only on your device while the direction arrow is on screen; never uploaded.
3.2 Positions you attach on purpose
- Help request: when you send "Need help", you can attach your current position and an optional message (up to 280 characters). Trip members are told you need help, but only organizers see your message. If the trip is "organizers only", only organizers see an ordinary member's help position; an organizer's or co-organizer's help position is visible to the whole group, as their shared position is (section 3.1). The position is erased 24 hours after the trip ends (a copy kept to answer repeated sends of the same request is deleted after 24 hours). The message is kept with the trip (section 7); it and the position are erased at once if you delete your account.
- Meeting-point pin: an organizer can drop a meeting point as a pin, at their own current position or at coordinates they type or paste. Everyone in the trip sees that point. Every dropped pin, wherever its position came from, has its coordinates and address erased 24 hours after the trip ends; its name is kept with the trip. A meeting point set at a planned stop is not erased: it uses the stop's name, address and coordinates, which stay with the itinerary (section 7, ended trips and their content).
3.3 Battery state
- While you share, the app can raise a "Battery low" flag for you when the battery falls below 20 % (it clears above 30 %). You can also raise or clear it yourself. Only a yes/no flag and whether it was automatic are sent, never the battery level. The flag expires after 2 hours and is deleted when you clear it, leave or the trip ends. If you raise or clear it yourself, a trip event records that, kept for 30 days after the trip ends; an automatic flag leaves no such event.
3.4 Your identity
- All participants and organizers sign in with Apple or Google. A device key helps a signed-in user sign in again on the same device; it does not create a separate guest account.
- We receive and keep an account identifier from Apple or Google, the email address they give us (with Apple this can be a private relay address), whether the email is verified, and the name you use in the app. With Sign in with Apple we also keep an encrypted Apple refresh token so we can revoke the link when you delete your account.
- We keep sign-in sessions, including the sign-in method and platform (refresh tokens are stored only as hashes).
- We record which version of the Terms and Acceptable Use Policy you accepted and when, and whether your account has been suspended for a breach. These records are deleted with your account.
Phone number for organizer contact
Before joining or creating a trip, you enter a phone number so organizers can contact you during the trip. We check its format but do not verify that you own it; no verification SMS is sent. The organizer and co-organizers of a trip you are an active member of can see it during the active trip and for 24 hours after it ends. Other participants cannot see phone numbers, including organizers' numbers. Access ends if you leave or are removed from the trip.
An organizer can open their phone, messaging or WhatsApp app to contact you. Those conversations occur outside Tutila, and the number may remain in their device's call or message history. You can change or remove your number in Account; removing it prevents joining or creating new trips until you add a number again, but existing trips continue. We remove the number from the live database when you remove it or delete your account. Backup retention is described in section 7.
3.5 Device and notification data
- An installation identifier created by the app (stable per installation).
- Push notification tokens from Apple Push Notification service and Firebase Cloud Messaging, stored encrypted, with the platform (which picks the push service), the app version and the app language (which picks the language of notifications). We do not receive your time zone, device model or battery level.
- On iPhone, if you turn on "Next destination on the lock screen", Live Activity push tokens, stored encrypted. The lock-screen content shows the next destination or meeting point, the time and your own distance; it never shows anyone's position.
- Push notifications never contain coordinates.
3.6 Trip content
- What organizers enter: trip title and dates, stops with names, addresses, coordinates and notes, meeting-point names, addresses and short notes, free-time times. Coordinates of stops can come from a place search (see MapTiler in section 6) or from a map link the organizer pastes. The search text and the pasted link are sent to our server only to find the place, and are not stored. If the pasted link is a short link from Google Maps, Apple Maps or Waze, our server asks that provider where the link leads (the request comes from our server, not your device); the place the organizer then saves becomes part of the trip.
- What members do in a trip: joining and leaving, roles, roll-call answers, flags ("Lost", "Battery low", "Running late", "I'm here"), check-in requests, visibility choices. Some of these are kept as trip events for the organizer's history and for security.
Attendance details. In every visibility mode, only you and the organizers (including co-organizers) can see your individual roll-call answers, “I'm here” attendance flag and arrival/departure records at stops. Other members can see roll-call counts, not other members’ individual answers or arrival records. Names, roles and sharing status remain visible; other status markers and positions follow the visibility rules above.
3.7 Purchases
- When an organizer buys a Trip Pass, the purchase is made through the Apple App Store or Google Play. We do not receive card or bank details. We receive and keep the store's transaction or order identifier (for Google also the purchase token), the product, the price and currency, the test or live environment, the status (including refunds), the trip it applies to and, while your account exists, the buyer's account. Account deletion removes the direct buyer-account and purchase-intent links; the trip reference and necessary store identifiers remain for the limited purchase period in section 7.
3.8 Reports and safety records
- If you report a member or a problem, we keep the reason, the optional details you write (up to 1,000 characters), the trip, the reported member and who reported it.
- We keep a security and audit log of sensitive events (for example sign-in token reuse, account deletion and payment events).
- To protect the service against abuse we use your IP address for rate limiting (for example, limiting how many join codes can be tried).
- While a reviewer sign-in is enabled for Apple or Google app review, attempts to use it are recorded in the security log with the caller's IP address (failed attempts are deleted after 30 days, successful ones with the 90-day security log).
3.9 Invites and the Play install referrer
- Invite links and join codes are secret values that let someone join a trip. Invite links last up to 30 days and never past the end of the trip. The trip’s main link renews automatically while the trip is open, and an organizer can replace it at any time. Join codes expire after at most 7 days.
- On Android, if you install the app from an invite page, Google Play can pass the join code to the app once after install. The app only uses it to show you the trip preview; you still have to tap Join.
3.10 What we do not collect
- No contacts, photos, microphone, camera, health or fitness data, step counts or motion-activity data.
- No advertising identifier, no advertising, no tracking across other companies' apps or websites, and no analytics or crash-reporting SDK.
- No chat between participants. Other members can see display names and statuses; organizer-authored trip and meeting-point text is shared with the trip. A participant's help-request message is visible only to organizers.
Cookies and similar technologies
The trip website uses HTTP-only cookies for sign-in: gtc_at holds an access token for up to 10 minutes; gtc_rt holds a refresh token for up to 30 days; and gtc_s records that a session exists for up to 30 days. Their actual expiry can be shorter when the session expires. These cookies support authentication and session continuity. The app also uses an installation identifier and device credentials to recognize a signed-in installation, as described above.
Where optional storage or access technologies require consent, we obtain it before using them and provide a way to change that choice. Reading this policy or continuing to browse is not consent. Disabling a technology necessary for a feature may prevent that feature from working.
Where a Service uses no tracking or optional technologies, browser signals such as Do Not Track or Global Privacy Control have no effect because there is nothing to opt out of. Where a Service does use such technologies, its description above explains how it responds to those signals.
4. Device access and local information
Location and notifications. Location permission is used for the optional on-device distance display and the trip-sharing features described in section 3. You can refuse location access or change precise/approximate access in your device settings. Sharing also requires the in-app trip control. If you enable continued sharing while using another app or locking the device, iOS uses its location background mode and Android uses a foreground location service with an ongoing notification. The app does not request Always location access on iOS or Android background-location permission. Notification permission controls alerts; iPhone Live Activities have a separate user control.
Local storage. The app keeps sign-in secrets, its device private key and installation identifier in platform secure storage backed by iOS Keychain or Android Keystore. Trip snapshots, including last-known positions received from the service, are cached in the app's cache directory for offline display. Selected actions such as arrival updates and sharing-stop requests can wait in a local queue until a connection returns; live location fixes and new help requests are not queued for later upload. Offline data can be stale. The trip cache is outside normal iCloud/Android backup locations; Android app backup is disabled. This does not erase information someone independently copied or saved elsewhere. Account deletion clears local sign-in tokens and device credentials after the server confirms the request.
Other apps. Opening navigation or an organizer's Call, SMS or WhatsApp action hands the selected destination or number to the chosen app. Those actions do not give Tutila access to your address book, calls or conversations. Device settings and the chosen service control its own processing.
Operating systems, app stores, and services you independently choose may process information under their own notices. We remain responsible for the providers and integrations we use to deliver our services as required by applicable law; their separate policies do not replace our disclosures.
5. Reasons and legal grounds for processing
Where applicable law requires a legal basis, the Service-specific description below identifies it for each processing purpose. A legal basis for one purpose does not automatically apply to another.
Where the GDPR or UK GDPR applies, we distinguish the following purposes:
- Providing your account and requested trip features: sign-in, trip planning, invitations, membership, requested notifications, purchase verification and application of Trip Pass limits rely on performance of our contract with you, to the extent the processing is objectively necessary to provide those features.
- Optional location features: uploading and sharing your position, automatic arrival detection while sharing and the optional distance-total feature rely on your consent. You can stop future sharing using the in-app control or device settings. Sending a help position is a separate action you choose. Withdrawing consent does not invalidate earlier processing or itself justify retaining old personal activity.
- Organizer contact: we use the number you provide to let authorized organizers contact you about the trip, based on our legitimate interest in enabling coordination during in-person group travel. Numbers are not used for marketing or verification, and access is limited as described in section 3. You may object to this processing and may remove the number in Account; the effects on joining or creating trips are explained there. We assess objections under the applicable law.
- Security, abuse handling and service integrity: proportionate rate limits, security records and investigations rely on our legitimate interests in preventing misuse and protecting users and the service. Retention must remain limited to the relevant purpose and period.
- Legal duties: accounting records, legally required disclosures and handling statutory privacy requests rely on the legal obligation applicable to the particular activity. Not every payment-related field is a legally required accounting record.
- Support and disputes: responding to ordinary support correspondence and addressing specific claims rely on our legitimate interests in providing assistance and establishing or defending rights, unless a contract or legal obligation supplies the applicable basis.
Providing information is not a general legal duty merely because Tutila requires it for a feature. Without the sign-in information we cannot provide an account; without a phone number you cannot create or join a new trip under the current configuration. Optional location sharing is not required to maintain an account. Where local law requires consent or a collection notice, including Israeli law, we provide the relevant notice and obtain the required consent; GDPR legal-basis terminology does not replace those requirements.
AI processing and automated decisions
Tutila does not use a generative-AI feature or send trip content to an AI service. It uses automated rules to estimate arrivals, distance and whether a sharing participant may be falling behind, and to enforce technical and purchase limits. These are coordination and service-management functions; an alert is not a determination that someone is lost or safe. Tutila does not use solely automated processing to make decisions about you with legal or similarly significant effects. Contact the privacy address if you believe an automated result is incorrect.
We do not treat acceptance of our terms as general consent to unrelated processing. Before using information for a new purpose, we assess whether it is compatible with the original purpose, update the relevant disclosure and obtain any consent required for that use. We do not treat a policy update as permission to reuse previously collected information.
6. Recipients and international processing
The providers and other recipients for this Service, the information they handle, and relevant international processing are:
Trip participants. Members receive display names, roles, status and positions where the trip visibility mode permits. Organizers additionally receive the contact number during its defined access window, help messages and organizer-only coordination information. A guide using information independently outside Tutila has responsibility for that use; this does not remove Datika's responsibilities for operating Tutila.
Cloudflare, Inc. (United States). Cloudflare provides hosting, D1 database and recovery, live-trip infrastructure, queues and technical logging, and processes the server-side information described in section 3. Its Customer Data Processing Addendum is incorporated into its self-service agreement. For covered European transfers, its published safeguards include the Data Privacy Framework and, where required, EU Standard Contractual Clauses with the UK Addendum. Cloudflare operates international infrastructure; information is not promised to remain solely in Israel or the EU.
Apple and Google. Apple provides Sign in with Apple, APNs/Live Activities and App Store purchase services. Google provides Google Sign-In, Firebase Cloud Messaging, Google Play Billing and the Play install-referrer service. When an organizer pastes a Google Maps, Apple Maps or Waze short link, our server sends that link to the provider to find where it leads. They receive the tokens, purchase verification and delivery information needed for those features. Push content contains no coordinates. Firebase Cloud Messaging is covered by Google's published Firebase Data Processing and Security Terms, including applicable transfer provisions. App-store and identity-provider activities are also governed by the relevant provider's terms and notices.
MapTiler AG (Switzerland). The device requests map tiles directly, exposing its network address and requested map area. Organizer place searches are sent through our server; saved place information becomes part of the itinerary. MapTiler describes its principal processing locations as Switzerland and the EEA.
Services you choose. Navigation receives the selected destination; an app used to share an invite receives that invite. Organizer phone/SMS/WhatsApp actions send the selected number to that service. These services can retain their own copies.
Correspondence. Messages to Datika's legal, privacy and abuse addresses, and to Tutila addresses such as support@tutila.app, pass through Cloudflare Email Routing to a Google Gmail mailbox in the United States. This mailbox operates under Google's consumer terms; we do not represent it as covered by a Google Workspace processing agreement.
You may request information about relevant transfer safeguards at privacy@datika.io.
We may disclose relevant information where a law requires it, or where legally permitted and necessary to address fraud, serious misuse, threats to safety, or legal claims. We assess the request and limit disclosure to what is appropriate. This does not mean that we collect information we otherwise do not hold.
If a business reorganization affects personal information we hold, any transfer must have a lawful basis, appropriate safeguards, and any required notice. It does not automatically authorize new uses inconsistent with the commitments made when the information was obtained.
Map requests and transfer information. Map tiles are delivered directly to the device; place-search requests go through our server. These requests expose the information described above to MapTiler rather than remaining entirely within Datika. MapTiler’s privacy notice explains its own processing. We do not promise that map requests are anonymous or that a particular short IP-address deletion period applies. For European transfers to Israel or Switzerland, applicable adequacy decisions may provide the transfer basis; transfers elsewhere require the applicable adequacy coverage or other lawful safeguards. You can request details relevant to your information from privacy@datika.io.
7. Retention and deletion
We keep personal information only for the period needed for the disclosed purpose or a documented legal requirement. The applicable periods or concrete criteria are:
Current feature-specific periods.
| Information | Period or deletion trigger |
|---|---|
| Your live position | Until you pause, leave or are removed, or the trip ends; live trip data erased 24 hours after the trip ends |
| Help request position | Erased 24 hours after the trip ends (the message is a personal trip record, row below) |
| Coordinates and address of a dropped meeting-point pin | Erased 24 hours after the trip ends. A meeting point at a planned stop keeps the stop's coordinates with the itinerary (see “Personal trip activity and shared content” below) |
| Flags "Lost", "Battery low" and "I'm here" | Expire after 1 to 2 hours; deleted when cleared, when you leave and when the trip ends |
| "Running late" status | Does not expire by itself; kept until you clear it, rejoin the trip or delete your account |
| Personal trip records: arrival and departure times at stops, help messages, roll-call answers, location-sharing session records (start and stop times, whether background sharing or navigation to you was allowed, platform) and records of joining and leaving | Kept with the trip as its history while your account exists. Leaving or being removed deletes your roll-call answers, flags, distance totals and member-related trip events; the other records stay with the trip. All are deleted when you delete your account or when the trip is deleted |
| Check-in requests | 7 days |
| Invite codes and share-link secrets | 30 days after the invite was revoked or the trip ended |
| Member-related trip events (flags, roll-call marks, falling-behind alerts, audience changes) | 30 days after the trip ended |
| Live Activity tokens | Deleted when the trip ends or you leave, and when you sign out on that phone; any token not updated for 30 days |
| Push notification tokens (with platform, app version and language) | When you sign out, the app asks us to delete this phone's push token, and we delete it even if you are still signed in on other phones or the website. If the phone is offline or the request fails, the app keeps the request and sends it again the next time the app is open with a connection (also after a restart), and it asks Google's push service to cancel the phone's Firebase token. When your sign-out ends your last signed-in session, we also delete all your other push tokens. If a signed-out phone is never opened again with a connection, its token is deleted by the 60-day clean-up. All are deleted on account deletion; any token not updated for 60 days is deleted |
| Sign-in sessions | Deleted 7 days after they expire or are revoked (refresh tokens last 30 days) |
| Unfinished purchase attempts | 30 days |
| Pending Sign in with Apple revocations | At most 30 days |
Account and phone. The account is kept until you delete it, rather than being automatically deleted for inactivity. You can remove the phone number separately; removal deletes it from the live account. The database recovery period is explained below.
Requesting deletion. Use Account > Delete account in the app or visit the Tutila account-deletion page. You can also request deletion without the app by emailing privacy@datika.io with the subject “Delete my Tutila account”. We ask only for information reasonably needed to verify and carry out the request and respond within the applicable legal deadline. The service revokes sessions and removes sign-in links, device keys, push and Live Activity tokens, and cached request responses. It deletes your personal arrivals, progress, location-sharing records, help requests, addressed check-ins, flags, roll-call answers, distance totals and relevant personal trip events. Membership records used by shared trip content are detached from your account and shown as “Deleted user”; shared itinerary content can remain. This does not guarantee that free text written by others contains no information about you. Contact privacy@datika.io to request review of personal information in retained shared content. Direct buyer-account and purchase-intent links are removed from purchase records; the trip reference can remain during the purchase-retention period. Necessary purchase, security and report records are handled separately under the periods and exceptions below. Deleting an organizer account cancels trips it owns that have not ended. Apple authorization revocation is requested; failed requests are queued for retry, rather than being guaranteed to finish at Apple immediately. Backup expiry and justified retention can outlast deletion of the live account. Copies independently saved by organizers or other recipients are not remotely recalled by this action.
Where information must be retained for a legal obligation or claim, we limit its use and access to that purpose and delete it when the reason ends. If this Service uses backups or offers account deletion, its description above explains the relevant timing.
Database recovery copies. We use Cloudflare D1 Time Travel on the Workers Paid plan as our only database backup. It retains database recovery history for up to 30 days. Information removed from the live database may remain in that recovery history until it expires. We do not keep separate database backup exports.
Personal trip activity and shared content. Shared itineraries, stop details, organizer notes and other shared trip content remain available as trip history until the organizer requests their deletion or they are no longer needed for that shared purpose, subject to applicable privacy rights. Account deletion removes your personal activity as described above, detaches account and membership references and cancels trips you own that have not ended; it does not automatically delete the shared itinerary used by the group. A retained seat labelled “Deleted user” is not a guarantee that the remaining trip content is anonymous. Organizers can request deletion of a trip, and anyone can request review or removal of personal information in shared content, at privacy@datika.io. We assess the request against other participants’ rights and any specific legal retention requirement. Recipients’ independently saved copies are outside the account-deletion function.
Financial records. The app does not keep a long-term accounting archive. Its purchase record contains the store transaction identifier, product, amount, currency, purchase date, payment/refund status and the trip reference; for Google it also contains the purchase token needed for verification and refunds. Associated entitlement, purchase-intent and payment-event records support applying the pass and handling refunds. Account deletion removes the direct buyer-account and purchase-intent links; it does not make the remaining store or trip identifiers anonymous.
The normal purchase-retention window is 180 days. A purchase must be at least 180 days old before deletion. Records for an ended trip are then deleted after the trip has been ended for 180 days. Where a trip has not ended, records remain while the pass is in use; if the pass is no longer in use, any refund must also be at least 180 days old. An unapplied purchase with no trip is deleted once it is 180 days old. A pass on a planned trip remains in use until that trip ends or the entitlement is revoked. The retention job removes the associated purchase records together; payment webhook event records are deleted after 30 days. A specific legal hold can require restricted retention of the relevant record.
Necessary invoices and Apple/Google accounting reports are held separately from the app for Datika’s bookkeeping. Required Israeli accounting records are retained for seven years after the end of the relevant tax year or six years after the income-tax return for that year was filed, whichever is later, and longer only where a specific legal obligation or documented claim requires it. This does not extend the app’s purchase-retention period or authorize keeping unrelated phone numbers, location or personal trip activity.
Security logs. Security audit records are retained for 90 days, except specific records needed for a documented legal obligation or an active investigation or dispute. Any exception is limited to the relevant records and purpose. Payment-event records follow the separate purchase period above. Cloudflare Workers operational logs are a separate short-lived technical store; its standard Paid-plan retention is up to seven days, rather than the database audit-log period.
Reports and correspondence. Abuse reports are deleted after 12 months. Ordinary support, privacy, legal and abuse correspondence in our mailbox is kept for up to 12 months after the last substantive reply. Specific records needed for a legal obligation or a documented investigation or dispute may be retained longer, with access and use limited to that purpose, and are deleted when that reason ends. Retained security records and reports can still contain an account reference or information supplied by another person; replacing a display name or detaching a membership does not make every retained record anonymous.
8. Security
We use safeguards appropriate to the information and risks, including limiting access to people who need it for their work and requiring appropriate protection from our service providers. No service can guarantee absolute security. That limitation does not reduce our legal duties to protect information or to notify affected people and authorities when required.
9. Your choices and privacy rights
Depending on the law that applies, you may have rights to access or obtain a copy of your information, correct it, request deletion, restrict or object to processing, and receive certain information in a portable format. Where we rely on consent, you may withdraw it without affecting the lawfulness of processing before withdrawal. Where applicable, you may also have rights to opt out of specified processing, use an authorized agent, or appeal a decision about your request.
Contact privacy@datika.io to exercise a right. We request only information reasonably needed to verify and fulfill the request and respond within the applicable legal deadline. We do not create new identifying records merely to identify someone where the law does not require us to do so. If we do not hold the requested information, we explain that. We do not penalize you for exercising your rights.
You may complain directly to the relevant privacy regulator; you do not have to contact us first.
- EEA and UK: Where the GDPR or UK GDPR applies, the rights described above are subject to the conditions in that law. You may object to processing based on legitimate interests on grounds relating to your situation and may object to direct marketing at any time. You may complain to your local supervisory authority; see the EEA authority directory or the UK Information Commissioner's Office.
- Israel: Where Israeli privacy law applies, you may request to inspect personal information about you held in a database and request correction of information as provided by that law. A request for information must explain whether disclosure is legally required or voluntary and the consequences of not providing it. Contact us using the details above to make a request.
- United States: Where an applicable state privacy law covers our processing, your rights may include access, correction, deletion, portability, and opting out of sale, targeted advertising, or certain profiling. Some laws also provide an appeal process and rights concerning sensitive information. The Service-specific disclosures describe whether those activities occur here, regardless of whether a particular state law covers us.
Additional regional information that applies to this Service:
Location and contact information. Precise location and phone numbers are used for the features described here, not advertising. The absence of advertising does not mean that information is never disclosed: authorized trip members, organizers and the service providers in section 6 receive the information described there. Stop location sharing or remove your number using the controls described above.
EEA and UK. You may withdraw optional location consent and object to processing based on legitimate interests. We assess requests under the conditions of the applicable law. Account deletion and the applicable retention exceptions are described in section 7.
United States. Tutila does not sell personal information or share it for cross-context behavioral advertising, and does not use targeted advertising. Service disclosures to trip participants and providers still occur as described in section 6. Where your state law provides rights to access, correct, delete, obtain a copy, use an authorized agent or appeal a refusal, contact privacy@datika.io; identify an appeal as such. We do not discriminate for exercising applicable rights. These statements do not assume that every state statute applies to Datika.
Canada. You can contact privacy@datika.io to request access or correction, raise a privacy concern or discuss withdrawal of consent and its consequences for a feature. Overseas providers may be subject to lawful access by authorities in their jurisdictions. You may contact the relevant federal or provincial privacy commissioner where applicable.
Australia. Where the Australian Privacy Act applies, you may request access or correction and complain to privacy@datika.io. We assess the complaint and respond within the applicable requirements. If it remains unresolved after a reasonable opportunity to respond, you may complain to the Office of the Australian Information Commissioner. Overseas recipients and known processing locations are described in section 6.
Israel. Information is provided voluntarily unless a specific law requires otherwise; feature requirements and consequences of not supplying information are explained above. You may request inspection and correction under applicable Israeli privacy law using privacy@datika.io. Datika LTD is the controller identified in section 1.
10. Children and information about other people
Tutila is intended for people aged 18 and over. People under 18 must not create an account or participate through a Tutila profile. Organizers must not create profiles for younger children or use another person’s account to bypass this limit. The age limit does not remove any additional protections or authorization requirements applicable to minors where they live.
If you believe this Service has received a child's information without the required authorization, contact privacy@datika.io so we can investigate and take appropriate action.
If you provide information about another person, you must have the necessary authority and comply with applicable law. We still have our own responsibilities for any processing we carry out.
11. Changes to this policy
Each Service notice identifies its release and effective date. Shared wording may change across Datika products together. If a change materially affects your information or choices, we give the notice and obtain any consent required before the affected processing starts. Publishing a revised notice alone does not authorize a new use of information already collected.
