last updated: september 6, 2026.

who handles your data

codedorian is operated by dorian marié, the controller of personal data processed to provide this service. for privacy questions or to exercise your rights, email [email protected].

your account and subscriptions

we store account and login information, contact details you provide, language and time zone preferences, sessions, and subscription settings. mobile use also involves device identifiers and push notification tokens. billing records include subscription status, prices, stripe references, and invoices; stripe processes payment details and billing information at checkout.

the details your chosen service needs

setup combines the fields shared by a service with any additional or replacement fields for your plan. required fields are needed to configure that subscription; optional fields let you adjust its behavior. depending on your choices, this includes:

• x unfollow alerts: the x username you enter and follower information retrieved to detect changes and calculate the subscription price.
• birthdays: the names and full dates of birth you enter, used to calculate reminder dates and ages.
• calendar: google account email addresses and oauth refresh tokens, calendar and event information, a time zone, reminder intervals, and an optional completion heartbeat url. upcoming events are cached for reminders.
• github notifications: a github access token and information about your open pull requests and their checks, including titles, branches, links, and results.
• first to be available: the team names you enter to produce a shuffled list.
• heartbeat: a monitoring url when used by the plan, and settings such as the interval, grace period, and http method.

where your updates go

email plans ask for a recipient email address. slack plans ask for a slack token and channel name. push plans use the devices connected to your account, and some deliveries are saved in your messages. heartbeat plans that include url requests contact the configured destination.

the selected recipient, slack channel members, or anyone able to view your device notifications may see the delivered content. choose destinations with this in mind, especially for birthday, calendar, or repository information.

why we use this information

we use account, subscription, and integration data to provide the service you request: authenticate you, perform scheduled checks, prepare reminders, deliver results, and manage billing. this processing is based on performing our contract with you. we also process technical and security records for our legitimate interests in keeping the service reliable, preventing abuse, diagnosing errors, and responding to support requests. legal obligations may require billing records to be retained. where processing relies on consent, you may withdraw it.

connected services and providers

data is exchanged with the providers needed for your selected service and delivery channels, including google calendar, github, slack, and the x data provider twitterapi.io. stripe handles payments. hosting, email, push, security, and diagnostic providers support operation of the app, including cloudflare, google, apple, and sentry where used. these providers receive the data needed for their role; technical records may include ip addresses, browser details, errors, and account identifiers.

provider processing may take place outside your country, including outside the european economic area. contact us for information about the destinations and transfer safeguards applicable to your data.

credentials and technical records

integration tokens and monitoring urls can grant access to connected services. provide them only in the setup fields that request them, limit their permissions, and revoke or replace them with the provider when access is no longer needed. do not include unrelated passwords or secrets in free-text fields.

the app uses session and preference mechanisms to keep you signed in and remember settings. execution history, messages, logs, change history, and error reports can contain information involved in running a service.

how long data is kept

account and subscription content is generally kept while the account or related feature remains active. technical records, messages, change history, and billing records may remain as needed for operation, security, support, audit, and legal obligations. canceling a subscription does not automatically erase its settings or past records. contact us to request deletion; information that must be retained for legal obligations or the establishment, exercise, or defence of legal claims may be kept for those purposes.

your choices and rights

you can update subscription settings and revoke integration access with the connected provider. revoking access may stop the service from working and does not cancel billing.

subject to applicable conditions, you may request access, correction, deletion, portability, or restriction of your personal data, object to processing, and withdraw consent for processing based on it. these rights also apply if someone else supplied information about you. email [email protected]. you can lodge a complaint with your data protection authority, including the cnil in france.

about · terms · privacy · view all services