How Civic Cycle handles user data

Civic Cycle collects email addresses used for account sign-in, password reset, keyword alerts, and weekly digest subscriptions.

If you create an account, app also stores your preferred county or school district so meetings, alerts, and digests can match your area.

If you create keyword alerts, app stores keywords, selected meeting bodies, alert status, timestamps, and unsubscribe tokens needed to manage those alerts.

If you sign in with Google, authentication is handled through Supabase and Google. Civic Cycle receives account details needed to identify your account, such as your email address.

Account data used to authenticate you, keep your session active, and let you manage settings.

Alert and digest data used to send requested emails when matching meetings or weekly summaries become available.

County preference used to personalize meeting lists, search results, and email content.

Administrative logs may record operational events such as imports, summary generation, email sends, API usage, and admin role changes so service can be monitored and debugged.

Civic Cycle does not ask for payment data.

Civic Cycle does not build advertising profiles or sell personal data.

Meeting transcripts, agendas, and summaries come from public government meeting materials, not private user submissions.

Data stored and processed with service providers used to run app, including Supabase for authentication and database services, Resend for email delivery, and configured infrastructure providers for hosting.

Google may process authentication data when you choose Google sign-in.

Data shared only as needed to operate service, comply with law, or protect app from abuse.

Account profile, alert preferences, and digest subscription records remain stored while account or subscription stays active.

You can stop alert or digest emails at any time through unsubscribe links included in emails. You can also change your county preference from settings while account remains active.

Deleting or fully removing account data is not yet self-serve in product interface. Until dedicated workflow exists, retention may continue until project operator removes data manually.

Civic Cycle uses third-party authentication and database tooling instead of storing raw passwords directly in application code.

No internet service can promise perfect security. Use strong password or trusted Google account and avoid sharing credentials.

This policy may change as product features change. Material updates should be posted on this page with revised effective date.

Effective date: May 30, 2026.