Project Privacy Notice

1. Scope and project roles

This notice applies to the paid video-recording project at apply.crossinghurdles.com. Crossing Hurdles recruits and supports candidates. For an open project, after a successfully saved application, an applicant can begin setup by using Minute Data first and then CH Dashboard with the same registered email before recording and uploading project tasks through the app.

Crossing Hurdles is operated by Samvedh Grow Private Limited, T-5, 1104, Tata Primanti, Sector 72, Badshahpur, Gurgaon, Haryana, 122101, India. The company is responsible for the application website and its recruitment records. Contact helpdesk@crossinghurdles.com for privacy matters. This notice also covers existing records when a project is closed; it does not reopen applications.

2. Information this website collects

The application form collects:

• Name, email address, and phone number
• Country or territory of residence and, when a project requests it, the selected state, province, or territory
• Planned activities, phone model, phone-headband status, and weekly availability
• Referral information, when provided
• For a qualifying, successful request for a canonical public HTML page that appears to come from a person, a first-party, privacy-minimized page-open event record containing the public page path, time, country code, UTM source, medium, campaign, term, and content parameters, and the referring website domain when available. Prefetches, redirects, obvious automated scanners, and rate-limited excess requests may be excluded. This record does not use or store a cookie or reusable visitor or session identifier. It does not include application contact fields and is not intended to collect contact details. The record does not store an IP address, precise location, user agent, full referring URL, or raw advertising click identifiers. A short-lived HMAC-derived rate-limit key may be used to enforce request limits without retaining the raw network address. Each recorded page open is counted separately, so the same person may be counted more than once
• Consent confirmation and version, selected language, and, for an application you submit, the first campaign touch retained in a pseudonymous measured session when available, or otherwise the campaign parameters present on the current form URL, together with Google advertising click identifiers, whether a Meta click identifier was present, and the referring website domain. This application-bound attribution is stored with the application even if session measurement is off; the applicant record does not retain a visitor-session identifier
• While measurement is active: a random session identifier, pages viewed, form-funnel stages, language, campaign details, referring website domain, country code, and whether the pseudonymous session led to an application. Visitor analytics do not store your IP address, name, email address, phone number, precise location, user agent, or raw advertising click identifiers
• Google Ads measurement information, which may include page views, conversion events, browser or device information, coarse location derived from an IP address, and advertising identifiers or cookies while measurement is active
• Meta Pixel measurement information, which may include pages viewed, successful application-submission events sent using Meta's standard AddToCart event, browser or device information, coarse location derived from an IP address, and advertising identifiers or cookies while measurement is active
• TikTok Pixel measurement information, which may include Page and page-specific ViewContent events, successful application-submission events sent using TikTok's standard CompleteRegistration event, browser or device information, coarse location derived from an IP address, and advertising identifiers or cookies while measurement is active. Only after an application is saved successfully and while measurement remains active, it may also include a SHA-256-hashed lowercase email address, an E.164-normalized and SHA-256-hashed phone number, and a SHA-256-hashed random application-submission identifier for advanced matching
• The hosting provider supplies a country-level location signal used for aggregate analytics and operational reporting. It is not used to block the application form or determine project eligibility, and this website does not store your IP address or precise location for this purpose

This application website does not ask you to upload and does not store your task videos.

The Referral Rewards portal separately processes the verified referrer email, linked referral emails, accepted-hour snapshots, eligibility, estimated rewards, payout status, and the security records needed to issue and validate short-lived six-digit codes. The dashboard shows this information only after a verified server-side session.

3. How application information is used

Application information is used to:

• Review project eligibility and suitability
• Contact candidates about their application and next steps
• Coordinate onboarding and participant support
• Protect the application process from abuse or fraud
• Understand which recruitment campaigns bring applicants
• Count page loads in aggregate and compare recruitment sources without using a reusable visitor identifier
• Measure pseudonymous sessions, page views, form-funnel stages, traffic sources, country-level performance, and session-to-application conversion rates

A successfully saved application to an open project provides setup instructions. Task availability and payment still depend on project requirements and approval of recorded hours.

The legal basis depends on the purpose and applicable law: processing an application and arranging participation involves steps you request before a contract or performance of a participation agreement; security, fraud prevention, support and limited recruitment reporting involve legitimate operational interests where permitted; accounting and legally required records involve legal obligations. Session and advertising measurement are described separately below, including their default-on setting and how to turn them off. That setting is not an express acceptance by you. Contact us for the basis relevant to your particular information or to object to processing based on legitimate interests.

Cookie-free page counts, optional session measurement and third-party advertising are separate activities. Session identifiers are pseudonymous, not a promise of complete anonymity. Hashed email addresses and phone numbers used for advertising matching may still identify you when matched by an advertising provider. Rejecting optional tracking does not prevent applying, receiving support or accessing eligible referral records.

We also retain application profiles and application history to assess suitability for future opportunities and may contact applicants about relevant roles where permitted by applicable law. Applying, retaining a record or updating this notice does not by itself record consent to future marketing. You can ask us not to contact you about future opportunities, or request deletion, by emailing helpdesk@crossinghurdles.com.

4. Sharing and project services

Crossing Hurdles does not sell application information for money. Optional advertising sharing is described below and may be treated as sharing or targeted advertising under applicable law. Information may be shared only as reasonably needed with the client and service providers that support project hosting, communications, onboarding, security, payments, or candidate support.

This website records the qualifying privacy-minimized, cookie-free page-open events described above for every eligible page request. The records contain no cookie or reusable visitor or session identifier and are not designed to identify a person or link separate visits. When you submit the form, the first campaign touch retained in a pseudonymous measured session when available, or otherwise the current form URL's campaign details, together with advertising-click context and the referring website domain, are stored only with that application so recruitment sources can be compared; while session measurement is active, the form also sends a pseudonymous visitor-session identifier with the application so the server can mark that session as converted. The identifier is used during submission processing but is not retained in the applicant record, and the visitor-session record does not contain the applicant's contact details. Session and advertising measurement are active by default unless you turn them off in Privacy choices or your browser sends Global Privacy Control or Do Not Track.

While measurement is active, this website uses a random identifier for a session that ends after 30 minutes of inactivity and no later than 24 hours after it begins. Session records contain campaign details, the referring website domain, public page paths, form-funnel stages, language, country code, timestamps, and application conversion status. They do not contain your contact details, full referring URL, IP address, precise location, user agent, or raw Google Ads click identifiers.

Google Ads is used to measure which recruitment campaigns lead to applications. The Google Ads tag and conversion measurement are active by default while measurement is enabled and may use cookies or identifiers. Ad-user-data use, ad personalization, and analytics storage remain denied. Global Privacy Control, Do Not Track, or turning measurement off keeps the tag disabled. You can change your choice at any time using the Privacy choices button.

Meta Pixel is used to measure visits from Meta campaigns and successful application submissions. PageView and AddToCart events are active by default while measurement is enabled; AddToCart represents a successfully saved application and is not sent for a failed or incomplete submission. Meta may use these events and cookies or identifiers for advertising measurement and optimization under its terms. Global Privacy Control, Do Not Track, or turning measurement off keeps the Pixel disabled, revokes Pixel consent, and removes the site's accessible Meta measurement cookies.

TikTok Pixel is used to measure page visits and successful application submissions. Page, page-specific ViewContent, CompleteRegistration, and advanced matching are active by default while measurement is enabled; CompleteRegistration represents a successfully saved application and is not sent for a failed or incomplete submission. After an application is saved successfully, and only while measurement remains active, the browser lowercases the email address, normalizes the phone number to E.164, trims a random application-submission identifier, and hashes each available value with SHA-256. Only those hashes are passed to TikTok identify immediately before CompleteRegistration; that identify call never contains the raw email address, phone number, or submission identifier, and this website does not log or persist the tracking hashes. TikTok may use the events and hashed identifiers for advertising measurement, matching, audience creation, and optimization under its terms. Global Privacy Control, Do Not Track, or turning measurement off keeps the Pixel disabled, revokes Pixel consent, and removes the site's accessible TikTok measurement cookies.

Six-digit referral verification codes are sent through the site's configured Google Workspace account. Referral Rewards routes do not initialize advertising pixels or send referral-route events or details to Google Ads, Meta Pixel, or TikTok Pixel. The referrer email and verification code are not placed in the page URL or browser storage. The browser receives referral details only from a server-side validated snapshot after verification; it never fetches the underlying tracker or contribution system directly.

The sample video is served directly from this website and starts automatically without sound on project pages. You can pause it or use the player controls at any time. If you choose the Google Drive fallback link, Google may process connection information and set cookies under its own terms.

Cloudflare provides hosting and security services and may set strictly necessary security cookies to identify malicious traffic and keep the website available.

CH Dashboard is our website label for an external client-operated onboarding service; it does not mean Crossing Hurdles owns that service. Information entered directly into Minute Data or CH Dashboard is handled under the notices and agreements of those services. Review their operator information, privacy terms and recording agreement before creating an account or uploading recordings.

External onboarding and recording services linked in your project instructions are operated separately by the project client or its service providers. A Crossing Hurdles button label does not change their operator. Review the destination's privacy notice and recording agreement before entering information there; contact our support team if those details are missing or unclear.

Applicant information is copied to access-controlled Google Sheets for recruitment operations. Google Workspace supports these spreadsheets, support communications and verification emails. Authorized staff may also use restricted exports and recovery backups. These copies are separate from the website database.

Joining a linked WhatsApp group is optional and is governed by WhatsApp's privacy terms and group settings. Information you share there can be seen by other participants. Do not post identity documents, verification codes or sensitive application details in a group; contact support privately instead.

Our website operator is based in India. Hosting, communications, advertising and client onboarding may involve processing outside your country. The applicable transfer requirements depend on the service and destination. Contact helpdesk@crossinghurdles.com to request information about relevant recipients, processing countries and transfer safeguards; this notice does not claim that every destination has equivalent privacy laws.

6. Application-record retention

Application profiles, including existing applications and their associated application history, are kept in the live website database for recruitment and consideration for future opportunities, with no fixed automatic age-based deletion period. This does not mean every record must be kept forever: deletion requests, legal requirements and reviews of purpose and necessity may require removal or restricted use. Privacy-minimized page-open events and measured first-party traffic records are scheduled for deletion once they are older than 13 months. Maintenance processes eligible records in limited batches; a backlog may require multiple runs, and failures can delay completion. These automated traffic thresholds apply only to the live website database, not to the separate copies and referral/payment records described below. Project recordings are not submitted through this website; their retention is governed by the separate project-specific onboarding agreement.

Referral verification codes expire in five minutes, and verified Referral Rewards sessions expire after the configured session period, 30 minutes by default. Expired, used, or replaced code records, expired or revoked session records, and old rate-limit records are removed on the automated cleanup schedule after the shortest operationally useful period. Payout ledger and audit history may be kept longer when needed for payment administration, accounting, disputes, or legal obligations.

The absence of an automatic application expiry and the 13-month traffic threshold above describe the live website database. Deletion there does not automatically erase Google Sheets, downloaded exports, recovery backups, messages or records held independently by an onboarding service. Those copies require a separate retention or deletion review. A deletion request should identify the application and any known copies so support can coordinate the review with the relevant systems and recipients.

Referral contribution records, payment ledgers and related audit records are separate from automated traffic and security cleanup. Retention may depend on an active claim, payment reconciliation, a dispute or a legal obligation. Contact support for the applicable period and deletion options. We do not promise immediate removal from every backup or from an independently operated service.

7. Your questions and choices

To ask about, correct, or request deletion of application information, or to stop receiving recruitment messages, email helpdesk@crossinghurdles.com from the address used in your application.

Depending on applicable law, you may request confirmation of processing, access or a copy, correction, portability, information about recipients, restriction, anonymization or deletion, and review of applicable automated decisions. You may object to processing where the law permits and turn optional tracking off through Privacy choices. Where processing relies on consent, you may withdraw it without affecting the lawfulness of processing before withdrawal.

Send privacy requests to helpdesk@crossinghurdles.com. If you no longer have access to your application email, explain this so support can arrange proportionate identity verification. Do not send passwords or verification codes. Requests are handled within applicable legal time limits; any required retention or other lawful limitation should be explained in the response. You may complain to your relevant data protection authority, including Brazil's ANPD where applicable.

8. Updates to this notice

If this notice changes, the updated version and effective date will be posted on this page. Material recording terms must still be presented through the project-specific onboarding agreement before recording begins.