Privacy Policy

Optyflo ("Optyflo", "we", "us") is operated by Wealth Connects LLP, a limited liability partnership incorporated in India (LLPIN AAW-4368), with its registered office at Flat No 12109, Tower 7, Crossing Republik, Ghaziabad, Uttar Pradesh 201016, India.

Optyflo is a workflow automation platform that also performs the sending: email from your own verified domain, WhatsApp, automated voice calls, Zoom webinar automation, forms and lead magnets, a CRM with a unified inbox, and an AI builder. Optyflo was formerly marketed as SalesProClub; both names refer to the same service and operator.

This policy covers optyflo.com and its subdomains, the Optyflo web application and API, the open-tracking pixel and tracked links inside emails our customers send, the public form, quiz and booking pages we host for customers, the optional website script a customer may embed for attribution, and every message we transmit on a customer's behalf.

Two roles apply, and they decide what you can ask of us:

• Account holders — our customers and their team members. For the data you give us to open and run an account, Optyflo is the data fiduciary under India's Digital Personal Data Protection Act, 2023 ("DPDP Act") and the controller under the GDPR where it applies.
• Contacts — the subscribers, leads, webinar registrants, quiz players and website visitors of our customers. For this data Optyflo is a data processor acting on the customer's documented instructions. The customer decides why and how it is used. If you are a contact, your first point of contact is the business that messaged you; we will help them respond.

Data you give us directly:

• Account data — name, work email, phone number, company name, password (stored only as a salted hash), the date and version of these terms you accepted at sign-up, and the email address and basic profile returned by Google if you sign in with Google.
• Workspace content — contacts (email, phone number, tags, custom fields, notes, deals, and any other profile fields you choose to store, which may include gender and date of birth), templates, campaign copy, automation flows, webinar and quiz definitions, forms and lead magnets, uploaded files and voice recordings, knowledge-base documents you ask the AI builder to answer from, and your unsubscribe / compliance footer settings.
• Billing data — your plan, any individually purchased modules, the ledger of metered usage, and, where your account has a credit wallet, its balance and a ledger of every top-up and per-message charge.
• Payments — wallet top-ups and plan purchases made in the app are processed by Razorpay on Optyflo's own Razorpay account; card, UPI and bank details are entered on Razorpay's checkout and never reach us. We store the Razorpay order ID and payment ID, the amount, what it was for, its status (and Razorpay's failure reason if it failed), and the name and email on your account. Other plans are provisioned by our team.
• Integration credentials — the API keys, OAuth tokens and phone-number identifiers for services you connect: Amazon SES or your own SMTP server, Gmail, Google Sheets, Meta WhatsApp Cloud API, an Indian WhatsApp business service provider such as AiSensy or Wati, Obligr voice, Zoom, Razorpay, Cashfree, HighLevel / LeadConnector, ad-platform conversion APIs, and an OpenAI API key if you supply your own. Section 6 covers how they are protected.
• Support and marketing — messages you send to hello@optyflo.com, demo-booking and contact-form submissions, and your email address if you join the newsletter from the site footer.

Data we collect automatically:

• Usage and security logs — sign-in events, IP address, browser and device type, pages and actions in the app, API calls, and an activity log of changes in a workspace. Administrative actions on a customer account are separately audited.
• Sending and delivery events — sends, deliveries, bounces, complaints, opens, clicks, replies and unsubscribes for the messages you send, returned to us by Amazon SES, Meta, your provider or your own mail server.
• Usage monitor — while a page of optyflo.com, the app, or a public form or quiz page we host is open, a periodic heartbeat with a random identifier, the page path, your IP address, an approximate location derived from it, and your browser and device type. Section 5 explains it.

Data we process on behalf of customers:

• Contacts and their engagement history — uploaded by CSV, captured by forms and lead magnets, synced from Zoom registrations or a connected CRM, or created by inbound email and WhatsApp replies. Optyflo computes an engagement score per contact (hot / warm / cold / dormant) from that history so customers can segment; the score drives no decision with legal effect on the contact.
• Webinar registrations, live attendance and no-show labels received from Zoom; quiz answers submitted on public quiz pages; and payment events (amount, status, payer identifiers) received from, or looked up in, a customer's own Razorpay or Cashfree account to trigger their flows.
• Voice-call outcomes — answered, busy, no answer, duration and keypress responses — written back to the contact for calls a customer places through Obligr.
• The IP address, browser type and approximate location of people who submit a customer's forms, quizzes, bookings or newsletter sign-ups, or who click links in a customer's messages.
• Where a customer links a WhatsApp number as a companion device, the messages sent and received on that number — including personal conversations — so they can appear in the customer's inbox (section 8).
• Website visits and conversions recorded by the optional attribution script, where a customer has enabled it (section 5).

• To provide the service — authenticate you, store your workspace, schedule and deliver messages, run flows, host public forms and quiz pages, and show you analytics.
• To keep senders healthy — run the automatic warm-up ramp, throttle sends, monitor bounce and complaint rates, suppress addresses that have unsubscribed or hard-bounced, and pause an account whose complaint rate crosses 0.3% or bounce rate crosses 3%, because one bad sender damages deliverability for everyone.
• To power AI features you invoke — the AI flow builder, campaign and subject-line drafting, WhatsApp template drafting, knowledge-base answers, per-recipient personalisation and reply drafting. See section 7.
• To bill you — record metered usage and produce statements.
• To secure and improve the product — detect abuse, debug failures, measure which features and pages are used (including through the usage monitor in section 5), and prioritise fixes. We do not build profiles of your contacts for our own purposes.
• To communicate with you — transactional email about your account (security alerts, delivery problems, sending paused) always; product news only if you opted in, and every such email carries an unsubscribe link.

We do not sell personal data, rent lists, or use customer contact data to market to those contacts ourselves.

For account holders, we process data to perform our contract with you (running the service), to comply with law (tax and accounting records, lawful requests), for our legitimate interests (security, fraud prevention, product improvement), and with your consent where the law requires it (newsletter, non-essential communications). Under the DPDP Act, opening an account and using a feature is the request that authorises the processing needed to deliver it; you may withdraw consent for optional processing at any time, and withdrawing it does not affect processing that already took place.

For contacts, the customer who messages you is responsible for having a lawful basis — typically your consent or an existing relationship — and for honouring your opt-out. Our Terms require it, and our sending pipeline enforces unsubscribe and suppression lists automatically.

WhatsApp opt-in: the customer is responsible for obtaining, and keeping a record of, each contact's opt-in before messaging them on WhatsApp. Optyflo does not store a WhatsApp opt-in record and does not independently verify that an opt-in was obtained. It blocks campaign messages to contacts who have unsubscribed, but some automated sends — such as webinar reminders, quiz and payment-journey messages, and messages from a linked-device number — do not check opt-out status.

We load no third-party analytics or advertising trackers on our own site and use no cross-site tracking cookies. What we do set on optyflo.com and in the app:

• Sign-in session cookie (authjs.session-token) — keeps you signed in — 24 hours.
• Sign-in CSRF cookie (authjs.csrf-token) — protects the sign-in form — browser session.
• Integration state cookies (gmail_oauth_state, sheets_oauth_state, zoom_oauth_state) — protect the step where you connect Google or Zoom — about 10 minutes.
• Quiz cookie (wq_sub) on public quiz pages — keeps one quiz attempt together — 2 hours.
• spc_presence_sid (browser local storage, not a cookie) — the random identifier the usage monitor uses — until you clear site data.
• Interface preferences in local storage, such as table layouts and display currency — stay in your browser — until you clear site data.

Usage monitor. We run a first-party usage monitor on optyflo.com, in the app, and on the public form and quiz pages we host for customers. While a page is open and visible, it sends a heartbeat every 20 seconds with the random identifier above, the page path and, if you are signed in, your account. We record your IP address, an approximate location (city, region and country) derived from that IP, your browser and device type, and each page you visit. We use it to operate and secure the service and to see which pages are used. It is not shared with any third party and not used for advertising. These records are deleted automatically after 90 days.

Emails sent through Optyflo may include a one-pixel open-tracking image and rewritten tracked links, where the sending customer has those features on. They record the time of an open or click, the message and recipient, and the IP address and user-agent of the request. Every marketing email carries a one-click List-Unsubscribe header and a visible unsubscribe link.

A customer may embed an optional attribution script on their own website to connect sign-ups and revenue back to campaigns. It is designed to be first-party only:

• It sets one cookie on the customer's own domain (_oft_vid, a random visitor id, 400 days) and uses no third-party cookies.
• It does no fingerprinting and makes requests to no one but Optyflo.
• It honours the Global Privacy Control signal and the browser's Do-Not-Track setting: when either is on, the script does nothing at all.
• Visitor IP addresses are stored only as a salted one-way hash.

Customers who use the attribution script, or who enable conversion uploads to an advertising platform, are responsible for disclosing it in their own privacy notice and obtaining any consent their jurisdiction requires.

Our application and database servers are hosted in India. Outbound email through our shared infrastructure is relayed by Amazon Simple Email Service in the AWS Europe (Stockholm) region; if you connect your own SMTP server or Gmail, mail leaves from that provider instead. Uploaded files are stored on our servers. If we move them to Amazon S3 or another S3-compatible store, we will name that provider and its region in section 8 before the change takes effect.

• All traffic to and from Optyflo is encrypted in transit with TLS.
• Passwords are stored as salted one-way hashes and are never recoverable. API tokens you create are stored only as one-way hashes.
• OAuth tokens (Google, Zoom, Razorpay, HighLevel), WhatsApp session keys and connected channel credentials are encrypted at rest with AES-256-GCM before they reach the database. Some older integration credentials — SMTP passwords, AiSensy, Obligr and OpenAI API keys, and webhook secrets — are not yet encrypted at rest; we are completing their migration to encrypted storage.
• Sign-in is rate-limited per account and per network address.
• Public unauthenticated endpoints (form submissions, inbound webhooks, the attribution script) are rate-limited. Inbound webhooks from Zoom, Amazon SES and Razorpay are signature-verified; other inbound webhooks are authenticated by a secret URL token and, where you configure a signing secret, by its signature. Outbound webhooks we send are signed with HMAC-SHA256.
• Access to production is limited to the people who operate the service, and administrative actions on customer accounts are written to an audit log that survives account deletion.
• We take rolling backups of the production database so that a failed release or corruption can be reversed; older backups are overwritten as new ones are taken.

No system is perfectly secure. If we learn of a breach affecting your personal data we will report it to CERT-In and the Data Protection Board of India where the law requires, and notify you without undue delay.

The AI features run on OpenAI: drafting a flow onto the canvas from a description, analysing an existing flow, writing campaign emails and subject-line options, drafting Meta-compliant WhatsApp templates, generating an email theme, answering questions from a knowledge base you upload, per-recipient AI personalisation, and drafting replies in the inbox.

• For drafting and knowledge-base features we send OpenAI only the text needed for the request you made — the brief, the flow description, or the relevant excerpts of your knowledge base.
• Contact data does go to OpenAI in two features. Per-recipient AI personalisation (the AI intro and call-to-action merge tags) sends, once per recipient at send time, that contact's name, company, notes and tags. The AI reply assistant sends the recent messages of the conversation it is drafting a reply for. We never send a whole contact list in one request.
• If you supply your own OpenAI API key, those requests are made under your OpenAI account. If we move a feature to another provider with an OpenAI-compatible API, we will list that provider in section 8 before the change takes effect.
• OpenAI processes this under its API terms, which do not permit it to train on API inputs and outputs.
• AI output is a draft. A generated flow stays a reviewable draft until you explicitly promote it, and you are responsible for reviewing anything generated before it is sent. Exception: if you add the AI auto-responder to an automation, its replies are sent without review unless the model escalates the conversation to a person.
• AI generation is capped per workspace per day and per month; the ceilings depend on your plan and are visible in your account.

We share personal data only with the providers below, only as needed to run the feature you use, and under contracts that restrict what they may do with it. Several of these are services you connect with your own account; your relationship with that provider is then governed by its terms as well. Each entry gives the provider — what it does — the data involved — where it processes it.

• Hostinger — application and database hosting, and uploaded files unless object storage is configured — all service data — India.
• Namecheap — DNS for our domains — DNS lookup metadata only; our traffic does not pass through it — global.
• Amazon Web Services — email relay through Amazon SES — message content and recipient address — Sweden (AWS Europe (Stockholm) region).
• Resend — receiving inbound email and our support mailbox — inbound messages and sender address — USA.
• Meta Platforms — the WhatsApp Business Platform (Cloud API) via embedded signup, using your own WhatsApp Business number; and the Conversions API if you enable ad attribution — phone number and message content; hashed email, phone and name for conversions — USA / global. Optyflo is a Meta Tech Provider; Meta bills your business directly for WhatsApp messages and we do not meter them, unless you connected under Optyflo's WhatsApp solution, in which case we charge each message to your prepaid credit wallet (section 8A).
• AiSensy and Wati — WhatsApp template messaging when you connect such an account — phone number and template variables — India.
• Obligr — automated outbound voice calls, IVR and SMS to Indian numbers when you connect an Obligr account — phone number, call outcome and keypress — India.
• Zoom — meeting creation and binding, registrant sync, attendance and live-session events for your webinars — name, email, join and leave times — USA.
• Google — sign-in with Google, sending from your Gmail mailbox (send scope only), reading and writing the Google Sheets you choose, and Google Ads conversion uploads if you enable them — as configured by you — USA. See the Google note below.
• Razorpay (Optyflo's own account) — processing your wallet top-ups and plan purchases — your name, email and phone number prefilled on the checkout, the amount and the order and payment IDs — India. Card, UPI and bank details are handled by Razorpay alone.
• Razorpay and Cashfree — payment notifications, and payment and refund lookups using your own account keys, to trigger flows and attribute revenue — payer name, email, phone, amount and payment id — India. We never see card details.
• HighLevel / LeadConnector — CRM sync when you connect it — contact fields — USA.
• TikTok — Events API conversion uploads, if you enable them — hashed identifiers and event details — processed where TikTok operates.
• OpenAI — the AI features in section 7 — see section 7 — USA.
• The accounting providers we use to invoice you — billing details — India.

Linked-device WhatsApp (optional). If you link a personal or WhatsApp Business app number by scanning a QR code, Optyflo connects to WhatsApp as a linked device on your behalf using an unofficial client. Messages sent and received on that number — including personal conversations — pass through and are stored on our servers so they can appear in your inbox. This connection is not provided or endorsed by WhatsApp or Meta, may be disconnected or lead to the number being banned at any time, and is not part of our Meta Tech Provider services.

Google API Services: Optyflo's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Gmail access only to send the messages you compose or schedule, and Sheets access only to read and write the spreadsheets you choose (by pasting their link or creating one from Optyflo). We do not request access to your Google Drive. We never read your inbox and never transfer Google user data to third parties except as needed to provide those features.

Ad-conversion uploads to Meta, Google and TikTok transmit hashed identifiers (for example a SHA-256 of a lowercased email) plus event details; the platform matches them against its own users. These uploads are off unless you turn them on and connect the ad account.

We may also disclose data when the law requires it, to enforce our Terms, to protect the rights or safety of Optyflo, our customers or the public, or as part of a merger or acquisition, in which case this policy continues to apply to the transferred data.

This section covers what happens when you connect a WhatsApp Business number to Optyflo through Meta's Embedded Signup — the Connect with Facebook button on the Optyflo WhatsApp tile under Account → Connections. Optyflo is a Meta Tech Provider: we operate the WhatsApp Business Platform (Cloud API) on behalf of your business. For the messages and the contact data involved we act as your processor (section 1); you remain responsible for your contacts' opt-in (section 4).

What we receive from Meta when you connect:

• The ID of the WhatsApp Business Account (WABA) you choose in Meta's window, and the phone number ID of the number you choose. Meta's window also reports your Meta business portfolio ID to the page; we do not store it.
• A business access token Meta issues to Optyflo for that WhatsApp Business Account. We use it straight away to confirm the account and number really belong to that grant, to subscribe Optyflo to the account's message and template webhooks, and to register the number for the Cloud API.
• The account's name, the number's display phone number and its verified business name, which we use to label the connection in your workspace.
• Where we register the number, the six-digit two-step-verification PIN we set for it, kept so the same number can be registered again later.
• We do not request or store your Facebook profile, friends, posts or any other personal Facebook data. The Facebook login only authorises access to the WhatsApp Business Account you select.

How it is protected: the WABA ID, phone number ID, access token and PIN are stored together as one record encrypted at rest with AES-256-GCM, and are decrypted only on our servers to send and receive messages for you. The token is never shown in the app or returned by our API, and is never used for any account other than yours. A number already connected by another workspace cannot be connected again.

What we process to send and receive on your behalf:

• Outbound messages — the recipient's phone number and either the approved template's name and the values filled into it, or the text of a free-form reply. We pass these to Meta's Cloud API when you, a teammate or one of your automations sends.
• Inbound messages — when someone writes to your number, Meta delivers the message to our webhook. If the sender's number matches a contact in your workspace, we add the message (sender number, text or button reply, and Meta's message ID) to that contact's conversation in your Inbox, and it can trigger your automations. A message from a number that is not one of your contacts is not stored; only Meta's message ID is kept, for up to 7 days, so a redelivery is not processed twice.
• Delivery receipts — Meta's sent, delivered, read and failed statuses, recorded against the message they belong to.
• Template updates — approval, rejection, pause, category and quality changes Meta reports for your message templates, which update the template in your workspace and, when a template is rejected, paused, disabled or moved to Marketing, email you.
• Every webhook from Meta is checked against Meta's signature before anything is processed, and is matched to your workspace by your phone number ID or WABA ID. Events for a number no workspace has connected are discarded.

We use this data only to provide the WhatsApp features you use. We do not sell it, do not use it for advertising or to build profiles, and do not share it with anyone except Meta, which carries the messages, and the subprocessors in section 8 as needed to run the service. Message content reaches our AI provider only when you use an AI feature that needs it (section 7).

Billing: by default Meta bills your business directly and we meter nothing. If you connected under Optyflo's WhatsApp solution, Meta bills Optyflo and we charge each message Meta accepts to your prepaid credit wallet at the published rate; we then keep a ledger entry per charged message with its price, its rate type and a reference to the contact (Terms, section 3A).

Retention: the connection record — WABA ID, phone number ID, access token and PIN — is deleted from our database as soon as you disconnect. Messages, delivery statuses and templates stay in your workspace so your history is not lost, until you delete them or close your account (section 10). Credit-ledger entries are kept as accounting records.

How to disconnect: in Optyflo open Account → Connections, choose the Optyflo WhatsApp tile, then Disconnect. To also withdraw Optyflo's access on Meta's side, remove Optyflo from your business portfolio's connected apps in Meta Business Settings, or from Business Integrations in your Facebook settings. Step-by-step instructions, and how to ask us to delete all of your data, are at optyflo.com/data-deletion.

Your data is stored in India. Email relayed through our shared Amazon SES account passes through the EU (Stockholm). The providers in section 8 may process data in the United States or other countries where they operate. Where the GDPR applies we rely on the providers' Standard Contractual Clauses or an adequacy decision; where the DPDP Act applies we transfer only to countries not restricted by the Central Government.

These are the deletions that run automatically today:

• Usage-monitor records (section 5) — deleted 90 days after they were last updated.
• Contacts you delete — kept in the Deleted tab, where you can restore them, for 30 days, then permanently removed.
• Completed automation runs and automation logs — deleted after 90 days.

Everything else is kept until it is deleted:

• Account and workspace data — kept while your account is active.
• WhatsApp Business connection (WABA ID, phone number ID, access token, PIN) — deleted as soon as you disconnect it (section 8A).
• When you ask us to close your account — we delete the account and the workspace data in it from live systems. Database backups are overwritten on a rolling basis after that.
• Suppression records — email addresses and numbers that have unsubscribed, bounced or complained are kept so the opt-out keeps being honoured even after the surrounding contact record is deleted.
• Invoices, usage and credit ledgers, Razorpay payment records and admin audit logs — kept for as long as Indian tax and company law require, including after your account is closed.
• IP addresses captured on form submissions, quizzes, bookings and link clicks — kept with the record they belong to, and deleted with it.
• Attribution visitor records and conversion events — kept with the customer's workspace; the first-party visitor cookie expires after 400 days.
• Server logs — rotated on a rolling basis.

Wherever you are, you can ask us to access, correct, export, restrict or delete the personal data we hold about you, to object to processing based on legitimate interests, and to withdraw consent you previously gave. Under the DPDP Act you may also ask for a summary of the personal data we process about you and who we shared it with, have a grievance addressed, and nominate someone to exercise these rights for you if you die or become incapable. Under the GDPR you may complain to your supervisory authority; under the CCPA you may opt out of "sale" or "sharing" — we do neither — and you will not be discriminated against for exercising a right.

• Account holders — you can update your profile in Settings, export your contacts as CSV from the Contacts page, revoke a connected integration from Account → Connections, and delete an API token from Developer settings. To export other data, or to close your account and erase its data, email hello@optyflo.com from the address on the account; we will confirm your identity, act within 30 days, and confirm completion in writing.
• Contacts of our customers — use the unsubscribe link in any email to stop email. To stop WhatsApp, SMS or calls, contact the business that messaged you — a STOP reply on WhatsApp is not yet processed automatically by Optyflo. If you cannot reach them, write to hello@optyflo.com with the business name and your number or address; we will forward the request, suppress your number or address in that business's workspace, and confirm what was done.

We acknowledge privacy requests within one business day and resolve them within 30 days, or tell you why we need longer. We may ask you to verify your identity first.

Optyflo is a business tool. You must be at least 18 to hold an account, and you confirm this when you sign up. Customers may not knowingly use the service to collect or message data about children under 18 without the verifiable parental consent their law requires. If you believe a child's data has reached us, email hello@optyflo.com and we will delete it.

When we add an integration, a subprocessor or a new kind of processing, we update this page and the effective date. For material changes we also email account holders at least 14 days before they take effect. Continued use after that date means you accept the updated policy.

Grievance Officer, for the purposes of the DPDP Act, the Information Technology Act, 2000 and the rules under them: Wealth Connects LLP, Flat No 12109, Tower 7, Crossing Republik, Ghaziabad, Uttar Pradesh 201016, India. Further details are available on request at hello@optyflo.com.

Grievances are acknowledged within one business day and addressed within 30 days. If you are not satisfied with our response, you may complain to the Data Protection Board of India.

Data-processing agreements (DPA), subprocessor questions and anything else: hello@optyflo.com. Privacy questions are answered within one business day.