Privacy Policy
Privacy Policy
Orthodox Web Solutions LLC. Last updated October 21, 2026.
Orthodox Web Solutions builds and hosts websites for Orthodox Christian churches, monasteries, dioceses and other organizations, and provides the Site Manager, the website system they use. This policy explains what information we collect, why, how it is protected, and the choices you have. It covers orthodoxws.com, our client area at accounts.orthodoxws.com, our scheduler, the Site Manager and its apps, and our sign-in service at api.orthodoxws.com. Websites we host for churches explains how this applies to the people who visit our clients' websites.
In short: we collect what we need to serve you, we never sell it, we do not use it for advertising, and you can ask us to see, correct or delete it at any time.
On this page: What we collect · How we use it · Who we share it with · Websites we host for churches · Social connections · Google Calendar · Zoom · How data is protected · How long we keep it · Your rights · Contact
What we collect
What you give us
- Forms on our website. When you contact us, sign up, ask for a website review or fill out a design questionnaire, we receive what you enter: usually your name, your organization, email address, phone number, your message, and any files you upload.
- Your client account. When you become a client, we keep your contact details, your organization's details, your services and domain names, invoices and payment records, and your support tickets.
- Email, calls and meetings. When you write to us, call us or book a call through our scheduler, we keep the messages, the booking details and our notes, so we can help you and follow up.
- Domain names. When we register a domain name for you, the registrar and the domain registry require the owner's contact details, as they do for every domain.
What is collected automatically
- Server logs. Like every website, our servers record each request: the IP address, browser type, the page asked for, the page you came from, and the date and time. We use these logs to keep the websites running and secure, for example to block attacks and to find problems.
- Cookies. Our websites use only the cookies they need to work: a session cookie that keeps you signed in and keeps a form together while you fill it out, and a cookie that remembers a language you choose. We do not use advertising cookies or Google Analytics, and we do not track you across other websites.
- Services built into our pages. Some pages load parts from other companies: Google reCAPTCHA on our forms (to stop spam), embedded YouTube videos (in privacy-enhanced mode, which sets no cookies until you play a video), Google Fonts, Google Translate when you choose another language, and maps. These companies receive your IP address and browser details when you load them, under their own privacy policies.
How we use it
- To answer you, set up and run your website, email and services, and support you.
- To bill you for our services and keep accurate records.
- To tell you about your account, your services, security matters and changes to the Site Manager. You can ask us to stop any other messages, such as newsletters, at any time.
- To keep our servers and our clients' websites safe, and to prevent spam, fraud and abuse.
- To improve our services, using what we learn from support requests and how the Site Manager is used.
- To meet our legal obligations.
We do not sell personal information, rent it, or use it for advertising.
Who we share it with
Only with the service providers that help us run our services, and only what each one needs:
- the data centers and backup service where our servers and backups are kept, in the United States;
- our payment processor, to take payments;
- our email delivery service, to deliver the messages our servers send;
- the domain registrar, for domain names we register for you;
- Google (reCAPTCHA, Fonts, Translate, YouTube and maps, as described above) and Zoom, when you book a call with us;
- an artificial intelligence service (Anthropic's Claude) that helps our team answer support requests and powers Help Chat in the Site Manager. It receives the question and the information needed to answer it, processes it only to give us the result, and does not use it to train its models.
We may also disclose information when the law requires it (for example, a subpoena), to protect the safety of a person or the security of our services, or to a successor if our business is ever transferred, in which case this policy continues to apply.
Websites we host for churches
Each website we host belongs to the church or organization that runs it. When you visit one of those websites, fill out its forms, give online, join its mailing list, use its member directory, send a prayer request, book an appointment or use its app, that church decides what is collected and how it is used, and its own privacy policy applies. We store and process that information on the church's behalf, only to provide its website and features, and we do not use it for our own purposes. To see, correct or delete information a church holds, please contact the church; we will help it answer your request.
Some features use other companies the church has chosen: online gifts and store payments go through the church's payment provider (for example Tithe.ly, PayPal, Stripe or Authorize.net), and app notifications through a notification service. The Site Manager connections below are part of this too.
Social connections
The Site Manager's social connections let a website administrator connect the organization's own social media accounts (Facebook Pages, Instagram, Threads, YouTube, TikTok, LinkedIn Pages, Pinterest) so that the website can show what those accounts publish, and, where enabled, publish the website's own news to them.
What is collected
- A sign-in token. When an administrator connects an account, the platform issues a token that allows the actions the administrator approved (reading the account's public posts and, where enabled, publishing). The token is encrypted and stored only in that organization's own website database. Orthodox Web Solutions' sign-in service (api.orthodoxws.com) passes the token to the website and keeps no copy.
- The account's public identity: its id, name or username, and profile picture, shown on the website's administration pages and beside its posts.
- The account's own public posts: text, pictures, video thumbnails, dates, links and public reaction counts, copied to the website on a schedule so that pages can show them without contacting the platform while a visitor waits.
- A log line on the sign-in service recording that a connection was attempted and how it ended, with no token and no post content.
What is not collected
Nothing about the people who follow, like or comment on the account. Nothing from any personal account: an administrator connects the organization's Page or professional account, and the website reads only that account's own posts. No messages, no contacts, no advertising data.
How it is used
To display the connected accounts' posts on the organization's website and in its mobile app, and, when the administrator chooses it for an item, to publish that item to the connected account. Nothing is sold, shared with third parties, or used for advertising.
Where it is kept
On Orthodox Web Solutions' servers in the United States, in the organization's own website database, alongside the rest of that website's content.
How it is removed
A website administrator can disconnect an account at any time under Social, Connections; the token and every cached post from that account are deleted immediately. Removing the app from the platform side (for example under Facebook or Instagram's Apps and websites) invalidates the token, after which the website stops reading and its administrators are told to remove the connection. A platform's data deletion request reaches us at the address registered with that platform and is honored the same way; a confirmation code is issued and can be checked at this service.
Your choices
Only a website administrator with the Social privilege can connect or disconnect an account. The permissions asked for at sign-in are the minimum needed for what the website does; nothing is published unless the administrator checks it on an item.
Google Calendar (appointment booking)
A website that uses the Site Manager's appointment booking lets each person who takes bookings (a priest or a staff member, for example) connect their own Google account from their private booking page. Connecting is optional and is done by that person, through Google's own sign-in and permission screen for Site Manager by Orthodox Web Solutions.
What is accessed, and why
- The email address of the Google account, to show the person which account is connected.
- The list of the account's calendars (their names), so the person can choose which calendars make them busy and which one receives their bookings.
- Busy times on the calendars they chose: only when a time starts and ends. The titles, guests, descriptions and locations of their events are not read. Busy times are used to leave those times out of what visitors are offered.
- Events: the Site Manager adds each confirmed booking to the calendar the person chose (with the visitor as a guest, and a Google Meet link when the booking is a Google Meet), and changes or removes that same event when the booking is moved or cancelled. It does not read, change or remove any other event.
What is stored
- The access and refresh tokens Google issues, encrypted, in that organization's own website database. Orthodox Web Solutions' sign-in service (api.orthodoxws.com) passes them to the website and keeps no copy.
- The account's email address, the names of its calendars, the person's choices among them, and the id of each event the Site Manager created.
- Busy times are asked for when a visitor looks at the booking page and are not stored.
All of this is protected as described in How data is protected: encrypted in transit, tokens encrypted at rest with AES-256-GCM, the app's client secret held only on the sign-in service, and no Google Calendar information shown to visitors.
How it is used and shared
Only to provide the booking feature to the person who connected the account. Google user data is not sold, not used for advertising, not used to develop or train artificial intelligence or machine learning models, and not transferred to anyone else, except as needed to provide the feature, to comply with the law, or with the person's consent. Nobody at Orthodox Web Solutions reads it, except with the person's permission to resolve a support request, or where the law requires it. A visitor to the booking page sees only which times are open, never why a time is unavailable.
The Site Manager's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
How it is removed
The person can press Disconnect Google Calendar under Settings on their booking page at any time: the Site Manager tells Google to withdraw the permission and deletes the tokens, the calendar names and their choices at once. They can also remove Site Manager by Orthodox Web Solutions at myaccount.google.com/permissions; the website then stops using the connection and tells the person. Events already added to their calendar stay there, as theirs. To ask us to delete anything else, write to the address below.
Zoom (appointment booking)
A website that uses the Site Manager's appointment booking can make a Zoom meeting for each online booking. Each person who takes bookings can connect their own Zoom account from their private booking page, and a website administrator can connect one Zoom account for the website, used for the people who have not connected their own. Connecting is optional and is done through Zoom's own sign-in and permission screen for Site Manager by Orthodox Web Solutions.
What is accessed, and why
- The Zoom account's user ID, email address and plan type, to show which account is connected, to recognize the account if it is later removed from Zoom, and to warn that meetings on a free Zoom plan end after 40 minutes.
- Meetings: the Site Manager creates a meeting for each confirmed online booking, at the booked time, and changes or deletes that same meeting when the booking is moved or cancelled. It does not read, change or delete any other meeting, and it does not access recordings, chat, contacts or anything else in the Zoom account.
What is stored, and where
- The access and refresh tokens Zoom issues, encrypted, in that organization's own website database, with the account's user ID, email address and plan type.
- For each booking, the meeting ID, join link and passcode, kept with the booking so they can be sent in the confirmation emails to the visitor and the person, and so the meeting can be changed or deleted with the booking.
- Orthodox Web Solutions' sign-in service (api.orthodoxws.com) passes the tokens to the website and keeps no copy. It keeps only the Zoom user ID and which website connected it, so that it can tell that website if the app is removed in Zoom.
All of this is protected as described in How data is protected. Zoom data is used only to provide the booking feature. It is not sold, not used for advertising, not used to develop or train artificial intelligence or machine learning models, and not shared with anyone except the visitor and the person the booking is for, or as the law requires.
How to disconnect, and what is deleted
The person can press Disconnect Zoom under Settings on their booking page, and an administrator can disconnect the website's Zoom under Components › Booking, People. The Site Manager tells Zoom to withdraw the permission and deletes the tokens and account details at once. The app can also be removed in Zoom, under Manage, Added Apps, in the Zoom App Marketplace: Zoom then notifies us, and the website deletes the tokens and account details within minutes. Meetings already created stay in the Zoom account, as the owner's. To ask us to delete anything else, write to the address below.
How data is protected
These protections apply to everything this policy describes, and in particular to sensitive data: the sign-in tokens Google, Zoom and the social platforms issue, and the Google Calendar and Zoom information described below.
- Encrypted in transit. Every connection, between a browser and a website, between a website and Orthodox Web Solutions' sign-in service, and between either of them and Google or a platform, uses HTTPS (TLS). Nothing is sent unencrypted.
- Encrypted at rest. Sign-in tokens are encrypted with AES-256-GCM before they are saved, and stay encrypted in the website database and in every backup of it. The encryption key is kept apart from the databases, on our servers only, and is never sent to a browser.
- The app's own credentials stay in one place. The client secret that lets the app ask Google or a platform for tokens is held only on the sign-in service, outside its web folders, readable only by that service. Websites never hold it: when a token needs renewing, the website sends its encrypted token to the sign-in service, which renews it and returns it encrypted.
- Signed, short-lived hand-offs. Every message between the sign-in service and a website is signed and expires within minutes, so it cannot be forged or replayed.
- Least access. The app asks only for the permissions its features need. Tokens are never shown on any page. Visitors never see any Google Calendar information, and website administrators see only whether a person's calendar is connected and to which Google account. A person's booking page opens only with their private link plus a one-time code emailed to them. Website administration requires signing in, with two-step verification available. At Orthodox Web Solutions, only the staff who run the servers can reach them, through restricted, authenticated access.
- Kept only as long as needed. Tokens are deleted the moment a connection is removed, as described in each section. Busy times from Google Calendar are used at the moment they are asked for and are never stored. Sign-in service logs record only that a connection was made or failed, never a token or any calendar content.
- Protected servers. Our servers, in the United States, run behind a firewall with intrusion blocking and malware scanning, and receive security updates. If we learn of unauthorized access to Google user data or other connected-account data, we will tell the people and organizations affected, and Google or the platform concerned, without undue delay.
How long we keep it
We keep client account and billing records while you are a client and afterward for as long as the law and our accounting require. A website's content is kept while it is hosted with us; when a service ends, it is removed from our servers, and copies age out of our backups on their normal schedule (daily backups, plus weekly and monthly archives). Messages from our website forms and support requests are kept as long as they are useful for helping you. Server logs are kept for a limited time and then deleted.
Your rights
Whoever you are and wherever you live, you can ask us to tell you what personal information we hold about you, to give you a copy of it, to correct it, or to delete it, and you can object to or ask us to limit how it is used. Depending on where you live (for example in the European Union, the United Kingdom or California), the law may give you further rights, and you may complain to your data protection authority. Write to privacy@orthodoxws.com; we will answer within 30 days, and we may need to confirm that the information is yours before acting. Information held in a church's website belongs to that church, so we may involve its website administrator. Clients can also see and update their details by signing in to the client area. If information is needed to provide a service you asked for, deleting it may mean ending that service.
Children
Our services are for churches and organizations and are not directed to children. We do not knowingly collect personal information from children under 13. If you believe a child has given us personal information, please write to us and we will delete it.
Changes to this policy
We may update this policy as our services change. The date at the top shows the latest version. If a change is significant, we will say so on this page and, for clients, by email. We will not reduce your rights under this policy without your consent.
Contact
Orthodox Web Solutions LLC
10315 Carey Road
Berlin, MD 21811, USA
Privacy questions and requests: privacy@orthodoxws.com
Everything else: support@orthodoxws.com or 888.697.0020
See also Terms of Service and Our Policies.

