ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Data Management: Define retention policy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem?
Kaapi currently lacks a defined data retention/wipe policy. This absence raises concerns about how long data is stored and when it should be deleted, impacting data management and compliance.
Describe the solution you'd like
- Define a clear data retention policy for Kaapi.
- Establish a data wipe policy to ensure timely deletion of stored messages.
- Produce a data-inventory note for DPDP review.
Original issue
Context
Kaapi stores all messages in its LLM call tables. It has no user identity — messages tie only to org/project/bot ID, so PII exists only if it's in message content. Data is encrypted at rest in AWS RDS, which sits in a private subnet and is accessible only to Kaapi developers.
Even then, Kaapi should have some retention/wipe policy.
Contributor guide
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
Start by reviewing Kaapi’s LLM call tables and the AWS RDS storage context described in the issue. Define retention and wipe rules for stored messages, then produce the requested data-inventory note for DPDP review.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- databases, documentation, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100