Privacy Policy
What happens when you visit, ask Robi a question, apply for an audit or contact us — and how to change your advertising choice.
Visiting the website
Netlify hosts this website and delivers its pages, fonts, images and creator video. To deliver and protect the site, Netlify receives technical request information, such as your IP address, requested address, time of access and browser information; a referring address may also be sent by your browser.
A Netlify Edge Function uses the country supplied by Netlify’s network and any Global Privacy Control signal in the request to select the advertising settings described below. It adds the country code and privacy-signal status to the page; it does not request precise location from your device. Netlify caches separate country and privacy-signal variants. If the country is unavailable or the function fails, the page asks for a choice rather than enabling the United States default.
The fonts, revenue screenshots and video are served as website files. The video may load metadata before you press Play. It is not an embedded player from a separate video service.
Read Netlify’s Privacy Statement and its Data Processing Agreement for information about its services. This website’s legal pages load no advertising tags.
Your audit application
We use your application to review your setup, decide whether we can help, prepare the audit and contact you about it. Typeform provides the application form and processes responses on our behalf. Responses, including applications that end at a qualification question, are stored in Typeform for us to review.
The form opens in a popup when you choose an application button on this page or in Robi. No Typeform library, form or other Typeform resource loads before that click. Opening it connects your browser to Typeform, which receives technical information needed to serve and protect the form, such as your IP address and browser information. Typeform can set functional cookies only when the form is opened. The embed disables Typeform tracking; no separate advertising pixel is configured in the form.
| Information | Purpose |
|---|---|
| Revenue eligibility, revenue range, audience sources and adult-age answers | To check whether the revenue threshold is met, understand your setup and confirm that you are an adult. |
| Whether you show your face and your content category | To understand the content you create after the revenue and age checks. |
| Main challenge | To understand what you need help with. |
| Preferred contact method | Choose iMessage, WhatsApp, Telegram, email or Instagram so we know where to respond. |
| Phone number with country code, Instagram handle, email or Telegram handle | The form shows the contact field for your chosen method. A handle or email is required when shown; the phone field is optional. |
| Name or creator name | Required so we know what to call you. |
| Additional notes | Optional business context before the call. |
Please keep notes relevant to your business and do not include passwords, identity documents or sensitive personal information.
| Field | What it contains and why |
|---|---|
session_id | A random UUID for this browser-tab session, used to connect separate form attempts and advertising events to the same visit. Each submitted response has its own Typeform response identifier; the session UUID is not the submission identifier. |
site_variant | tiemstudios.com (video page, ad domain), so we know which version of the application page you used. |
consent_state | The advertising-permission state when the form opens: accepted for an explicit or remembered acceptance, us_default for the United States default without an explicit acceptance, declined for a decline or remembered opt-out, gpc when Global Privacy Control is enabled, or none when no choice has been made. Closing the banner without choosing keeps the form accessible and does not permit advertising measurement. This field does not grant permission by itself. It is a snapshot at opening and does not update a form that is already open. |
gclidgbraidwbraidfbclidttclidutm_sourceutm_mediumutm_campaignutm_content | Advertising-click identifiers and campaign labels from the page address or this tab’s session storage. They carry values only while advertising measurement is permitted under the choice and country rules below; otherwise they are empty. |
landing_pagereferrer | When advertising measurement is permitted, the first landing address without its fragment and the referring address supplied by your browser, when available. Otherwise, the landing-page field contains only the current origin and path, and the referrer field is empty. |
fbpfbc | The values of readable _fbp and _fbc cookies, when present and advertising measurement is permitted. These identifiers help connect the form response with the browser or advertising click; otherwise the fields are empty. |
If the popup cannot load, the page offers another attempt, a direct link to the form, and email contact with TIEM. The direct link opens Typeform’s website; submissions made there do not trigger this page’s advertising callbacks.
Typeform may save unfinished answers in its own browser storage so that you can return to them. Closing the popup or withdrawing advertising consent does not erase responses already stored with Typeform. See Typeform’s Privacy Policy, Cookie Policy and its explanation of saved progress.
Application eligibility and age
The offer is for creators earning at least $1,000 a month, net after platform fees, averaged over the last three full months across all subscription platforms combined, with Instagram as their main source of new fans. A “No” on the first revenue question ends the application at the below-$1,000 screen. A “Yes” continues to the revenue-range question and the remaining form. The form also asks about other audience sources.
The form asks whether you are 18 or older. A “No” on the age question ends the application at the under-18 screen. The form follows fixed rules, not an AI assessment. The page remembers when the qualifying revenue-range question appears; a successful ending can count as an advertising lead only with that flag. It receives question and ending references from the embed, not your individual answers.
You can close and reopen the form to correct an accidental answer; Typeform may retain previously entered answers. Advertising duplicate prevention does not lock you out of applying. If you want a person to review your situation, email us.
The service and application are for adults aged 18 or older. We do not request your date of birth or an identity document in this form. If a minor has sent us personal information, contact us so we can address its removal.
Robi, the chat assistant
Robi gives automated, predefined answers using local keyword matching. Questions and replies remain in the current page’s memory. They are not sent to an AI provider, Typeform or a live agent, and are not stored in the browser’s local or session storage.
The chat is a second way into the audit: its application button opens the same Typeform popup. Robi does not collect application answers. Your chat transcript is not attached to the form. Closing the chat keeps the conversation on the current page; reloading the page clears it.
Google Ads, Meta and your choice
Advertising measurement helps us understand which campaigns lead to visits and suitable applications. The cookie dialog offers Accept and Decline. Declining does not prevent you from watching the video, using Robi, applying or contacting us.
Country settings and privacy signals
For a visitor identified as being in the United States, advertising measurement starts by default without a banner, unless this browser has a saved decline or sends Global Privacy Control (GPC). A saved decline always takes precedence over a saved acceptance. GPC also takes precedence: no Google or Meta tag is loaded, the dialog explains the signal, and Accept is unavailable while it remains enabled. The GPC decision is saved as a decline. The page checks both the request’s Sec-GPC signal supplied through Netlify and the browser’s globalPrivacyControl setting.
For other countries, or when country detection is unavailable, the page shows the dialog unless it recognises a saved choice. Use Cookie settings to change that choice. The Do Not Sell or Share My Personal Information link saves a decline directly. See Global Privacy Control for information about the browser signal.
Before a decision, and after Decline
Outside the United States, including when the country is unknown, the Google tag loads in advanced Consent Mode v2 unless GPC is enabled. Before it loads, all four signals — ad_storage, analytics_storage, ad_user_data and ad_personalization — are set to denied. They stay denied after Decline. Google can receive cookieless consent and page-measurement requests and technical connection data such as an IP address. The page enables advertising-data redaction and disables URL passthrough. It does not grant advertising-cookie storage while these signals are denied.
The Meta pixel does not load without permission. With GPC, or a remembered decline for a United States visitor, neither external advertising tag loads. Google’s denied-mode requests elsewhere are separate from the site events described below.
While you have not chosen, the page holds its Google and Meta events in an ordered queue in this tab’s session storage, or in page memory if storage is unavailable. This includes form loading and starting, revenue qualification, submission or rejection, video milestones and reaching the final section. No queued site event is sent before permission. Accept sends the queued events in their original order; Decline deletes the queue. New site events are not queued or sent while decline or GPC remains in effect.
When advertising measurement is enabled
After Accept, or under the United States default described above, Google’s advertising storage, advertising user-data and personalization signals become granted. Analytics storage stays denied; this page does not use Google Analytics. The Meta pixel loads and sends its automatic PageView. The advertising services may use cookies and identifiers to measure campaigns and support personalized advertising.
The site is configured for Google Ads AW-18355357345, with lead conversion label QfhxCNbR8NccEKGNwrBE, and Meta pixel 739467762390551.
Google measurement
The page records funnel_opened when a Typeform popup is ready. It records gate_passed_revenue when the Instagram question becomes visible. A revenue or age rejection records lead_disqualified with the corresponding reason. These events are sent only when advertising measurement is permitted, including replay from the undecided queue.
The Google Ads lead conversion requires the successful ending, identified by its reference or the final notes question immediately before submission, and the qualifying-revenue flag for that attempt. Rejections, unknown endings and submissions without that flag do not trigger a lead conversion. The conversion uses Typeform’s responseId as its transaction_id; session_id separately connects it to this browser-tab visit. Missing response identifiers do not produce a conversion.
Meta measurement
The events below are sent only when advertising measurement is permitted. Events recorded before a choice are replayed after Accept. The pixel’s automatic PageView occurs when it loads, including a later permitted page load.
| Event | When it is recorded |
|---|---|
VideoStart | The creator video starts playing; once per browser-tab session. |
Video50 | The playback position reaches 50% of the duration, including seeking forward; once per browser-tab session. |
VideoComplete | The playback position reaches 95% or the video ends; once per browser-tab session. This does not establish that every second was watched. |
ScrollBottom | The final audit section enters the viewport; once per browser-tab session. |
FormLoaded | Typeform’s onReady callback reports that the popup is ready; once per attempt, for diagnostics. |
PotentialLead | Typeform’s onStarted callback reports the first answer; once per attempt, including attempts opened through Robi or Try again. |
QualifiedStart | The revenue-range question shown only after “Yes” to the $1,000 threshold appears; once per attempt. This is the campaign optimisation event. “No” on the first question produces no qualification event. |
Lead | The successful ending is reached with the qualifying-revenue flag for that attempt; once per Typeform response. |
LeadDisqualified | The below-$1,000 ending is reached from the first revenue question, or the under-18 ending is reached from an age question; once per Typeform response. |
The page uses question and ending references, not question titles, to identify progress and outcomes. It records at most one terminal outcome for each responseId. A rejected attempt does not block a later qualified submission in the same browser-tab session. A missing response identifier, missing qualifying-revenue flag or unknown ending produces no lead conversion.
PageView and Lead are standard Meta events; the others are custom events. Video and scroll event IDs use the session UUID plus video-start, video-50, video-complete or scroll. Form loading and qualification IDs use a separate attempt UUID plus form-loaded or gate1. The first-answer ID uses the response identifier supplied by Typeform, or the attempt UUID if that callback has no response identifier, plus potential-lead. Terminal IDs are responseId-lead and responseId-dq. Each site-generated Meta event also carries the session UUID for joining.
These events reveal video or application progress, that the revenue threshold was passed, or a revenue- or age-based rejection. The site event code does not send your name, contact details, notes, exact revenue-range answer, content-category answer or chat messages to either advertising service. Automatic Meta pixel configuration is disabled. Any server-side advertising measurement must respect the same advertising preference; submitting a form is not advertising consent. This website’s Netlify Edge Function selects the country and privacy settings and sends no advertising events itself.
Advertising requests still contain normal device, connection and page information, and permitted cookies or advertising identifiers may let providers associate activity with a browser or account. These events are pseudonymous, not anonymous. See Google’s explanation of Consent Mode, the Google Privacy Policy and the Meta Privacy Policy.
Changing or withdrawing consent
Open Cookie settings in the footer to reopen the dialog. Choose Decline to withdraw permission, or Accept to enable advertising measurement when GPC is not active. The Do Not Sell or Share My Personal Information link saves the same persistent decline directly. Your choice applies to this browser; other browsers or devices have their own settings.
Decline deletes unsent queued events, resets all four Google signals to denied, revokes Meta consent, clears the site’s stored campaign identifiers, landing address and referring address, and attempts to remove readable first-party advertising cookies named _fbp, _fbc, and those beginning _gcl_ or _gac_. When Meta has loaded, or Google has loaded for a United States visitor, the page reloads to remove those scripts. A reload closes an open Typeform and clears the local chat; it does not delete answers or responses already stored with Typeform. Other open tabs also receive a saved decline when the browser supports local-storage notifications.
Withdrawal stops future site advertising events. It cannot undo information already sent or delete cookies on a provider’s own domain. Outside the United States and without GPC, Google can continue the denied-mode requests described above. You can use browser controls and the providers’ privacy settings for provider-domain cookies, and contact us about data already submitted.
What stays in your browser
If your browser allows website storage, the page uses the entries below. If storage is blocked, a choice still applies to the current page but may not be remembered on a later visit.
Your advertising preference: the first-party cookie tiem_consent_v1 stores granted or denied for up to one year after the preference is saved. It is sent with requests to this website so that server-side consent checks can use the same explicit choice. Local storage also holds tiem_consent and tiem_consent_version, preserving recognised choices from earlier versions until you change them or clear site data. A decline in either source takes precedence. GPC saves a decline; turning off GPC alone does not erase it.
Your visit and form attempts: session storage holds tiem_session (the visit UUID). Each popup attempt has a separate UUID, the last question reference and its qualifying-revenue flag in page memory. Typeform supplies its own response identifier for submitted responses. The retired per-session qualification and outcome flags are no longer used to stop later attempts.
Queued events and duplicate prevention: tiem_event_state_v2 contains the session UUID, an ordered queue of unsent Google and Meta site events, event keys already recorded, and outcomes keyed by Typeform response identifier. The queue includes the event names and the limited event details described above, not form answers or contact details. It is sent in order when permission is granted and emptied on decline. Recorded video and scroll guards from the older tiem_meta_funnel entry are carried forward so they are not counted again. These records normally last for the tab’s browsing session, subject to browser session-restoration behavior. If session storage is unavailable, they remain only in page memory until reload.
Visit attribution when permitted: the nine campaign fields listed above use session-storage keys with a tiem_ prefix; each value is limited to 500 characters. tiem_landing_page and tiem_referrer retain the first landing address and the referring address supplied by your browser. These values are stored only while advertising measurement is permitted and are cleared on decline. The fbp and fbc hidden fields read existing advertising cookies when permitted; the site does not create those identifiers itself.
The local chat stays in the current page’s memory. Typeform’s separate saved-progress storage is described above. Advertising services may set their own cookies when permitted; their lifetimes and processing depend on provider settings and policies. Clearing site data removes saved choices and duplicate-prevention records. The next visit then follows the country and GPC rules above, including the United States default.
Rhian’s published material
Rhian’s creator video and revenue screenshots are published with her written consent. They show her individual experience and the periods stated on the page. Her results are not a forecast of yours.
Rhian can contact info@tiemstudios.com to withdraw publication consent. We will remove the affected material from this website and stop its further use in our campaigns. Withdrawal does not affect processing that was lawful before it was withdrawn.
Recipients, location and retention
We receive applications and use Typeform to store and process them. Netlify provides hosting. Google and Meta process the advertising information described above. These providers may process data in the United States and other countries, where privacy laws can differ from those where you live.
Provider terms describe their international processing and available safeguards. You can ask us at info@tiemstudios.com about the safeguards that apply to your information.
Retention of applications and correspondence depends on whether they are still needed to respond, prepare the audit, manage a resulting relationship, meet an applicable legal obligation or handle a dispute. Browser storage lasts as described above. Hosting logs, form-service records and advertising data also depend on the relevant provider’s service and account settings. For a deletion request or information about a specific record, contact us.
Your rights and the reasons for processing
Where the GDPR applies, handling an audit or service request is based on taking steps at your request before a contract (Article 6(1)(b)); advertising cookies, consent-enabled advertising processing and creator publication rely on consent (Article 6(1)(a)). Hosting, security, application administration and limited cookieless campaign measurement are pursued as legitimate interests (Article 6(1)(f)), subject to your rights and the requirements of applicable law. Processing needed for a legal obligation is based on Article 6(1)(c).
Depending on the law that applies to you, you may request access, a copy or portability, correction, deletion, or restriction of your personal data; object to processing based on legitimate interests; and withdraw consent. You may also complain to your local data-protection authority. The European Commission explains individual data-protection rights.
Send a request to info@tiemstudios.com using the contact details from your application. We may need enough information to verify that the request concerns your data. You can also use Cookie settings to decline consent-dependent advertising without losing access to the site.