FANOS Enterprises, LLC

Confidentiality, Privacy, and Team Code of Conduct Agreement

Six Simple Promises

By joining the FANOS team, I agree to:

1. Protect people: Never reveal who a protected story is about.
2. Protect FANOS: Keep its plans, products, services, finances, partnerships, and internal work private.
3. Use information only for the FANOS work I am assigned.
4. Use only approved accounts, folders, devices, and tools.
5. Report mistakes or concerns right away: Hiding a problem creates more risk.
6. Treat every person with dignity, respect, honesty, and care.

Important: This is an agreement needing legal review. Read it, ask questions, and sign when you understand it. A parent or guardian should also sign when the Team Member is under age 18.

1. Purpose and Who This Agreement Covers

This Agreement is between FANOS Enterprises, LLC, referred to as “FANOS,” and the person signing as the “Team Member.” Its purpose is to protect:

• people whose lives or experiences are discussed through Alchemizing Stories;
• FANOS team members;
• guests, applicants, clients, vendors, and partners;
• FANOS business information; and
• FANOS services, products, tools, offerings, and future plans.

This Agreement applies to employees, contractors, interns, student mentees, volunteers, advisors, and any other person who receives access to FANOS information. It applies whether the information is: written; spoken; photographed; recorded; stored electronically; seen during a meeting; or learned informally.

2. What Counts as Confidential Information

“Confidential Information” means all non-public information in the categories below, even when it is not labeled “confidential.”

A. Protected Story and Personal Information

Protected Story and Personal Information includes:

• the real identity of any person discussed in a protected Alchemizing Stories narrative;
• any key, note, or record connecting a pseudonym (fake name) to a real person;
• names, initials, faces, voices, handwriting, photographs, and personal usernames;
• telephone numbers, email addresses, home addresses, and other contact information;
• exact locations, dates, ages, job titles, and family relationships;
• immigration history, religious community, employment information, and financial information;
• medical, mental-health, disability, legal, or family information;
• the identity of hospitals, clinics, schools, employers, churches, nonprofits, government agencies, businesses, or other institutions discussed in a protected story;
• raw footage, audio, transcripts, interview notes, messages, records, screenshots, drafts, captions, and comments;
• file names, tags, version histories, links, and electronic metadata; and
• any combination of details that could allow someone to guess the person or institution, even when no name appears.

B. FANOS Proprietary (Protected) Business Information

FANOS Proprietary Business Information includes:

• business plans, strategic plans, roadmaps, and internal priorities;
• planned services, products, programs, workshops, and consultations;
• unpublished digital toolkits, resource libraries, tools, applications, and technology ideas;
• prototypes, frameworks, methods, processes, and research approaches;
• unpublished literary products, family-story projects, and other creative products;
• pricing, budgets, expenses, revenue, forecasts, and funding plans;
• grant plans, financial records, tax information, and insurance information;
• contracts, legal advice, negotiations, and proposed terms;
• staffing plans, compensation information, and internal team decisions;
• unpublished episodes, scripts, research, editorial calendars, and production plans;
• audience information, analytics, marketing plans, and growth strategies;
• vendor, sponsor, client, and partner lists;
• partnership discussions, outreach plans, and proposed collaborations;
• brand assets under development;
• trademarks, logos, taglines, design files, and templates;
• SOPs, playbooks, trackers, dashboards, and project plans;
• account lists and internal workflows; and
• any other non-public information that could help another person copy, compete with, interfere with, or take advantage of FANOS’s work.

C. Security and Third-Party Information

This includes:

• passwords and recovery codes;
• account numbers and access links;
• security questions and authentication information;
• API keys, device information, and information about FANOS security systems; and
• confidential information FANOS receives from a client, guest, team member, applicant, vendor, partner, attorney, accountant, or other third party.

3. Strict Story-Privacy Rule: No Personal Identifiers

Non-Negotiable Rule
The Team Member will not share, publish, discuss, confirm, deny, hint at, or help another person identify any protected person or institution connected to an Alchemizing Stories narrative. This rule applies in both public and private settings, including: conversations with family or friends; school assignments; group chats; text messages and private messages; social-media posts; portfolios; resumes; scholarship, school, or job applications; personal projects; other employment; and work for another organization.

The Team Member agrees to:

• use only the pseudonym (fake name) and general or published description approved by FANOS;
• remove names and identifying details from drafts, file names, comments, captions, thumbnails, tags, prompts, version histories, and metadata;
• never create or keep a separate list connecting pseudonyms to real identities unless the Founder and legal counsel specifically approve it;
• never confirm or deny another person’s guess about who or which institution a story describes;
• never publicly connect a FANOS story to information found elsewhere;
• avoid exact dates, locations, ages, positions, and unusual facts that could make identification possible; and
• stop and ask before using a detail that might identify someone when combined with other information.

Public Guests and Contributors

A guest may be named, photographed, recorded, or shown only when FANOS confirms that the person has authorized that specific public use. That authorization applies only to: the approved guest; the approved content; the approved platform; the approved purpose; and the agreed period of use.

Permission to identify a public guest does not allow the Team Member to: reveal another anonymous person mentioned in the guest’s story; identify an anonymous institution mentioned in the story; share unpublished recordings or conversations; use the guest’s material in a personal portfolio; or share material outside the approved FANOS publication.

4. How Confidential Information May Be Used

The Team Member may use Confidential Information only when all three conditions are true:

1. The information is needed for a specific FANOS assignment.
2. The Team Member has been given access or written approval.
3. The information is handled through an approved FANOS process or system.

The Team Member may not: use Confidential Information for personal gain; use it for school credit without written approval; use it for another business, organization, or competing project; copy, photograph, screen-record, or screenshot it unless required for an approved assignment; download, print, forward, or remove it without approval; give it to another FANOS team member who does not need access; contact a protected story subject without authorization; contact an applicant, client, vendor, partner, institution, or media outlet unless specifically assigned and authorized; or use FANOS information to develop or support a separate product, service, organization, or commercial opportunity.

Access is based on need, role, and approval, not simply on being part of the FANOS team.

5. Technology, Account, and File-Security Rules

The Team Member agrees to: use individual accounts rather than another person’s login, unless otherwise told; use strong passwords; turn on multi-factor authentication when available; use only FANOS-approved folders, accounts, devices, and sharing settings; share files only with specifically named people who need access; check permissions before sending or publishing a link; lock devices when they are not being used; keep devices and software reasonably updated; protect screens and documents from being viewed by unauthorized people; tell FANOS immediately about a suspicious login, exposed password, or lost device; and follow any additional privacy or security instructions issued by FANOS.

The Team Member may not: send passwords or recovery codes through ordinary email, text, chat, Google Docs, GitHub, or another shared document (some exceptions apply); store passwords in a spreadsheet or ordinary document (some exceptions apply); use “anyone with the link” sharing unless FANOS approves the file for public access; move FANOS files to a personal email account, personal cloud drive, camera roll, USB drive, or unapproved application; use a shared or public computer to access sensitive information without approval; leave confidential information open or visible to other people; or delete official FANOS records without approval.

Passwords, recovery codes, and other sensitive access information must be kept in a secure password manager (please do your research to figure this out).

Personal Devices

A personal device may be used when FANOS approves it and the device has: a passcode or password; current security updates; automatic screen locking; and reasonable privacy protections. When a temporary local download is approved, the Team Member must delete it from: downloads; the desktop; the camera roll; trash or recycle folders; personal cloud backups; and other personal storage locations after the official FANOS copy has been uploaded and confirmed. The Team Member must not delete the official FANOS copy.

6. Artificial Intelligence

Ask Before Uploading
The Team Member may not enter or upload any of the following into a public or personal AI tool, transcription service, translation service, editing platform, design tool, storage platform, or other outside service without written approval: Confidential Information; financial records; legal documents; partner or vendor information; or identifying story details.

The Team Member must: never enter a real name or other personal identifier into an AI prompt; use the minimum amount of information needed; de-identify the information first; review the tool’s sharing and retention settings when instructed; verify facts, citations, translations, and quotations; and have a human review every output before FANOS uses or publishes it. AI-generated material must never be presented as verified human knowledge without appropriate review.

7. Publishing, Public Statements, Portfolios, and Social Media

Only the Founder, CEO, or another person designated in writing may give final approval to publish, release, or share FANOS content. The Team Member agrees that: silence does not mean approval; a draft is not approved merely because it appears complete; approved material must be published exactly as approved; substantive changes after approval require new approval; titles, names, facts, images, captions, links, and claims must not be changed without authorization; the Team Member may not speak publicly on behalf of FANOS without authorization; the Team Member may not respond to a reporter or media request without authorization; the Team Member may not make legal, medical, tax, or financial claims on behalf of FANOS; the Team Member may not promise a product, payment, partnership, service, or benefit without authorization; and the Team Member may not post confidential behind-the-scenes information on a personal account.

The Team Member may not publicly share: screenshots of internal work; private meetings or conversations; unfinished documents; internal disagreements; confidential accomplishments; unreleased logos or products; team messages; private photos; confidential schedules; or information about a protected story.

FANOS documents, screenshots, data, recordings, plans, work samples, or internal tools may not be used in: a portfolio; a class assignment; a school competition; an academic application; a job application; a scholarship application; or a personal project without prior written approval and complete de-identification.

8. Team Code of Conduct

A. Dignity, Care, and Trauma-Informed Behavior

Every Team Member must: treat each person as a human being, not as content, a diagnosis, a mistake, or an opportunity for attention; protect the dignity and meaning of people’s experiences; use respectful and accessible language; avoid judgmental or humiliating language; avoid pressuring anyone to share more than they wish to share; and remember that access to someone’s story is a responsibility, not an entitlement.

Team Members may not: gossip; shame; blame; sensationalize; mock; exploit; manipulate; pressure; or use another person’s pain for attention or personal gain.

B. Respectful and Safe Workplace

FANOS does not permit: discrimination; harassment; sexual harassment; bullying; threats; intimidation; retaliation; degrading conduct; coercion; or unwanted sexual or romantic conduct.

Team Members must respect differences in: race; color; national origin; ethnicity; culture; language; religion or faith; sex; pregnancy; disability; age; sexual orientation; gender identity; family status; immigration background; health status; and experience or authority.

A Team Member should report conduct that feels unsafe, coercive, discriminatory, harassing, retaliatory, or inappropriate. No person will be punished for making a good-faith report, asking for help, or participating truthfully in a review.

C. Accuracy and Integrity

Team Members may not invent or misrepresent: facts; citations; quotations; credentials; partnerships; results; audience numbers; research findings; or the status of a project.

Team Members must not: plagiarize; alter a quotation in a misleading way; manipulate a story to create a false impression; present an assumption as a verified fact; hide an error; claim that an AI-generated statement has been verified when it has not; or claim work performed by another person as their own.

Team Members must: correct mistakes promptly; clearly distinguish facts from ideas or assumptions; identify the source of information when appropriate; preserve the intended meaning of a speaker’s words; and tell the Founder when they are unsure.

D. Professional Boundaries and Conflicts

A Team Member may not privately solicit from a story subject, applicant, audience member, vendor, or partner: money; gifts; favors; business; romantic attention; personal services; employment; private health information; private financial information; or another personal benefit.

The Team Member must disclose any personal, family, financial, school, employment, or business relationship that could: affect impartiality; influence a decision; create divided loyalty; or create the appearance of a conflict.

The Team Member may not accept gifts, discounts, free products, referral payments, or special benefits connected to FANOS work without written approval.

E. Student and Minor Safety

Student interns should receive only the minimum information and access needed for an age-appropriate assignment. No one may instruct a student Team Member to hide work-related: contact; messages; meetings; assignments; safety concerns; privacy concerns; uncomfortable conduct; or incidents from a parent or guardian, FANOS leadership, counsel, or another trusted adult.

Student Team Members may: ask questions; request clearer instructions; ask for adult review; report discomfort; identify a task as too advanced; decline an unsafe or unapproved task; and ask that a parent, guardian, or trusted adult be included. They may do so without retaliation.

Work communications, meetings, and deadlines involving students should use: approved communication channels; reasonable hours; clear supervision; age-appropriate tasks; and the access limits established for the student’s role.

9. What to Do If Something Goes Wrong

Report It Right Away
The Team Member must immediately report: a lost or stolen device; a message sent to the wrong person; an incorrect file-sharing setting; a suspicious login; a missing file; an exposed password; accidental publication; an identifying detail in a story; a document placed in the wrong folder; an unauthorized download; inappropriate conduct; harassment or retaliation; a request to hide information; a possible conflict of interest; or any other possible privacy, security, or conduct problem.

Report the problem even when you are unsure whether harm occurred.

Primary Reporting Email or Telephone Number: contact@fanosconsulting.com
Alternate Contact or Counsel: As directed by the Founder.

The alternate contact should be used when the concern involves the Founder, supervisor, or person who would normally receive the report.

When reporting, explain: what happened; when it happened; what information or account may be involved; who may have received or seen it; what device or system was involved; and what immediate steps were taken.

The Team Member must not: hide the problem; destroy evidence; alter records to cover the mistake; contact affected people without instructions; contact the media; make a public statement; or attempt to investigate another person independently. FANOS will determine the appropriate next steps. A promptly reported, good-faith mistake will be handled differently from intentional misuse, concealment, retaliation, or repeated disregard of the rules.

10. FANOS Responsibilities

FANOS agrees to make reasonable efforts to: provide understandable, age-appropriate confidentiality instructions; explain the Team Member’s role and authority; provide approved work systems; limit access to the minimum information reasonably needed; protect Team Member personal information; avoid publicly sharing Team Member personal information without permission, except as required or permitted by law; provide a way to report privacy, conduct, safety, harassment, discrimination, or retaliation concerns; respond to good-faith reports without retaliation; take reasonable corrective action when needed; and provide appropriate supervision for student Team Members.

11. Return, Deletion, and End of Access

At FANOS’s request, or when the Team Member’s FANOS work ends, the Team Member will promptly: return FANOS property and materials; stop using FANOS accounts and systems; stop using Confidential Information; return keys, equipment, records, and devices belonging to FANOS; delete approved temporary copies from personal devices; remove FANOS information from personal email and personal cloud storage; remove files from downloads, trash folders, backups, and other personal locations; help transfer unfinished work and records to the person FANOS identifies; provide necessary account and project-status information; and confirm completion in writing if FANOS requests it.

The Team Member must not delete or alter official FANOS records during offboarding. FANOS will decide which official records must be preserved.

12. How Long the Duties Last

These duties begin when the Team Member first receives Confidential Information. They continue: throughout the Team Member’s FANOS relationship; and after the relationship ends.

Duties concerning the following continue as long as the information remains private or protected by law: protected story information; personal information; passwords and credentials; security information; third-party confidential information; and trade secrets.

Other proprietary business information remains protected until: FANOS authorizes its release; or it becomes public through no violation of this Agreement.

13. Information Not Covered

Confidential Information does not include information the Team Member can prove: became public through an authorized FANOS release or through no breach of this Agreement; was lawfully known to the Team Member before FANOS disclosed it; was lawfully received from another person who had the right to disclose it; or was independently developed without using FANOS Confidential Information.

Special Rule for Protected Stories: Even when a person or institution may be identifiable from public information, the Team Member may not confirm, deny, connect, or discuss the identity based on knowledge gained through FANOS.

14. Legally Protected Reports and Disclosures

Nothing in this Agreement prevents or punishes a Team Member for: reporting suspected unlawful conduct; reporting fraud; reporting discrimination; reporting harassment or sexual harassment; reporting sexual assault; reporting retaliation; reporting a safety concern; discussing or reporting wage or working-condition concerns when protected by law; reporting another legally protected concern; contacting a government agency; contacting law enforcement; consulting an attorney; speaking with a parent or guardian; responding truthfully to lawful legal process; cooperating with a government investigation; participating in a protected workplace investigation; or exercising another right protected by federal, state, or local law.

The Team Member does not need FANOS permission to make a legally protected report.

This Agreement is not intended to conceal sexual harassment or sexual assault, or to restrict a legally protected report about either. When another disclosure is legally required, the Team Member should give FANOS prompt notice when the law permits so FANOS can seek appropriate legal protection.

15. Limited Permission and No Transfer of Rights

FANOS gives the Team Member only the limited permission needed to use Confidential Information for approved FANOS work. No other license, ownership interest, or permission is granted. The Team Member may not assume that access to a FANOS document, idea, file, account, or tool means the Team Member owns it or may use it elsewhere.

Ownership of: work created for FANOS; pre-existing materials; inventions; written content; designs; photographs; recordings; code; research products; and other intellectual property should be addressed in the Team Member’s employment, contractor, internship, volunteer, contributor, or other role agreement.

16. Consequences and Lawful Remedies

A violation of this Agreement may result in: immediate suspension of access; removal from an assignment; corrective action; additional training; discipline; termination of the FANOS relationship; and required return or deletion of information; and another lawful response.

FANOS may seek: a court order stopping further use or disclosure; return or destruction of unauthorized copies; compensation for legally recognized harm; and other remedies available by contract or law.

A good-faith mistake that is reported promptly will be handled differently from: intentional disclosure; personal misuse; concealment; retaliation; dishonesty; or repeated disregard of privacy or security rules.

17. General Terms

1. This Agreement supplements, but does not replace, any role agreement, privacy policy, release, client obligation, or other duty that provides greater protection.
2. This Agreement does not promise employment, compensation, a specific assignment, or a particular length of service.
3. Changes to this Agreement must be in writing and approved by FANOS and the Team Member.
4. FANOS may issue reasonable privacy and security procedures that do not reduce the Team Member’s legally protected rights.
5. If one part of this Agreement is found unenforceable, the remaining parts continue to apply to the fullest extent allowed by law.
6. A delay in enforcing a provision does not waive it.
7. Proposed governing law and venue: Commonwealth of Virginia, unless legal counsel determines that another jurisdiction should apply.
8. Electronic signatures and signed counterparts may be used to the extent allowed by law.
9. If this Agreement conflicts with a legally protected right, the protected right controls.

18. Team Member Acknowledgment

By signing, I confirm that:

• I read this Agreement, or it was read and explained to me.
• I had the opportunity to ask questions before signing.
• I understand the strict no-identifiers rule for protected Alchemizing Stories narratives.
• I understand that FANOS plans, services, products, offerings, and internal operations are private unless FANOS approves their release.
• I understand that confidentiality applies in private conversations as well as public communications.
• I understand that I may not place confidential information into an AI or other outside tool without approval.
• I know how to report a privacy, security, safety, or conduct concern.
• I understand that I may make legally protected reports without FANOS permission.
• I agree to follow this Agreement and all approved FANOS privacy, security, and conduct procedures.