Legal

Privacy Policy

Last updated October 2026

How ClickFQ handles personal data on ReligiousFlow — what we collect as the platform, and what we merely process on behalf of the places of worship that use it.

1. Who this policy covers

This policy explains how KIWCO ("ClickFQ", "we", "us"), the company that operates ReligiousFlow, handles personal data in connection with it.

Two different sets of data, two different responsibilities. Data about the Organisation that runs a website is ours to explain. Data about visitors to that website — donors, people booking a service, volunteers — belongs to the Organisation; we only process it on their behalf.
  • Where we are the Data Fiduciary (the one who decides): account holders' details, billing records, support correspondence, and how the platform itself is used.
  • Where we are a Data Processor (acting on instructions): everything a visitor submits to an Organisation's website. That Organisation decides what is collected and why; ask them about their own privacy notice.

2. What we collect

From the Organisation that holds the account:

  • name, email address and password (stored only as a cryptographic hash);
  • the details you enter about your place of worship — its name, address, phone, timings, images and written content;
  • subscription and payment records, including the plan, cycle, amount, and identifiers returned by our payment provider;
  • messages you send us.

On behalf of the Organisation, from visitors to its website:

  • donation records — donor name, email, phone, amount, message and payment identifiers;
  • booking requests — name, phone, email, chosen service, date, and any details the Organisation asks for;
  • volunteer sign-ups — name, phone, email, interests and availability;
  • enquiries submitted through the ClickFQ marketing site.

Blog posts an Organisation publishes are ordinary website content, not personal data we process on anyone's behalf — but if a post names or pictures someone, that is the Organisation's decision and responsibility.

Automatically: page views on a hosted website (recorded as a count with a path and language, for the Organisation's own analytics), and standard technical data such as IP address and browser details needed to serve and secure the site and to apply rate limits.

We never receive or store card numbers, UPI PINs, CVVs or net-banking credentials. Those go directly to our payment provider.

3. How we use it

  • to create and run your website and provide the features you have enabled;
  • to take subscription payments and to pass donations to the receiving Organisation;
  • to send transactional messages — sign-in emails, receipts, alerts about a new donation, booking or volunteer;
  • to keep the platform secure, prevent abuse and enforce rate limits;
  • to provide support, and to tell you about changes to the service;
  • to meet legal, tax and accounting obligations.

We do not sell personal data, and we do not use donor, booking or volunteer data for our own marketing.

4. Payments and donations

Donations are charged on the Organisation's own payment account, not ours. The money does not pass through ClickFQ. We keep only a record of each donation — donor name, contact details, amount and the provider's reference — so it appears in that Organisation's dashboard and can be reconciled.

Where an Organisation displays a UPI ID or QR code instead, the payment happens entirely between the donor and that Organisation. We never see it.

ClickFQ's own subscription billing is processed by Razorpay on our account. Card and banking details are handled by the payment provider under its own privacy policy and its regulatory obligations; we never receive them.

5. Who else processes data

We use a small set of service providers, each bound to protect the data and to use it only to provide their service to us:

  • Supabase — database, authentication and file storage
  • Vercel — application hosting and content delivery
  • Razorpay — ClickFQ's subscription billing (an Organisation's donations run on that Organisation's own Razorpay account)
  • Brevo — transactional email
  • Cloudinary — hosting and delivery of images, and of any welcome recording an Organisation uploads, where enabled
  • Upstash — rate limiting
  • Meta (WhatsApp Business API) — only where an Organisation sends on ClickFQ's number. An Organisation using its own WhatsApp Business account sends under its own agreement with Meta, and we are not a processor of those messages at all.
  • AI model providers (currently Anthropic, reached through an AI gateway) — only for the internal ClickFQ staff tools described in section 6, never for visitors' donation, booking or volunteer details.

Third-party services a hosted website loads in the visitor's browser. These receive the technical data any web request carries (such as IP address and browser details) directly from the visitor, under their own privacy policies:

  • Google Fonts — the typefaces each website theme uses;
  • YouTube — videos and live streams an Organisation embeds. Gallery videos load from YouTube's privacy-enhanced domain (youtube-nocookie.com), and only after the visitor presses play;
  • Maps and social media — where an Organisation embeds a map or links to its social profiles.

Weather. Where an Organisation turns on local weather, our servers ask the Norwegian Meteorological Institute (MET Norway) for a forecast for the Organisation's approximate location (its coordinates, rounded). No visitor data is sent.

We also disclose data where the law requires it, in response to a valid order from a court or authority, to establish or defend a legal claim, or to protect the rights and safety of users and the public.

If the business is sold or reorganised, data may transfer to the acquirer, who would remain bound by this policy or one at least as protective.

6. Artificial intelligence

AI in how we build. ClickFQ uses AI coding assistants (including Anthropic's Claude) to help write, test, review and document the ReligiousFlow software. Those tools work on our source code. They are not given access to your account data or to visitors' personal data as part of that work.

AI in the running service is limited to internal tools used by ClickFQ staff:

  • Business review reports. To draft the narrative of a report for an Organisation, we send an AI model aggregated figures — counts, totals and trends such as page views or bookings over a period — not individual donors, devotees or volunteers.
  • Drafting ReligiousFlow's own blog articles. Staff can ask an AI model to draft a platform article from a topic they type. No customer or visitor data is included.
  • An internal assistant that helps ClickFQ staff look up and act on information in the platform. It can read the records a staff member asks it about, which may include an Organisation's account details, and is used only by authorised staff for support and operations.

AI output is treated as a draft and checked by a person before anyone relies on it. AI is not used to make decisions about donations, payments, account access or what appears on an Organisation's website. We do not use your data, or visitors' data, to train AI models.

The platform does not send visitors' donation, booking or volunteer details to AI models. If an Organisation chooses to use an AI tool of its own, for example to write or translate its content, that is under its own control and its own privacy notice.

7. Where data is stored

Data is stored on infrastructure operated by the providers above, in [HOSTING REGION, e.g. India / Singapore]. Some providers process data outside India; where they do, we rely on the provider's contractual protections and on transfers being permitted under applicable law.

8. WhatsApp alerts

An Organisation can ask to be told on WhatsApp when a donation, booking or volunteer arrives. Alerts go to one number that the Organisation itself enters — its own office or trustee — and are sent from ClickFQ's WhatsApp Business number.

The alert contains the donor's or devotee's name, phone number and the amount or service, because that is the point of the alert. It is sent only to the Organisation that the information already belongs to, and only when that Organisation has switched the feature on.

We count how many alerts each Organisation has sent in a month, to apply the allowance included in its plan. That count is a number, not a record of who was messaged.

9. How long we keep it

  • Account and website content — for as long as the account is open, and for a reasonable period afterwards so a lapsed subscription can be restored or exported.
  • Donation, booking and volunteer records — kept for the Organisation for as long as its account is open, and as long as tax and accounting law requires.
  • Analytics — page-view records are retained on a rolling basis for the dashboard's reporting window.
  • Backups — retained for a limited period and then overwritten.

When an Organisation deletes content, it is removed from the live service; residual copies may persist in backups until those expire.

10. Your rights

Under the Digital Personal Data Protection Act, 2023 and, where it applies to you, other data protection law, you may ask us to:

  • confirm what personal data we hold about you and give you a copy;
  • correct or complete anything inaccurate;
  • erase data we no longer need to keep;
  • nominate someone to exercise your rights if you are unable to;
  • raise a grievance about how your data has been handled.
If you donated, volunteered or booked through a place of worship's website, that Organisation decides what happens to your data — please contact them first. If you cannot reach them, contact us and we will help route the request.

Contact our Grievance Officer at [GRIEVANCE OFFICER NAME & EMAIL]. We acknowledge within 24 hours and aim to resolve within 15 days. You may also complain to the Data Protection Board of India.

11. Cookies

We use a small number of cookies, all first-party:

  • Sign-in cookies, which keep an account holder logged in. Without them the dashboard cannot work.
  • A site-selection cookie, remembering which website you are managing when you have access to more than one.
  • A short-lived cookie used during sign-in with Google to return you to the right page.

A hosted website may also keep a small note in your browser's session storage, for example that you have already heard or closed its welcome recording, so it is not offered again on every page. It stays in your browser, is cleared when you close the tab, and is never sent to us.

We do not use advertising cookies or third-party tracking pixels on the ReligiousFlow platform. An individual Organisation may add its own analytics to its website; that is its choice and its disclosure to make.

Sponsored advertisements. Websites on the Free plan show sponsored advertisements that we choose by the place of worship's city, state and faith, never by anything about you. We count how many times each advertisement is shown and clicked, per website per day, as bare numbers: no cookie is set, and no identifier, IP address or device detail is stored with those counts. A click passes through our server so it can be counted, and then takes you to the advertiser's website, whose own privacy policy applies from there.

12. Children

ReligiousFlow accounts are for adults acting for an Organisation. We do not knowingly collect personal data from a child. If you believe a child's data has been submitted through a website we host, contact our Grievance Officer and we will act on it.

13. Security

We use encrypted connections throughout, store passwords only as hashes, isolate each Organisation's data with database-level access rules, rate-limit public endpoints, and keep automated backups. Access to production data is limited to the people who need it to run the service.

No system is perfectly secure. If a breach affects your personal data we will notify you and the Data Protection Board as the law requires.

14. Changes to this policy

We may update this policy. The date at the top always reflects the current version, and we will notify account holders of material changes by email or in the dashboard.

15. Contact us

Privacy questions and requests: [GRIEVANCE OFFICER NAME & EMAIL].

Everything else: hello@clickfq.com.

Registered address: [REGISTERED ADDRESS].