anomalyco / anomalyco/models.dev
Add provider data retention and training policies to metadata
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.7k
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 873
Description
Different providers have different data retentions.
Different providers within places like github and openrouter also have their own data retention policies.
I propose that models.dev adds a new metadata field for data retention, this would be shown in days.
We should also add a metadata field for if they train on data.
Users can then use this information to choose if they want to send their prompt to that provider.
We should be able to get this information from the provider.
Openrouter lists some information here for example: https://openrouter.ai/docs/guides/privacy/provider-logging#data-retention--logging
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by locating the model metadata schema and provider metadata ingestion, then review the linked OpenRouter privacy documentation and comparable provider sources. Done means retention in days and provider training status are represented in metadata with documented source information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100