Skip to content
devup↗
Site language

Privacy notice

Updated 16 October 2026

Who runs devup

devup is a technology newsletter run by Arda Abacı. For questions about your subscription or personal data, contact:

ardaabaci19@gmail.com

What we store and why

We store your email address, selected newsletter language, subscription status, and consent time and version to manage your subscription. Confirmation tokens have an expiry time. Delivery records include send attempts, provider identifiers, errors, and delivery, bounce, or complaint events. Queued messages contain the recipient address and personal subscription links.

Signup protection and preferences

To limit abusive requests, the app keeps rate-limit counters using keyed hashes of email addresses and, when supplied by the host, IP addresses. Hosting providers may also process request logs. Your language preferences are stored in cookies and browser local storage.

Services used

Vercel hosts the website, Prisma Postgres stores subscription and delivery records, and Resend processes outgoing emails and delivery events. Google Gemini summarizes news sources; subscriber email addresses are not included in the application's news-generation requests. These providers may process information outside Türkiye; their processing locations and retention depend on the service and account settings.

Your subscription and requests

Signing up requests a confirmation email. Newsletter delivery starts after you confirm. Each newsletter includes links to unsubscribe and change its language. Unsubscribing stops future newsletter delivery; it does not automatically erase existing delivery records. You can contact Arda to request access, correction, or deletion of your personal data. Requests are reviewed individually; the app does not provide automatic account erasure.

Retention and cleanup

Automatic cleanup is enabled. Its policy removes eligible unused news-source records older than 14 days, never-attempted pending signups older than 30 days, and expired rate-limit counters after one day. Eligible confirmation tokens and message payloads are cleared seven days after expiry; terminal newsletter message payloads are redacted after 90 days. Cleanup runs in batches, so these thresholds are eligibility periods rather than exact deletion deadlines.

Cleanup does not erase every record: confirmed, unsubscribed, and suppressed addresses, minimal delivery history, and records needing delivery review can remain. Provider logs and backups are managed separately from application cleanup.