Fledgy AI is operated by Metacognition Labs LLC. Last updated 4 August 2026.
This is a template, not legal advice. It describes how the software actually behaves. Before operating Fledgy AI with real students you must have it reviewed by a lawyer, particularly for FERPA, COPPA, GDPR and UK GDPR obligations, and for state student-privacy laws.
Metacognition Labs LLC operates Fledgy AI: a college admissions planning platform for students and school counselors, and a marketplace where students find work and organisations recruit them.Contact us at finn@cognitionlabs.uk.
Fledgy AI is intended for secondary school students, many of whom are minors. Where a school deploys Fledgy AI, the school acts as the data controller for its students' records and we process on its behalf. Where a student signs up independently, we rely on consent.
We do not knowingly collect data from children under 13. If you believe a child under 13 has an account, contact us and we will delete it.
Fledgy AI puts students and organisations in contact with each other. That is the point of the jobs board and the Open to Work directory, and it is also the part of the product that carries the most risk, because most students here are under 18 and the organisations are adults.
| Party | Can see | Cannot see |
|---|---|---|
| You | Everything in your account | - |
| Your counselor (if you joined a school) | Progress counts, college list, activities, honors, recommender status, GPA, essay prompts and status | Essay draft text, documents, marketplace purchases and earnings, admitted groups |
| Contributors you invite | College list, activities, honors, essay drafts, and comments if granted | Documents, earnings balance, your ability to edit anything |
| Other students | Only what you publish: a seller profile, a marketplace listing, or a group intro you opted into | Everything else |
Your profile is private by default. Nothing about you is visible to other users unless you explicitly publish a seller profile or opt into a group directory. Revoking a contributor ends their access immediately.
We are disclosing this explicitly because you should know.
This product, its application code, database schema, written guidance, and the curation of its opportunity and awards catalogs, was developed with substantial AI assistance. Catalog entries were assembled from an AI model's knowledge of real programs and have not been individually verified against their official sources by a human. Every entry links to its official page so you can check. See Data & accuracy.
At runtime, no student data is transmitted to any AI or language model. There is no AI inference in the product. Features that may appear AI-driven are not:
Your essays, documents, scores and messages are never used to train any model.
By creating an account or using Fledgy AI, you consent to our use of artificial intelligence as described in this section. That means: AI was used to build the product and to assemble its catalogs, and you accept that catalog entries, guidance and generated documents may contain errors that a human has not individually checked.
What you are not consenting to, because it does not happen: your data being sent to a model, used for training, or processed by AI at runtime. If we ever change that, it will not be done quietly under this clause. We will say so here, date the change, and ask again.
If you are not comfortable with this, do not use Fledgy AI for anything you would not want an unverified source to touch, and check every deadline, requirement and figure against the official page it links to. That is good practice regardless.
Application data, including uploaded documents, is stored in the application's own database.
Current limitation: uploaded documents are stored unencrypted and protected by access control rather than encryption at rest. Do not upload anything you would not want restored from a database backup. Encryption at rest, retention policies and audit logging are required before any production deployment handling real student records.
Clerk provides authentication. Your email address, name and sign-in activity are processed by Clerk in order to create and verify your session, and passwords, verification codes and any multi-factor secrets are held by Clerk rather than by us. This is a required processor: you cannot use Fledgy AI without it.
Beyond that, Fledgy AI makes no third-party requests by default. Optionally, an operator may enable:
We do not use advertising networks, analytics trackers or third-party cookies.
Session cookies are set by Clerk and are strictly necessary for login. Fledgy AI sets one cookie of its own, ud_role_intent: it remembers for one hour whether you clicked “create a counselor account” or “list your organization”, so the sign-up screens show you the right thing. It holds no personal data and is deleted as soon as you finish signing up. There are no tracking or advertising cookies.
The personal branding checklist uses your browser's local storage and never reaches our servers.
Depending on where you live you may have the right to access, correct, export, delete or restrict processing of your data, and to object or withdraw consent. Contact us to exercise any of these. Deleting your account cascades to all associated records.
Current limitation: account deletion is not yet self-serve, and deleting the Clerk account does not automatically remove the Fledgy AI record. Contact us and we will do it manually. A self-serve export and erase flow is required before any production deployment.
Where your school is the controller, direct requests to your school; we will assist them.
Account data is retained while your account is active. Admit letters are retained only as long as needed to verify a claim. On deletion, associated records are removed by cascade; backups age out on their own schedule.
We will post changes here and update the date above. Material changes affecting how we use your data will be notified in-product.