- What data category a feature needs
- Why that data is needed
- When processing leaves the device
- When cloud processing is required
- Material privacy or data-handling changes
- User-impacting incidents when disclosure is safe
- Material product limits and availability changes
- Public release state and user-facing version identity
FREDAI / PUBLIC PRODUCT PRINCIPLES
Clear where it matters.
Private where it protects.
A practical standard for disclosure and product accountability.
FredAI is in development. The statements below describe its intended public commitments and information boundaries; they are not claims that every feature is already released.
Useful information is public.Sensitive internals are not.These boundaries are deliberate.
01
DISCLOSURE BOUNDARY
What we show. What we protect.
- Credentials, tokens, keys and secrets
- Exploit instructions or bypass paths
- Defensive and anti-abuse thresholds
- Private infrastructure topology
- Internal access paths and privileged controls
- Unreleased proprietary internals
- Security telemetry that would weaken defences
- Any other user's private information
02
PUBLIC COMMITMENTS
The product rules.
No paid placement.
- Answers are not sold to advertisers.
- Product suggestions are not paid placements.
- Conversation ranking is not designed around advertiser attention.
Data is not inventory.
- Personal data is not sold to advertisers.
- Personal data is not sold to data brokers.
- Use stays tied to the feature the user chose.
Cloud boundaries are visible.
- Off-device processing is identified.
- Cloud-required features say so.
- Remote processing is not presented as fully local.
Material changes get a record.
- Privacy changes are dated.
- Material data-handling changes are dated.
- Material model-identity or release-state changes are documented.
Impact is acknowledged.
- Material user impact is disclosed when safe.
- Public notices focus on impact and remediation.
- Disclosures do not include reusable attack instructions.
No dark patterns.
- No fake urgency around consent.
- Privacy choices should use plain wording.
- Safer choices should not be deliberately harder to find.
Limits stay visible.
- Known material capability limits are stated.
- Availability changes are stated.
- Uncertainty is not disguised as certainty.
Dates do not force release.
- Public handoff remains evidence-gated.
- Verification failure keeps a release held.
- A scheduled event and a product release are separate states.
Transparency has a stop line.
- Security-sensitive implementation detail stays private.
- Public explanations describe user impact, not bypass mechanics.
- Private controls are not documented as public interfaces.
Storage rules belong with the feature.
- User-relevant retention rules should be stated where storage exists.
- A feature should not imply permanent or zero retention without evidence.
- Operational security logs are not published as a public schema.
Material identity changes are named.
- Public model or product identity should be clear where it affects use.
- Meaningful version changes should not be silently relabelled.
- Internal implementation detail may remain private.
Private means private.
- One user's information is not a transparency artefact for another.
- Public reports should remove unnecessary personal detail.
- Disclosure does not override confidentiality.
03
INFORMATION CLASSES
Three layers.
User-impacting facts.
Enough to understand the product.
Anything that increases risk.
THE RULE