Privacy policy

1. Who we are and how to contact us

Timule is operated by LEGACY LAB LTD, a company registered in England and Wales with company number 17082307. Our registered office is 71–75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ. In this policy, “Timule”, “we”, “us” and “our” mean LEGACY LAB LTD.

We are the controller of the personal information we use to provide and administer Timule. This means that we decide why and how that information is processed. Some technology providers process information on our instructions, while others also process information independently for their own services, as explained in sections 9 and 10.

For privacy questions, requests or complaints, email admin@legacylabgroup.com or write to our registered office, marked “Timule privacy”. You do not need a Timule account to contact us. Please do not send passwords, authentication codes or unnecessary identity documents.

This policy covers the Timule mobile application, its supporting services, memory invitation links, and correspondence with us about Timule. It does not automatically cover unrelated Legacy Lab products or separate website features. Features and providers can differ by device, operating system, release and country.

This policy explains our handling of personal data in connection with Timule and your rights under applicable data-protection law, including the UK GDPR and the Data Protection Act 2018, as amended, and the EU General Data Protection Regulation where it applies. Nothing in this policy or our Terms and Conditions limits your statutory data-protection rights.

2. The important points

Timule lets you create, place, share and revisit memories connected to places. You can organise memories in journeys and interact through supported social features. Your content, the location attached to it, and your chosen audiences are different from your private account and eligibility records.

Location has several distinct uses: placing and finding memories; distance-based features and optional nearby reminders; and a separate, targeted memory-creation analytics process. That analytics helps us understand whether people create memories while at a place or about another place. It is for product development, not advertising profiling.

An AR session can involve Google processing camera imagery and location even when you do not upload a photograph or video. Permission to use your photo library does not mean that your whole library is uploaded.

Local caches help screens and media load more quickly. Some persist between app launches or after sign-out. A cache does not create a continuing permission to view someone else’s content.

Uninstalling Timule, revoking a share, deleting a memory and deleting an account are different actions. Some original-memory timeline information and comment text can remain after ordinary deletion actions. Section 12 explains these effects and how to request removal of remaining personal information.

3. Information you and other people provide

Account, sign-in and eligibility information

We process your email address or supported authentication identity, internal user identifier, username, profile name, sign-in provider, verification status, account status and information needed for account recovery or provider linking. Timule supports email/password sign-in where available, Google sign-in and Sign in with Apple. Firebase Authentication handles the associated authentication processing.

We ask for your date of birth to check age eligibility. A private account-setup record stores your declared date of birth, age band, eligibility result, declaration method, check time and age-policy version. This is not merely an age-range check. Your date of birth and email address are not part of your ordinary public profile. An eligibility check can create a limited record even when you are not eligible to continue.

We also record the versions and times of your acceptance of the Terms and Conditions and Community Guidelines, your acknowledgement of this Privacy Policy, the relevant locale, and completion of legal onboarding. These are account and compliance records, not product analytics.

A supported sign-in identity, username, profile name and necessary eligibility and account records are required to establish and operate an account. A profile name does not have to be your legal name, but it must comply with our rules against impersonation. Profile images and additional profile content are optional.

Memories, media and social information

We process photographs, videos and their soundtracks, captions, comments, replies, profile content, and journey titles and covers that you submit. Related information includes ownership, identifiers, timestamps, thumbnails, media format and size, locations, map or AR placement, visibility settings, journey associations, and links between original memories and revisits.

Social and sharing information includes followers, following, follow requests, likes or reactions, saved items and collections, journey ownership and membership, invitations and join requests, direct-share recipients, invitation claims and revocations, blocks, hidden-content choices and notification preferences. Journey activity records and revisit relationships also allow those features to operate; their existence does not mean every action is recorded as a separate analytics event.

Information about you can come from another user’s content, comments, invitations, sharing choices or reports. For example, another person can include you in a photograph or identify your account in a report. We also receive the information supplied by your chosen sign-in provider and information generated by the device and services used to deliver Timule.

Support, reporting and moderation

When you contact us or submit a report, we process your contact or account details, the target content or account, your reason and explanation, evidence you choose to supply, timestamps, case status, correspondence and moderation decisions. A limited contextual snapshot can include the relevant caption, comment or reply, author information, place name, and memory or journey identifiers.

For supported location-related reports, you can voluntarily provide a current position through the reporting feature. A separate, validated service calculates distance from the reported memory and retains derived distance, accuracy and timing information, rather than storing the raw reporter coordinates in that report calculation. This is not permission to attach arbitrary GPS histories to a report.

Please avoid submitting unnecessary sensitive information. Content can reveal health, religion, relationships or other private matters. Do not disclose someone else’s private information without a lawful reason. Where information falls within a legally protected category, its processing also requires an applicable condition under the relevant law.

4. Technical information, notifications, search and suggestions

Technical and security information

Timule and its supporting infrastructure process information needed for connectivity, authentication, app integrity, abuse prevention, delivery and reliability. This can include IP addresses, installation or device-related identifiers, operating system and app version, service requests, timestamps, permission or capability status, region, locale, errors and diagnostic information.

We do not intentionally maintain public IP addresses as an account-level product-analytics profile. Network infrastructure and providers can nevertheless process IP addresses for communication, security and service operation. Firebase App Check and account-security records are separate from the targeted product analytics described in section 6.

Push delivery and in-app notifications

To deliver push notifications, we process an installation identifier, the associated account identifier, a push-delivery token, device-binding status and relevant creation or update times. Installation credentials used by the notification-device registry are stored as hashes on the backend rather than as raw credentials. A push token is a delivery address for an app installation, not a public profile identifier.

Signing out deactivates the relevant installation’s account binding. Invalid or stale tokens can be deactivated or removed, and account deletion releases the relevant device bindings. The notification-device registry does not store your GPS position; nearby-location calculations are handled separately.

In-app notification records can include a notification type, recipient, actor, relevant memory or journey, timestamp and read/unread status. Preferences control supported categories, actors or journey notifications. Disabling push notifications does not itself delete these records. Information shown in a notification can be visible on a device’s lock screen, depending on its notification settings.

Searches and suggested people

Search terms or tokens are sent to our services when needed to search for people, memories or journeys. A separate recent-search list is stored locally for the relevant account. Clearing that list is not necessarily deletion of information lawfully retained elsewhere, such as necessary security records.

Search results can depend on your selected filters, access rights, and location or distance radius where used. Suggested recipients or audiences can depend on followers, following, journey membership and recent journey participants. We do not use general screen-view or button-tap histories to personalise those suggestions in the current release.

These functional suggestions are distinct from advertising profiling. Our AR provider’s own usage and diagnostic processing is explained separately in section 7.

5. Location, maps and nearby reminders

The location attached to a memory

A memory’s location can be selected on a map, recorded when creating or placing it, or represented by an AR anchor. It can include coordinates, a place name and placement information. The selected location is not necessarily your current position when you upload the memory.

We store the memory’s location to display it on maps, calculate distances, support AR and revisits, and make the location-linked experience available to its authorised audience. It follows the memory’s normal content lifecycle, not the shorter lifetime of a temporary analytics location snapshot.

People who can view location-linked content may infer where you or someone else has been. Review your audience before including a home, school or other sensitive place. Withdrawing device-location permission does not remove locations already attached to content.

Your device’s current location

With the relevant permission, Timule uses approximate or precise device location for map positioning, distance-based searches, finding nearby memories, AR and revisit features. Some functions depend on being close to a place and may not work accurately with approximate location alone. You can refuse or change permissions in device settings; this can make affected features unavailable or less accurate.

Nearby reminders when the app is not open

When you enable nearby memory reminders and grant the relevant permission, Timule can use location while the app is closed or not in use. This helps Timule notify you when you return close to an eligible memory.

The device can perform proximity or geofence checks and send a current position, location accuracy and relevant request information to our backend. The backend calculates distances and checks eligibility before deciding whether to deliver a reminder. A coarse area key, timing and delivery-control records can help avoid repeated notifications. This processing is not entirely on your device.

The feature is designed for bounded proximity checks, not for maintaining a continuous GPS movement history. Its actual operation depends on your settings, connectivity and operating-system restrictions. Turning it off or withdrawing background-location permission stops future use of that permission for reminders; it does not erase existing memories or previously delivered notifications.

6. Targeted product analytics

Why we use analytics

We use targeted first-party analytics to understand how features are used, evaluate memory creation, diagnose product behaviour and inform improvements to Timule. “First-party” means that this is Timule’s own analytics process, although service providers can process the information on our behalf.

Our current dedicated product-analytics process focuses on whether a memory is created near the place where it is positioned or relates to a different location. This helps us understand in-the-moment and retrospective use. It is not a general system for tracking every screen, button or action, and it is not used to build advertising profiles. Broader analytics about revisit or journey usage may be considered in future, but are not represented here as already implemented.

How the current process works

When a memory is created, the app can use a snapshot of the device’s location for this separate analytics purpose. The backend checks that the authenticated account owns the memory, compares the snapshot with the memory’s placement location, and calculates the relationship or distance between them.

The resulting analytics record can include the memory and account identifiers, capture status, timing, accuracy, placement type and derived distance. Because it remains linked to identifiers, we do not describe it as anonymous.

The calculation service is designed not to persist raw creation latitude and longitude in the resulting analytics record. Those coordinates are different from the location deliberately stored as part of the memory itself.

Temporary retry data and deletion

A local queue can hold the creation-location material while delivery is pending. Entries are configured to stop qualifying for retry after approximately 72 hours or after reaching the retry limit. They are removed following successful delivery or when the relevant cleanup runs; an inactive device cannot necessarily perform cleanup at the exact expiry time.

Derived analytics records are held separately and are not subject to that same local retry period. Their retention is governed by section 12. The account-purge process includes memory-creation analytics linked to the account.

Your choices

The legal basis and applicable consent requirements are explained in section 8. Granting location permission for a map or reminder is not, by itself, consent to a separate analytics purpose. You can contact our privacy address to object to analytics based on legitimate interests, withdraw consent where applicable, or request deletion of linked analytics information. Changing device permissions can affect location-based features as well as future access to device location; it does not by itself erase records already held.

7. Camera, media, AR and biometric app lock

Media you select or capture

Camera, photo/video-library and microphone permissions support capturing, selecting, editing, attaching and uploading media. Microphone access can provide sound when recording video. Saving media to your device may require separate permission.

We process the media you choose to submit to Timule and the information needed for that action. Photo-library permission does not mean that your entire library is uploaded. Where available, your device’s limited-access controls let you select which items the app can access.

Augmented reality and provider processing

Timule uses Unity-based AR components and supported Google ARCore or Apple ARKit technologies. AR uses camera, movement and orientation information to place digital content. Geospatial features use Google’s ARCore Geospatial service. Activating AR is separate from uploading a memory.

Google’s ARCore disclosures describe collection of Google-account or device identifiers, diagnostics and API-use information for analytics, operation and improving AR. Geospatial processing also involves precise location and camera video. Google describes geospatial video as temporarily stored and marked for deletion, with anonymised information extracted from it potentially retained for improving its services. We therefore do not describe all AR processing as on-device or memory-only processing.

Opening AR does not, by itself, publish a video memory to your account. Google’s independent processing is governed by its privacy information. See Google’s explanation of AR data handling and the Google Privacy Policy. The relevant in-app AR disclosure also applies when activating the feature.

Biometric app lock

The optional app lock uses biometric authentication provided by your device. Timule receives capability information and the authentication result, not your raw fingerprint template or Face ID facial template. The device handles those templates. App lock controls access to the interface; it does not make all stored information end-to-end encrypted or replace account security.

8. Why we process information and our legal bases

For processing subject to UK or European data-protection law, the following legal bases apply. A device permission, acceptance of Terms and acknowledgement of this policy are not interchangeable forms of consent.

Providing the service you request — contract. Necessary account, authentication, content, recipient and journey information enables us to operate your account, store and display memories, fulfil search and sharing instructions, provide supported social features, maintain your settings and process account closure. We do not make unrelated analytics necessary merely by mentioning it in the Terms.

Age eligibility and legal records — legitimate interests, and legal obligation where applicable. We use eligibility and policy-version records to enforce our minimum age, protect users and demonstrate the agreement or notice provided. Where a particular law requires a record, that processing is based on the relevant legal obligation.

Safety, security and support — legitimate interests. We use relevant technical, account, content, reporting and relationship information to prevent unauthorised access and abuse, enforce proportionate rules, investigate reports, handle support and protect people. We consider necessity, proportionality and the effect on individuals, including children. You can object to processing based on legitimate interests.

Product improvement — legitimate interests where permitted; consent where required. Our interest is understanding and improving the service, including the targeted analytics in section 6. We rely on consent for analytics-related device access or location processing where the applicable law requires it. Legitimate interests do not override a separate consent requirement or make every first-party analytics activity exempt from device-access rules.

Optional device features — consent where required and contract for the requested function. We use the information needed to perform a location, camera or other feature you request. Where the applicable privacy or device-access rules require separate consent, it must cover the specific purpose. You may withdraw consent without affecting processing that was lawful before withdrawal.

Legal duties and claims — legal obligation or legitimate interests, as applicable. We process necessary information to respond to valid legal demands, fulfil rights requests, make legally required safety reports, establish or defend claims, obtain professional advice and manage a genuine business transfer. Additional legal conditions apply to protected categories of information.

Timule’s age gate compares a declared date of birth with the applicable minimum age. Access controls use audience, membership, sharing, blocking and account-status information to decide what an account can see or do. These processes can prevent access. Contact us to challenge an incorrect result and request human review. We do not describe ordinary distance filters or suggested recipients as decisions about credit, employment, insurance or similar matters.

9. Who receives information

Other users and authorised audiences

Your username, profile name, image and other profile information can be visible through the service. Memories and associated locations are disclosed according to their audiences and available access routes, such as public access, selected people, journey participation or a direct share.

Direct sharing is an additional access layer; it does not necessarily change the underlying privacy setting. Revoking one share or removing a journey membership may leave a different, independent access route. Use the memory’s audience, journey-management and “Shared with” controls together.

An external invitation can be forwarded. The first eligible signed-in person who claims it can become its recipient, even if that is not the person originally intended. After a successful claim, the invitation is consumed and access is associated with that account. The owner can review and revoke the grant.

A person who has already seen content can retain an independent copy. Revocation cannot retrieve copies outside our control. We remain responsible for access controls and processing within our control. Private sharing restricts the audience; it does not prevent authorised operational or legal access where needed.

Technology providers and authorised personnel

We use Google/Firebase for authentication, databases, storage, server functions, app integrity and push delivery; Google for supported sign-in, maps and ARCore; Apple for supported sign-in, platform services, ARKit and notification delivery; NAVER Cloud for NAVER map components where used; and Unity technology for AR. Our business email arrangements support correspondence and moderation review, including Google Workspace where used.

Providers receive information needed for their role. A Firebase cloud service handling our content is not automatically the same as an independent map or AR service handling its own operational information. Where a provider acts as our processor, the relevant contractual instructions and safeguards govern that processing. We do not suggest that every provider receives every category of information in this policy.

Appropriately authorised people can access relevant information for support, moderation, security, service operation or legal matters. Report information can be sent to our business email system. Necessary information may also be disclosed to advisers, courts, regulators or competent authorities where required or otherwise lawfully justified.

For a genuine financing, reorganisation, merger or transfer of the business, relevant information may be disclosed under appropriate confidentiality and privacy safeguards. This does not give a recipient unrestricted permission to use private content for unrelated purposes.

Google Play’s “shared” label has specific definitions and exceptions. A store label stating that data is not “shared” does not mean no cloud provider processes it or that content you choose to share cannot reach its recipients.

Government, regulatory and law-enforcement requests

We do not disclose user information merely because a government, regulatory or law-enforcement authority asks for it. We review requests for appropriate legal authority, scope, necessity and proportionality, and may reject, challenge or seek to narrow requests that are invalid, excessive or otherwise inappropriate.

Where disclosure is legally required or otherwise lawfully justified, we disclose only the information reasonably necessary for the relevant purpose and take appropriate steps to protect it during disclosure.

Where legally permitted and appropriate, we may notify the affected user about a request or disclosure. We may delay or withhold notice where prohibited by law, where notice could prejudice an investigation or legal process, or where an emergency or serious safety risk requires otherwise.

Nothing in this section prevents Timule from making a disclosure or report that we are legally required to make, including applicable child-safety or other mandatory reports.

10. International processing

Timule is operated by a UK company, but its information processing is not confined to the UK. The providers and services described above can involve the UK, the European Economic Area, the United States, South Korea and other countries where the relevant infrastructure or support is located. In particular, Firebase states that its Authentication service processes data in the United States. Selecting a region for one database or server function does not locate every provider’s processing there.

Where UK or European transfer rules apply, a restricted international transfer requires an applicable adequacy decision, appropriate safeguards or a permitted statutory exception. Relevant safeguards can include the EU Standard Contractual Clauses, a required UK Addendum, or the UK International Data Transfer Agreement, with any necessary assessment and additional measures. Acceptance of our Terms is not blanket consent to international transfers.

You can ask our privacy contact about the applicable recipients, countries and transfer safeguards, and request a copy or explanation of relevant safeguards with confidential information appropriately protected.

Provider information is available in the Firebase privacy information, Google Privacy Policy, Apple Privacy Policy, NAVER Cloud Privacy Policy and Unity Privacy Policy. These policies explain the providers’ processing and do not replace our responsibility for Timule’s own activities.

11. Local storage, caching and security

Timule uses local storage to maintain sessions, remember preferences, manage unpublished content and pending uploads, keep recent searches and improve loading performance. Some information exists only in memory during a session; other presentation records and media caches can persist between app launches.

Depending on the feature, local information can include account, memory and journey identifiers; preview text; thumbnails, covers or media; author/profile details; audience and access metadata; map position and view settings; memory locations; and temporary recovery or analytics requests. Authentication and security-related local storage is used for those functions rather than automatically becoming product-analytics data.

Account-scoped presentation caches are associated with the relevant account and checked on restoration. User-scoped in-memory presentation state is reset on account changes. Some persistent account-scoped caches can remain after ordinary sign-out so that the same account can restore previously loaded information. Signing out is therefore not a complete deletion of all device files.

A previously loaded screen can be shown while service information refreshes. Cached records are not independent authority to disclose content after access has changed. Deletion, revocation, changed audiences, blocking and changed journey membership can lead to content being hidden, replaced or removed as current information is received and checked. An offline device may not immediately receive a change; this does not remove our responsibility for reasonable access controls.

Retention differs by storage type. Some records are replaced on refresh or removed by cache limits, expiry checks, corruption handling, account-related cleanup or operating-system storage management. Others, such as unfinished content or preferences, serve a different purpose and can remain longer. There is no single fixed expiry time covering all locally stored information. A refresh interval is not necessarily a deadline for physically deleting a file.

Clearing device app data can remove local information, including unfinished work, without deleting your server-held account. Device backups, exported media and copies independently retained elsewhere are separate from the working cache. See section 12 for account deletion and residual information.

We use measures intended to protect information, including authentication, access restrictions, app-integrity checks and protected communications with supporting services. The notification-device system stores credential hashes rather than raw installation credentials on the backend. These measures do not guarantee absolute security or that every local file has additional application-level encryption. Keep your device and credentials secure and tell us about suspected unauthorised access. We provide legally required incident notifications where applicable.

12. Retention and deletion

We retain personal information for the purpose for which it is needed and no longer than justified. Relevant criteria include active accounts and content, the operation of a shared feature, completion of a request, unresolved reports or claims, security needs and specific legal preservation duties. A retention exception is not permission to keep an entire account indefinitely.

Account and content records. Account information, memories and associated media are generally retained while the account and content remain active, subject to deletion choices and the qualifications below. Linked analytics records are retained separately from temporary raw-location retry data and remain subject to necessity and account-purge handling.

Permanent account deletion. When you are signed in to Timule, you can permanently delete your account after completing the confirmation steps. There is no waiting or recovery period. “Immediate” does not mean simultaneous erasure from every system.

The permanent account-purge process includes linked memory-creation analytics and releases relevant notification-device and account-identity bindings. Cleanup can involve queued work and retries. Local storage, backups, retained evidence and independent contributions have the separate considerations described in this policy; we do not promise that every copy disappears when the button is pressed.

Individual memory deletion and revisits. Deleting an original memory with a revisit chain can preserve a timeline snapshot containing a thumbnail, caption, identity references, creation time and location, although the original full memory is no longer available. Other people’s independently created revisits are not automatically deleted. A retained snapshot can still contain personal information and is subject to applicable erasure rights and retention limits.

Comments after account deletion. Comments in surviving discussions can remain with the displayed author changed to “Deleted account”. Removing an author label alone does not necessarily anonymise the text. Where remaining text, snapshots or identifiers are personal information without a lawful retention reason, they are subject to erasure or appropriate redaction under applicable law.

Reports, security and legal records. Limited case information, report evidence, correspondence, request-completion records and security information can be retained where necessary to resolve a case, protect the service, comply with a specific legal duty or establish or defend claims. Access and retention must be proportionate to that purpose.

Backups and external copies. Where a backup cannot reasonably be edited immediately, deleted information is restricted from ordinary use and removed or overwritten through its applicable lifecycle, subject to lawful preservation. Restoration must not silently reinstate erased information. We cannot retrieve copies independently saved by another person or erase records a separate controller lawfully retains for its own purposes.

If you can sign in, open Settings > Account Management > Delete account in Timule and follow the confirmation steps. If you cannot sign in or use the in-app option, use our website deletion request form or email admin@legacylabgroup.com, marked “Timule account deletion”. You do not need to reinstall the app to send a request. External requests require account ownership verification before processing; submitting a request does not immediately delete your account. You can separately identify a retained comment, timeline snapshot or other personal information for an erasure request. Uninstalling Timule alone does not delete your account, memories or in-app notification history.

13. Your choices and privacy rights

You can use available controls to edit your profile, manage memories, review audiences and direct shares, manage journey participation, block or hide accounts and change notifications. Device settings control permissions such as location, camera, microphone, media access and push delivery. Some requested functions cannot work without the information they need.

Depending on the applicable law, you may request access, correction, erasure, restriction of processing or a portable copy of personal information. You may object to legitimate-interest processing, withdraw consent and exercise rights concerning qualifying automated decisions. These rights have statutory conditions and exceptions. We do not treat them as dependent on an unrestricted choice by Timule.

Send requests to our privacy contact. We seek only reasonably necessary identity or authority verification and consider requests by authorised representatives where permitted. An ordinary app download or content export is not necessarily a complete response to a request for your personal information.

For UK and European rights requests, we normally respond within one calendar month, subject to lawful verification, clarification and extension provisions. Where an extension or refusal is permitted, we explain it and the available complaint route. Other countries’ statutory time limits apply where relevant. Ordinary requests are free; any legally permitted charge or refusal must satisfy the applicable conditions.

Exercising a privacy right does not result in unlawful discrimination. A feature may nevertheless stop working where you withdraw information genuinely needed for it. Withdrawal of consent does not invalidate earlier lawful processing.

14. Young people

Timule is intended for people aged 16 and over, or a higher age where applicable law requires it. The age check uses a self-declared date of birth; it is not independent verification of identity or age. Users aged 16 or 17 can still be children under privacy and online-safety law, and their additional protections continue to apply.

If we learn that an account belongs to someone below the applicable minimum age, we restrict access and handle eligibility and account information according to the applicable law. Information without a lawful retention reason is deleted. A young person, parent or guardian can contact us about privacy, an incorrect eligibility result or an ineligible account. Parental approval does not override Timule’s minimum age.

15. United States and other local rights

United States residents

The categories described in this policy include identifiers and account information, age/eligibility information, user content, social and sharing relationships, network or app activity, diagnostic information, geolocation and derived information such as calculated distances. Precise location and account-access information can receive additional protection. Sections 3–12 describe the sources, purposes, recipients and retention criteria.

Depending on your state and whether the relevant law applies, you may have rights to know, access, correct, delete or obtain a copy of information; opt out of sale, targeted advertising or certain profiling; and limit or control sensitive-information processing. An authorised agent can act where permitted. You may also have a right to appeal a denied request. Contact our privacy address with the request or appeal; we explain our decision and applicable escalation options within the relevant statutory period.

Timule’s targeted first-party product analytics are not advertising profiling. We do not treat acceptance of this policy as permission to sell personal information or use it for cross-context behavioural advertising. Disclosures to providers require their own assessment under the applicable legal definitions; a Google Play “not shared” label does not settle that assessment. Any such activity introduced in future would require the applicable notice, choice and other safeguards before it starts.

Browser “Do Not Track” settings are not a universal control for mobile-app permissions, and Timule does not use them as one. Legally recognised opt-out signals, such as Global Privacy Control, are distinct; we give them effect where applicable law requires for processing we undertake. Requests can also be made directly to our privacy contact.

Other countries, including South Korea

Our UK location and the governing-law provision in our Terms do not remove mandatory local privacy rights. Where European law applies, you can complain to the competent supervisory authority, including where you live, work or consider an infringement occurred.

Where South Korean law applies, applicable rights of access, correction, deletion, suspension of processing and withdrawal of consent remain available. Country-specific notices or consents concerning outsourcing, overseas transfers or location services supplement this policy where required. They take priority where mandatory law requires a different approach. Providing an English policy does not remove a right to legally required local-language information.

16. Privacy complaints

Email admin@legacylabgroup.com, preferably marked “Timule data protection complaint”, or write to our registered office. Explain the concern and the outcome you seek. We acknowledge data-protection complaints within 30 days, investigate and respond without undue delay, keep you appropriately informed and communicate the outcome. A complaint that also contains a rights request retains the applicable rights-request timetable.

You can complain to the UK Information Commissioner’s Office or another competent regulator. Contacting us or accepting the Terms does not remove that right.

17. Changes to this policy

We update this policy when relevant processing, features or requirements change. The version number and last-updated date identify this text. We give appropriate notice of material changes and explain when they take effect. A materially different analytics purpose or provider arrangement is assessed before it starts, with a new notice or consent where required.

Continuing to use Timule is not treated as consent to a new purpose requiring a separate choice. Previous versions can be requested from our privacy contact.