Privacy
How AgentRepo.dev handles your information.
2026-10-19
Operator and contact
Luis Ballester Zafra operates AgentRepo.dev. Contact the address below for privacy requests, access, corrections or account deletion.
Accounts and contributions
Signing in with GitHub or email provides an account identifier, email address and profile information. We use these to authenticate you, record authorship and review submissions. Approved contributions and their public authorship are visible to visitors; pending proposals are available to the administrators. Do not upload secrets or personal data you cannot publish.
Contact assistant
The portfolio contact form stores your email, topic and message so we can respond. A bounded portion of your message is sent to DeepSeek to draft an AI-assisted reply; the application generates the email and PDF. Spacemail delivers the reply and an internal notification. Do not include sensitive information. AI output may be inaccurate and does not confirm availability or commercial commitments.
Analytics and technical data
Cloudflare Web Analytics measures page visits, referrers, approximate country, device/browser characteristics and loading performance. It does not use analytics cookies, advertising profiles or session recordings. It does not receive form contents or your account identity from this application. Browser blockers can prevent measurement. Hosting and security services also process request information to operate and protect the site.
Services and preferences
Supabase provides authentication and the database; Spaceship hosts the applications and Spacemail; Cloudflare serves and protects the website. These providers may process data outside your country under their own terms. Session cookies keep you signed in, and a locale cookie remembers your language. We do not sell your data.
Retention and rights
We retain account and contact information while needed to provide the service, review submissions and resolve support or security issues. Request deletion through the contact below; public contribution history and provider backups may require separate review. You may also contact the relevant data protection authority.