BlinkLink Technologies, Inc.
This policy describes how Blinklink's Audience Engineer Services work. It forms part of the Agreement wherever an Order Form includes an Audience Engineer license, under Section 1.1 of the Master Subscription Terms (the "Terms"). Words defined in the Terms mean the same here. The Order Form and the Terms prevail over this policy if they conflict.
1. The license
1.1. An Audience Engineer license is Orbit or Embedded. Orbit is part-time and the default, with a standup every week. Embedded is dedicated: the Audience Engineer works on Customer's account full-time, or for the share of time the Order Form states.
1.2. A Skills Audience Engineer works on training for Customer's teams and partners. A Social Audience Engineer works on video for the audiences Customer grows.
1.3. The Order Form states the license, the volume of Engineered Content it includes, whether the Audience Engineer uses Blinklink AI or Customer AI, and anything that differs from this policy, such as in-person attendance, Customer devices or email accounts, a required work location, a standing permission to publish, or a turnaround time.
2. What an Audience Engineer does
2.1. Skills. Converts training materials, SCORM files, documents, manuals, internal communications, and long-form video into short videos, lessons, courses, checks, certifications, and job aids, and runs the feeds, nudges, and learning paths Customer asks for.
2.2. Social. Clips long-form video into short videos, writes their titles, descriptions, and tags, produces short videos from Customer's source content, and prepares them for publication.
2.3. Both. Sets up the workflows Customer asks for, for example turning emails Customer forwards to the Audience Engineer into draft short videos; reads the deployment's analytics and reports on them; and, where Customer gives the access to do so, operates the platform for Customer.
2.4. An Audience Engineer is not general staff. They do not provide IT support, administration, or legal, safety, medical, or other professional advice, and do not work for teams, Affiliates, or use cases that the Order Form does not cover.
3. Standups and requests
3.1. Orbit: one standup a week, of 5 to 30 minutes, by video call, at a time agreed at onboarding. Embedded: Customer's regular team meetings within the Audience Engineer's working hours. Other meetings by agreement.
3.2. Requests reach the Audience Engineer in the standup, in the channel or email address set up at onboarding, or as a ticket. The Audience Engineer notes requests made orally in that channel.
4. The first 7 days
4.1. In the first 7 days of the license, Customer and the Audience Engineer agree the brand standard (style, tone, logo and color use, captions, languages, and lengths), the source materials to start from, who approves, the access needed, and the first workflows.
4.2. The brand standard is the measure of quality for Engineered Content. A change to it applies to new items from the date agreed, and redoing earlier items to a changed standard counts as new items.
4.3. Dates that depend on Customer's materials, access, devices, or approvals move when those arrive late.
5. Access
5.1. Customer may give the Audience Engineer administrator access. Whatever the access, the Audience Engineer uploads content, creates drafts, skills, and courses, sets up the workflows Customer asks for, and views analytics.
5.2. The Audience Engineer approves or publishes content, deletes content, changes users, permissions, settings, or integrations, messages End Users, or exports End User Personal Data only when Customer asks, under Section 22.6 of the Terms. Customer may ask by any means, including orally in a standup, by message, or by email. A standing permission, for example to publish each week's clips, is given and withdrawn in writing.
5.3. Publishing for Customer is the exception. As a rule, Customer approves its own content.
6. Approval and revisions
6.1. Every item is uploaded as a draft for Customer to approve or return with revisions. Nothing goes live without Customer's approval or request.
6.2. Each item includes one round of revisions within the brief and the brand standard, asked for within 10 working days of delivery, unless the Order Form says otherwise. A revision that requires the item to be recreated, such as a new source, script, structure, or length, or a changed brand standard, counts as a new item.
6.3. An item counts toward the volume when it is delivered for approval. An item that is not approved or returned within 10 working days counts as delivered and stays a draft.
6.4. Customer checks safety-critical, regulatory, and compliance content against its sources before approving it.
7. Volume, more capacity, and fair use
7.1. The Order Form states the volume, such as videos a month and their maximum length, and how language versions count. Unused volume does not carry over.
7.2. For more capacity, raise a ticket or ask the Audience Engineer. Blinklink quotes it, and it is added by an amended Order Form. An Audience Engineer for another team or use case needs its own Order Form.
7.3. Production is subject to fair use under Sections 4.4 and 22.4 of the Terms. Where requests go beyond the license, for example converting a whole archive at once, volume above the Order Form, work for teams or use cases it does not cover, or requests that use disproportionate production capacity, Blinklink may pace, queue, prioritize, or limit production, and will tell Customer and propose a plan or more capacity.
7.4. Turnaround is as the Order Form states, and otherwise as soon as reasonably practicable. It starts when the Audience Engineer has the source materials and a complete brief.
8. AI models
8.1. Audience Engineers use Blinklink AI unless the Order Form names Customer AI. Use of Blinklink AI is included within fair use unless the Order Form says otherwise.
8.2. With Customer AI, Customer provides the accounts, keys, capacity, and terms of use in advance and pays its providers. Turnaround and quality depend on the models Customer chooses. Blinklink does not switch to Blinklink AI without Customer's agreement.
9. Where Audience Engineers work
9.1. Audience Engineers work remotely, on Blinklink's devices and accounts, from locations Blinklink chooses.
9.2. In-person attendance, Customer devices, email addresses, or systems, and any requirement about where the work or the processing takes place, apply only when the Order Form states them or Blinklink agrees in writing before the work starts. Customer provides those devices and accounts, and the policies that apply to them, before the work that needs them starts.
9.3. Reasonable travel and on-site costs agreed in advance are Customer's unless the Order Form says otherwise.
10. People
10.1. Audience Engineers are Blinklink's people, employed or engaged and managed by Blinklink, and never Customer's employees (Section 22.8 of the Terms).
10.2. Customer may ask in writing for a different Audience Engineer, and Blinklink assigns one within 30 days. Blinklink may change the Audience Engineer with notice and a handover.
10.3. Audience Engineers do not sign personal agreements or policies for Customer. The Agreement covers confidentiality.
10.4. Customer treats Audience Engineers with respect. Blinklink may pause the work where its people are treated abusively or put at risk.
11. Confidentiality and records
11.1. Everything an Audience Engineer receives, sees, or hears in Customer's meetings, systems, and communications is Customer's Confidential Information (Section 22.10 of the Terms).
11.2. Audience Engineers record or transcribe meetings only with Customer's agreement, and keep Customer Materials only in the Services, Blinklink's systems, and Customer's systems.
11.3. Blinklink keeps records of requests, approvals, and work done, without copies of the content itself, under Section 14.4 of the Terms.
12. Pilots
12.1. During a Pilot, the Audience Engineer works as the Order Form describes.
12.2. Clips are Customer's. Other Engineered Content produced in a Pilot becomes Customer's when the Pilot converts and the first invoice under the subscription is paid. If the Pilot does not convert, that content is not delivered and is deleted with Customer Materials, unless Blinklink chooses to release it (Section 22.9 of the Terms). Customer's own materials are always Customer's.
13. When the license ends
13.1. Owned Content, including work in progress as it then stands, stays available to Customer. The Audience Engineer stops using Customer's access and returns Customer's devices.
13.2. Blinklink deletes Customer Materials, including copies held by Audience Engineers, under Section 14.4 of the Terms.
14. Changes
14.1. Blinklink updates this policy under Section 25.1 of the Terms.
© 2026 BlinkLink Technologies, Inc. Audience Engineer Policy, Version 1.1, effective 19 November 2026. Questions: legal@blinklink.com.