Privacy Policy
Effective date: October 19, 2026
1. Introduction / Who We Are
This Privacy Policy is issued by Develemit LLC, doing business as devalender ("devalender," "we," "us," or "our"). devalender is an online scheduling platform: hosts publish booking pages, an embeddable widget, a REST API and a command-line tool, and invitees use them to book, reschedule and cancel meetings.
2. Scope
This policy covers personal data we process when you visit devalender.com, create a host account, book a meeting through a devalender booking page or widget, or use our API or CLI. It does not cover third-party websites that embed our widget, calendars or tools you connect yourself, or how a host uses booking information after it reaches them. Hosts decide which meetings they offer and act as the controller of their invitees' data; we process that data on their behalf.
3. Data We Collect and Why
- Account data (hosts): email address, handle, display name and timezone, so you can sign in and publish a booking page.
- Operational data: event types, availability, date overrides and bookings, including each invitee's name, email address, timezone, chosen time and any cancellation reason, so we can schedule meetings and send confirmations and reminders.
- Billing data (Pro hosts): plan, billing interval and subscription status. Payments are handled by Stripe; we never receive or store full card numbers.
- Usage and technical data: IP address, browser type and request logs from our servers, plus product events and errors linked to an anonymous identifier kept in your browser's local storage, so we can secure the service, fix bugs and understand which features are used.
4. How We Use Data
- Provide booking pages, the widget, the API and the CLI.
- Send sign-in codes, booking confirmations, reschedule and cancellation notices, and reminders.
- Process Pro subscriptions and apply plan limits.
- Secure accounts, prevent abuse and enforce our Terms of Service.
- Monitor errors and performance and improve the product.
- Comply with legal obligations.
We do not sell personal data.
5. Google User Data
If a host connects Google Calendar, devalender asks Google for permission to do only the following, and only for that host's own account:
- Read the list of calendars on the account, so the host can choose which ones count as busy and where bookings are added.
- Read free/busy information for the calendars the host selected, so devalender does not offer times the host is already busy.
- Read the title, time, location and description of events on the calendars the host selected, only to show them to that host on their own devalender calendar page. We do not store these event details, and we do not share them with anyone, including on public booking pages. We never read attendee lists.
- Create, update and delete the events devalender itself adds for the host’s bookings, including the invitee’s name and email address and the meeting details, so confirmed bookings appear on the host’s calendar.
- Read the account’s email address, so the host can see which Google account is connected.
We use this data only to provide and improve these calendar features inside devalender. We do not sell Google user data, do not use it for advertising, do not use it to train AI or machine-learning models, and do not allow people to read it except as needed to provide the service, for security, or to comply with the law. The Google access token we hold is stored encrypted.
When the host disconnects Google Calendar, we revoke our access with Google and delete the stored connection data. Links between existing bookings and the calendar events we created are kept with those bookings so later changes can still be reflected; the host can delete the events from Google Calendar at any time. Hosts can also revoke access from their Google Account permissions page.
devalender's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
6. Children's Data (COPPA)
devalender is a business tool and is not directed to children under 13. We do not knowingly collect personal data from children under 13. Hosts are responsible for obtaining any parental consent required before collecting a child's information through their booking page. If you believe a child has given us personal data, contact [email protected] and we will delete it.
7. Data Retention
We keep account and booking data for as long as the host's account or subscription is active, and for 30 days after the account is closed or the subscription is cancelled, so the host can export or restore it. After that window we delete it, except billing records, which we keep for 7 years to meet tax and accounting obligations. Encrypted database backups roll over and are deleted within 7 days. Server logs are kept for a short rolling period. If a host connects Google Calendar, we delete the stored Google refresh token and the links between bookings and calendar events as soon as the host disconnects it or deletes their account; we do not keep a copy of the host's Google calendar data.
8. Your Rights (CCPA / California Residents)
If you are a California resident, you have the right to know what personal data we collect and how we use it, to request deletion, to opt out of the sale or sharing of personal data (we do not sell or share it for cross-context advertising), and not to be discriminated against for exercising these rights. Send requests to [email protected]. We will verify the request and respond within 45 days. Invitees may also contact the host who received their booking.
9. Cookies and Tracking
We use one strictly necessary cookie to keep hosts signed in, and no advertising or cross-site tracking. Details are in our Cookie Policy.
10. Data Security
All traffic is encrypted in transit with TLS. Database backups are encrypted at rest, API keys and sign-in tokens are stored only as hashes, and production access is limited to authorized personnel using key-based authentication. If a breach affects your personal data, we will notify affected users and regulators as required by law, without undue delay.
11. Subprocessors
We use the following service providers to run devalender:
| Subprocessor | Purpose | Data | Location |
|---|---|---|---|
| Hetzner Online GmbH | Application hosting and primary database | All data described in this policy | Germany (Nuremberg) |
| Cloudflare, Inc. | DNS and encrypted database backup storage (R2) | Request metadata such as IP address; encrypted database backups | United States and global network |
| Stripe, Inc. | Payment processing for Pro subscriptions | Host email and payment details. Card numbers go directly to Stripe; we never receive or store them | United States |
| DevelEmail (Develemit LLC) | Transactional email: sign-in codes, booking confirmations, reminders | Recipient name and email address, booking details | Develemit LLC infrastructure |
| emit-billing (Develemit LLC) | Subscription and entitlement management on top of Stripe | Host account identifier, email address and plan status | Develemit LLC infrastructure |
| Google LLC (Calendar API) | Optional Google Calendar sync: busy times and booking events for hosts who connect a calendar | Host Google account email, calendar list, free/busy times, and the events devalender creates for bookings (including invitee name and email) | United States and global network |
| emit-vision (Develemit LLC) | Product analytics and error monitoring | Page views, feature events and errors keyed to an anonymous or host identifier; no invitee personal data | Develemit LLC infrastructure |
12. Data Transfers
Our application servers and primary database are located in Germany, and some subprocessors operate in the United States. By using devalender you consent to your data being transferred to and processed in these countries, which may have data protection laws different from those where you live.
13. Changes to This Policy
We will email hosts at least 30 days before material changes take effect and update the effective date above. Continued use after that date means you accept the updated policy.
14. Contact Us
Questions or requests about this policy: [email protected].