Com2Worship · Legal
Privacy Policy
What Com2Worship collects and why, who helps us process it, and how you stay in control.
Effective date: 2026-10-05
1. Overview
Yun Hwang (“we”, “us”) operates Com2Worship (com2worship.com, the “Service”), a worship planning service for churches. We follow the privacy laws that apply to our users, including the California Consumer Privacy Act as amended (CCPA/CPRA) and Korea’s Personal Information Protection Act (PIPA).
The Service handles two kinds of information. (1) Account information you give us when you sign up — we decide how it is used. (2) Information church admins and leaders enter about their members (e.g., worship team members) — the church decides how it is used and we process it on the church’s behalf (Terms, Section 5). You may send requests about (2) to your church first, or to us and we will work with your church.
↑ Back to top2. Information we collect
| Category | What | How |
|---|---|---|
| Account (Google sign-in) | Email address, name, and whether Google has verified the email. We may receive your Google profile photo URL but do not store it. | From Google when you sign in (scopes: openid, email, profile). You can edit your name during sign-up. |
| Account (email & password, limited) | Email, name, password (stored only as a one-way scrypt hash) | Entered directly, for a small number of operator/demo accounts |
| Church & team | Church name, church/team memberships, role and permissions, leader status, positions (parts), language preference, sign-up and last login time | Entered by you or your church admin; generated as you use the Service |
| Scheduling | Service assignments (service, position, accepted/declined status, decline reason) and blockout dates (dates, reason, whether shared with leaders, leader acknowledgement) | Entered by you or your leaders |
| Worship & song content | Orders of service and notes, song details (title, author, lyrics, chord charts, key, BPM), uploaded sheet music (PDF, JPG, PNG), annotations on sheets, song usage history, reference links | Entered or uploaded by users |
| Notifications | In-app notification content, web push subscription (browser push endpoint and encryption keys), notification language | When you allow notifications |
| Feedback | Your message, name, email and church | When you send feedback in the app |
| Payments | The paying church admin’s email and the church name (to create a Stripe customer), Stripe customer and subscription IDs, plan. Card details go directly to Stripe and are never stored on our servers. | When a church subscribes |
| Sign-up source | UTM values from ad links (source, medium, campaign, content, term), external referrer, first landing page and time, sign-up method | Stored in a first-party cookie (c2w_attr) on public pages and recorded once at sign-up |
| Automatic | Session cookie, IP address, browser info and request records (hosting logs), usage analytics and ad conversions (Section 6) | Automatically as you use the Service |
| AI usage | Number of AI calls, tokens and model per church | When AI features are used |
We do not ask for government ID numbers. Because the Service is for churches, the fact that you serve on a church worship team may reveal religious affiliation; we use it only to provide the Service and never for advertising.
↑ Back to top3. How we use information and legal bases
| Purpose | Basis |
|---|---|
| Identify you, keep you signed in, join churches and teams, and provide features such as services, assignments, blockouts and sheet music | Performance of our contract with you |
| Send assignment, blockout and reminder notifications (in-app, web push, email) | Contract |
| Process paid plans, subscriptions and refunds; tax and accounting | Contract; legal obligation |
| AI song analysis, recommendations and chart conversion | Contract (only when a user runs the feature) |
| Security, abuse prevention, debugging, backup and recovery | Legitimate interests; contract |
| Usage analytics (GA4) and sign-up source counts to improve the Service | Legitimate interests (not used to identify you) |
| Ad performance measurement (Meta and TikTok pixels) | Consent / opt-out — you can opt out any time (Section 6) |
If we change these purposes we will tell you in advance and ask for consent where the law requires it.
↑ Back to top4. Service providers and sharing
We do not sell personal information for money. We use the service providers below, under contracts that prohibit using the data for other purposes.
| Provider | What they do | Data involved |
|---|---|---|
| Vercel Inc. (US) | Website and server hosting, scheduled jobs | Everything sent to and from the Service; access logs |
| Supabase Inc. (US, AWS Ohio us-east-2) | Database, sheet music storage, daily backups | Everything stored in the Service |
| Google LLC (US) | Google sign-in, analytics (Google Analytics 4) | Sign-in data, pages visited and device info |
| Resend (US) | Email delivery (onboarding, notifications, invites) | Recipient email and name, message content |
| Anthropic PBC (US) | AI song analysis, recommendations and chart conversion | Song title, author, lyrics or the sheet file; sermon theme and scripture reference; candidate song details (themes, key, BPM). We do not send users’ names or emails. |
| Stripe, Inc. (US) | Payments and subscriptions | Church admin email, church name, payment details (collected directly by Stripe) |
| Meta Platforms, Inc. (US) | Ad measurement (Meta pixel) | Page view and conversion events, cookie and device info, IP address |
| TikTok (TikTok pixel provider) | Ad measurement (TikTok pixel) | Page view and conversion events, cookie and device info, IP address |
| Grafana Labs (US) | Operational metrics dashboard | Church ID, church name, AI usage counts (no personal data) |
| Browser push services (Google, Apple, Mozilla) | Deliver web push notifications | Encrypted notification content, push endpoint |
Within the Service, members of the same church and team can see each other’s names, positions and assignment status as needed for the features. Blockouts you share with leaders are visible to that team’s leaders and admins; unshared blockouts are visible only to you. We do not disclose personal information to anyone else unless required by law.
↑ Back to top5. International transfers
Our servers and database are in the United States. If you use the Service from Korea or elsewhere, your information is transferred to and stored in the US (PIPA Article 28-8).
| Recipient | Country | Data | When & how | Purpose | Retention |
|---|---|---|---|---|---|
| Vercel Inc. | US | Data sent through the Service, access logs | Whenever you use the Service, over encrypted HTTPS | Hosting | Until the contract ends or you delete your account (logs per Vercel’s retention) |
| Supabase Inc. | US (Ohio) | All stored data in Section 2 | Whenever data is saved, encrypted in transit | Database, files, backups | Until account deletion; backups up to 30 days |
| Google LLC | US | Sign-in data, email recipients and content, analytics | On sign-in, sending and visits, encrypted | Authentication, email, analytics | Per Google’s policies (GA4 retention setting) |
| Anthropic PBC | US | Song info, lyrics, sheet files, sermon theme and scripture | When an AI feature runs, encrypted | AI features | Deleted after Anthropic’s commercial API retention period; not used for training |
| Stripe, Inc. | US | Church admin email, church name, payment details | At checkout, encrypted | Payments | As required by law |
| Meta Platforms, Inc. / TikTok | US and others | Page view and conversion events, cookie and device info | On public page visits and conversions, encrypted | Ad measurement | Per each company’s policies |
Privacy contacts for each provider are listed in their policies: Vercel, Supabase, Google, Anthropic, Stripe, Meta, TikTok.
How to refuse and what happens: you may ask us to delete your account (Section 8). Because the whole Service runs on US servers, you cannot use it without the hosting and storage transfers (Vercel, Supabase). You can refuse the ad pixels (Meta, TikTok) at any time without affecting your use of the Service (Section 6).
↑ Back to top7. Retention and deletion
| Information | How long |
|---|---|
| Account, church, team, schedule, song and sheet data | Until you ask us to delete your account (or the church). We delete without delay, within 10 days of the request. |
| Blockouts | Until you delete them in the app or close your account |
| Sign-in sessions | 14 days (ended immediately when you log out) |
| Daily backups | Automatically deleted after 30 days — deleted data may remain in backups for up to 30 days |
| Web push subscriptions | Until you turn notifications off or the browser subscription expires |
| Sign-up source | Cookie 90 days; the value recorded on your account until account deletion |
| Payment records (Stripe) | As required by law (e.g., Korean e-commerce law: contract, withdrawal and payment records 5 years; complaint and dispute records 3 years) |
| Access records | 3 months under Korean law (hosting logs per Vercel’s retention) |
We delete electronic files so they cannot be recovered. Information we must keep by law is stored separately from other data.
↑ Back to top8. Your rights
You (or a parent or guardian for a child) may at any time:
- Access, correct, delete, or restrict processing of your information, withdraw consent, or close your account.
- In the app: change your name and language (Settings), delete blockouts, leave a team (Teams), turn off notifications, opt out of ad pixels (Section 6).
- Account deletion, full deletion or a copy of your data: there is no in-app delete button yet, so please email us at support@com2worship.com. We will verify your identity and respond within 10 days.
Some information entered by your church (such as assignment history) may require coordination with your church admin. We may decline a request where the law requires us to keep the data or where it would affect others’ rights, and we will tell you why. We will not treat you differently for exercising your rights.
↑ Back to top9. Notice to California residents (CCPA/CPRA)
- Categories collected: identifiers (name, email, IP), commercial information (subscription and payment records), internet activity (visits and usage), and user content (schedules, songs, sheets). We do not create inferences or profiles. Sources, purposes and retention are in Sections 2, 3 and 7.
- Sale and sharing: we do not sell personal information for money. However, the Meta and TikTok pixels may be considered “sharing” for cross-context behavioral advertising. You can opt out with the Do Not Sell or Share switch in Section 6 or with a GPC signal. We do not knowingly sell or share information of consumers under 16.
- Sensitive personal information: we use it only as necessary to provide the Service.
- Your rights: to know/access, delete, correct, opt out of sale/sharing, limit use of sensitive information, and not be discriminated against. Email support@com2worship.com; we verify requests through your account email and respond within 45 days. Authorized agents must provide proof of authorization.
10. Children
The Service is for adult church staff and volunteers. Children under 13 (US) or under 14 (Korea) may not create an account.
If a church adds a minor (for example, a youth worship team member), the church must obtain a parent or guardian’s consent and enter only the minimum information needed (name and position). If we learn that we collected a child’s information without proper consent, we will delete it promptly.
↑ Back to top11. How we protect information
- HTTPS for all traffic, HSTS, and security headers (clickjacking and MIME-sniffing protection)
- Sign-in cookies set HttpOnly, Secure and SameSite; sessions expire after 14 days; Google sign-in protected with a state check
- Passwords are never stored in plain text — only salted scrypt hashes
- Role-based permissions (admin, editor, leader, member), per-church data separation, and server-side permission checks
- Sheet music is kept in private storage and served only after a permission check through short-lived (5-minute) links
- Secrets kept only in server environment variables; database row-level security (RLS) enabled
- Daily backups (kept 30 days) and admin access limited to a minimum number of people
12. Privacy officer and contact
| Item | Details |
|---|---|
| Operator | Yun Hwang |
| Privacy officer | Yun Hwang |
| support@com2worship.com |
Users in Korea may also contact the Personal Information Infringement Report Center (118, privacy.kisa.or.kr) or the Personal Information Dispute Mediation Committee (1833-6972, www.kopico.go.kr).
↑ Back to top13. Changes and effective date
If we change this policy we will post the update here and notify you in the Service at least 7 days before it takes effect (30 days for material changes that reduce your rights).
Effective date: 2026-10-05. See also our Terms of Service.
↑ Back to top