TimoBy Amotion AI

Timo Labs › Privacy

Privacy notice

Last updated 26 September 2026. AMOTION ARTIFICIAL INTELLIGENCE DEVELOPING LLC (Amotion AI), Trade Licence 1240571, Office G01-620, Dubai Investment Park 1, Dubai, United Arab Emirates, operates TimoLabs and is responsible for the personal data described in this notice.

Information we collect

Consultant enrollment collects your name, personal email address, city and country, and the professional profile links or CV you provide. You must provide at least one LinkedIn profile, GitHub profile or CV. For LinkedIn discounts claimed before 21 October 2026, we collected the published post URL. Agreement signing collects your legal name, residential address, typed signature and signing confirmation. We retain the agreement version, document reference, signing confirmation and timestamp, signed document and payment records. The agreement becomes binding only after payment confirmation; a document signed before payment is held pending payment. Both parties receive the finalized countersigned copy only after payment confirmation. Stripe handles payment; Timo does not receive your full card details.

We also keep support messages, invitation and onboarding delivery records, membership and assigned-address details, payment and refund status, and certification or badge evidence you provide. Where you use an available assessment or mock exam, we keep the submitted work and results. Historical cohort records remain subject to the retention limits below.

Where profile and opportunity features are available, we collect the professional details, skills, work samples and credentials you choose to submit, your visibility choice, credential verification status and your communications about opportunities. Membership does not itself create an employment or consulting engagement. Do not submit another employer's or client's confidential information, personal data or intellectual property without authorization.

The homepage employer form collects your name, company, work email, project or consulting requirement, and required skills and experience. We also process further details you choose to provide in an enquiry or subsequent correspondence.

How we use your data

How we use candidate data

We use consultant profiles for the stated purposes of platform administration, credential verification, enterprise discovery and opportunity matching. Under the consultant agreement, a profile is created after certification evidence has been verified. When profile activation is available, you choose Visible or Invisible and may request a later change. A Visible profile may be accessible to prospective clients, other internet users and search engines. An Invisible profile is not published for public discovery. We do not publish your CV, residential address, signature or payment records as part of a public profile. Contact details are shared for an engagement conversation only with your agreement.

Assessment records

Records from assessments you take are stored with your application and may be considered for relevant opportunities. You may request access, correction or deletion by writing to poorna@timolabs.dev, subject to the retention requirements below. This notice covers Timo profile and assessment features and does not change the services or access period agreed at enrollment.

Who receives information

We use Google Workspace to administer assigned Amotion addresses and deliver authorized messages to your personal inbox. Authorized Amotion administrators manage these addresses, and an Amotion administrative mailbox may also retain copies of messages delivered through them, including sign-in codes. An assigned address is not a private personal mailbox and must be used only for the services Timo expressly authorizes.

We use Google Sheets and restricted operational records to maintain applications, invitation delivery, payments and onboarding status. Authorized personnel can access the information needed to administer those services.

When you register with Anthropic, OpenAI or another authorized provider, that provider receives the information you submit and processes it under its own privacy terms. We may share the details needed to support an access or credential issue you raise. Providers and their exam or credential partners control their own accounts, assessments and credential decisions.

Where a provider uses Credly, badge issuance and the information required for it are governed by that provider's and Credly's processes. Resend delivers application acknowledgements, enrollment invitations, signed agreement copies and onboarding emails, as well as enquiries to Timo. The candidate and Timo receive the same finalized signed agreement only after payment confirmation. Our payment provider processes your payment on Amotion's behalf. Amotion AI operates the service. Our email delivery, cookieless analytics, hosting and payment processing run through service providers acting on our instructions.

We share professional profile information for discovery, matching and shortlisting in accordance with the visibility and sharing choices described above. We share contact details only after you agree to the specific engagement conversation. Candidates can withdraw consent by email to poorna@timolabs.dev.

Website analytics and Session Replay

This site uses PostHog in cookieless mode to measure page views and named actions such as viewing prices, opening the application form and sending a request. PostHog itself uses memory-only persistence, creates no analytics cookie or local-storage identifier, disables automatic click capture and does not record sessions. Timo keeps a random anonymous journey identifier in your browser tab’s session storage to connect page visits and actions during that visit. It expires after 30 minutes of inactivity and is removed when the tab closes.

Timo automatically stores a random first-party browser identifier and a limited history of public pages in your browser’s local storage to understand which pages and referring websites help people enroll. Each history covers a maximum of 30 days from its creation. Returning visits do not extend this period. Expired history is not reused: your next visit starts a new history with a new browser identifier. This history can connect visits across tabs and browser restarts in the same browser. It is a browser-level observation, not proof that visitors are the same person.

The browser history records the first observed public page and source, the latest external source, the sanitized public referring hostname (without its path or query), separate campaign and post labels when supplied through campaign tags, and up to 32 distinct public pages with observation times. Google, Bing, LinkedIn, YouTube and Instagram referrals can be recognized without campaign tags; other public referring hostnames can identify a learner’s blog or another referring website; a missing referrer means direct or unknown. We do not store form answers, names, email addresses, phone numbers, signatures, private enrollment URLs, query strings or tokens in this history, and do not use device fingerprinting. Blocked or cleared storage, private browsing and unrecognized devices can leave gaps in measurement.

A previously saved decline continues to disable this browser history until its original 30-day choice period ends. When local storage is blocked or unavailable, measurement uses the short-lived tab history described above, or memory for the current page if tab storage is also unavailable. You can remove locally stored history through your browser’s site-data controls. Deleting Timo’s site data removes the browser identifier, history and saved choice; visiting again starts a new history unless storage is blocked. This does not delete attribution already saved with an application or completed order; contact us to make a data request. This measurement does not determine your enrollment, payment or access.

When you apply, we save a validated attribution snapshot with your application and retain the original observed discovery information when you later use your private enrollment link. A completed order keeps its own snapshot. Reports distinguish first observed pages, other observed assisting pages and incomplete or unknown history. An observed visit does not prove that a page caused a purchase; unrelated anonymous activity on another device is not linked to your application.

Timo uses Microsoft Clarity, a Microsoft website analysis tool, on its public pages and on the page where you review and sign your consultant agreement before paying through Stripe, our payment provider. Clarity creates heatmaps showing where visitors click and scroll, and recordings that let the Timo team watch how a page was used. This helps the team find problems with navigation and enrollment. Timo has configured Clarity not to place analytics or advertising cookies in your browser.

Recordings can show the agreement text, notices and error messages displayed on the enrollment page. Timo does not hide this displayed text, including any personal details that appear in it, such as your name, address or typed signature. Microsoft Clarity automatically hides the contents of input boxes and dropdowns. Timo cannot turn off that feature. A detail hidden inside an input box can still appear in a recording if the page also displays it outside the box. Members of the Timo team who have access to our Clarity account can watch these recordings.

Your invitation link contains a private code that opens your enrollment. Timo keeps this code out of recordings by opening your enrollment at a different web address before recording starts. Enrollment confirmation pages are not recorded. Recording stops before you move to Stripe to enter your card details; Stripe's pages do not appear in Timo's recordings. The retention section below explains how these records are kept. You can contact poorna@timolabs.dev with questions about recording or to request access, correction or deletion of your personal information, as described under Your rights below.

PostHog and Microsoft Clarity process technical request information, including page information, event times, browser and device information and IP addresses. We use these reports to improve the website and enrollment process. See the Microsoft Privacy Statement for how Microsoft handles data collected by Clarity.

Purchase events include transaction and payment-provider references for measuring completed orders. PostHog person profiles are disabled in this website configuration. These references are not direct contact details, but may be associated with an order through restricted operational records. Cookieless analytics still involves processing technical information; it does not mean that all event data is anonymous.

Why we process information

We process information to respond to your application or enquiry, provide the services you agree to purchase, administer payments and agreements, meet applicable legal obligations, and protect the service and resolve disputes where permitted by law. Optional public profile publication and communications follow your choices. Where consent is required, you may withdraw it; this does not remove records we must retain for another lawful purpose.

Retention

Your choices and requests

You may ask to access, correct or delete personal information, change profile visibility, withdraw consent for optional uses, or object to a use where applicable law provides that right. For profile visibility or deletion under the consultant agreement, you may also contact poorna@amotion.ai. Some records may remain where law or a current dispute requires them. Email poorna@timolabs.dev from the contact address used on the request form.

International processing and security

The service and its providers may process information in countries outside your own. We use service providers and access controls appropriate to the information. No internet service can promise absolute security. Keep account credentials and one-time codes private.

Contact

Email poorna@timolabs.dev with a privacy question or request.