GetFluxly Start Free

Legal

Privacy Policy

This policy describes what we collect on www.getfluxly.com and how we use it. It only covers this marketing website and the GetFluxly service. It does not cover the GetFluxly product that customers install in their own apps via the SDK or HTTP Events API. Customers using GetFluxly are responsible for their own end-user privacy notices.

Last updated: July 11, 2026

1. Who we are

GetFluxly ("GetFluxly," " we," "us," or "our") is a product analytics, lifecycle automation, and email platform.

The Service is operated by Dinesh Miriyala, a sole proprietorship established under the laws of India. For any privacy question or to exercise the rights described below, email support@getfluxly.com.

2. What we collect and why

2.1 Visitor analytics, before you sign up

While you are anonymously browsing www.getfluxly.com, our website stores nothing about you in your browser: no cookie, no localStorage entry, and no sessionStorage entry of ours. What we collect happens on our servers, from the request itself:

  • Page views: the URL of the page, page title, referrer, and any UTM parameters, read from the request and the page you are on.
  • A temporary, server-derived identifier (prefixed gfh_): when an event reaches our servers, we combine your IP address, browser user agent, and a random salt value into a single HMAC-SHA256 hash. The salt is regenerated every day and deleted after about 48 hours, so this identifier cannot be used to follow you from one day to the next. It only groups the page views and events you generate around a single day.
  • Approximate location: country, region, and city, computed by our hosting network's edge (Cloudflare) before your request reaches our application.
  • Standard server log data: IP address (stored only in anonymized form, see below), user agent, and timestamp.

Your IP address is never stored in full. We anonymize it immediately: IPv4 addresses are stored with the last segment zeroed out (a /24 network), and IPv6 addresses are truncated to a /48 network. The unanonymized address is used only for the instant needed to compute the values above; it is never written to disk.

2.2 What we store after you sign up

Signing up for GetFluxly is the moment we start keeping anything about you in your browser, and it is the consent action itself: nothing above is gated on a choice, because nothing is stored to gate. Once you create an account, we write the following so the product works for a signed-in user:

  • gf_anon_id (localStorage and a first-party cookie): an id that groups your page views and events into one profile.
  • gf_external_id: your account identifier.
  • gf_traits: a few basic profile attributes, such as your name or plan.
  • gf_first_touch (localStorage): the referrer and UTM parameters from the first time you visited, kept so we can credit the right marketing channel for your signup.
  • gf_buffer (sessionStorage, short-lived): a temporary snapshot of an event still in flight when a page unloads, cleared once it sends.
  • gf_consent / gf_optout: one flag recording whether you have explicitly opted in or opted out, set automatically at signup or directly if you use the opt out control in section 5.

From this point your activity is tied to your account. It is identified, not anonymous: that is by design, so GetFluxly can show a signed-in user their own account's usage and events. We also stitch the anonymous browsing you did earlier the same day onto your new profile using the temporary server hash from section 2.1; browsing from earlier days is not linked, because that day's salt has already been deleted.

2.3 Contact form

When you submit a contact or get-in-touch form on the site, we collect the information you provide:

  • First and last name
  • Work email
  • Company name (optional)
  • Your message
  • Any UTM parameters and the referrer URL associated with your visit

We use this only to respond to your inquiry and reply to you. We do not sell or rent it.

2.4 Email correspondence

If you email us (for example, support@getfluxly.com), we keep the message and your email address so we can respond and so we have a record of the conversation.

3. How we use the information

  • To operate, secure, and improve www.getfluxly.com.
  • To respond to your sales and contact inquiries.
  • To prioritize SDK and integration work based on what customers are using today.
  • To measure aggregate site usage and understand which marketing channels work.
  • To prevent fraud and abuse of the website and the request form.
  • To comply with legal obligations (e.g., responding to lawful requests from authorities).

4. Service providers we share data with

We use a small number of vetted infrastructure providers to run the site. We share the minimum information needed to operate the service:

  • Supabase: stores contact form submissions. Hosted on AWS infrastructure.
  • Vercel: hosts and serves the website and its API routes. Receives standard request logs.
  • Email providers: when we email you in response to your inquiry, the message passes through our email provider in transit.

We do not sell or rent your information to third parties. We may disclose information when we're required to by law or to protect rights, property, or safety.

5. Cookies and similar technologies

Before you sign up, the only cookie present for your visit is Cloudflare's __cf_bm, a strictly necessary cookie our hosting network sets to tell real browsers from bots and keep the site available. We do not configure it, and we set no cookie, localStorage entry, or sessionStorage entry of our own while you are anonymous.

After you sign up, we write the browser storage listed in section 2.2 (gf_anon_id as both a cookie and a localStorage entry, plus gf_external_id, gf_traits, gf_first_touch, gf_buffer, and gf_consent / gf_optout) so the product works for your signed-in account.

You can clear any of this at any time using your browser's site-data controls. Doing so will not affect your ability to browse the site anonymously, though it will sign you out if you are signed in.

Opt out. If you would rather not be tracked at all, even after signing up, use the control below. It stops further events from your browser and stores one flag ( gf_optout) recording that choice.

6. How long we keep it

  • Pseudonymized event rows: kept for up to 180 days and then deleted.
  • The daily salt used to derive the temporary gfh_ identifier: deleted after about 48 hours; it is never written to a durable store beyond that window.
  • Contact submissions: kept for a reasonable period so we have a record of the conversation. You can ask us to delete your submission at any time.
  • Email correspondence: kept while it's useful for the conversation and our records.

7. International transfers

Our service providers (Supabase, Vercel) primarily process data in the United States. If you are visiting from the European Economic Area, the United Kingdom, or another region with data-transfer restrictions, your information may be transferred to and processed in the United States. Where required, we rely on standard contractual clauses or equivalent safeguards offered by these providers.

8. Your rights

Depending on where you live (EU/UK, California, and others) you may have the right to:

  • Access the personal information we hold about you.
  • Correct inaccurate information.
  • Delete information we hold about you.
  • Object to or restrict certain processing.
  • Receive a portable copy of the information.
  • Withdraw consent for any processing that relies on consent (this won't affect lawful processing that already happened).

To make any of these requests, email support@getfluxly.com from the address tied to your data, or include enough detail for us to identify your records. We'll respond within a reasonable timeframe and at no charge unless your request is clearly excessive.

9. Children

GetFluxly is a B2B service and is not directed to children. We don't knowingly collect personal information from anyone under 16. If you believe a child has submitted information, email support@getfluxly.com and we'll delete it.

10. Security

We use industry-standard measures to protect information in transit and at rest, including TLS for all traffic to the site, encryption at rest provided by our infrastructure providers, and least-privilege access controls. No system is perfectly secure; if you believe you've found a vulnerability, please email support@getfluxly.com.

11. Consent and privacy signals

GetFluxly's SDKs honor end-user privacy signals. When a visitor has not granted consent, or sends a Global Privacy Control (GPC) or Do Not Track (DNT) signal, events from that visitor are suppressed or de-identified at ingest according to the configured consent mode. Certain regions (for example, California) are pinned to honor GPC regardless of configuration.

These guardrails are not a substitute for your own compliance. As the customer, you remain responsible for obtaining, recording, and honoring valid consent from your end users under GDPR, CCPA/CPRA, and other applicable laws. GetFluxly provides the tooling; you provide the legal basis.

Per-channel pixel and tracking controls are on our near-term roadmap to give you finer-grained, channel-by-channel alignment with regional authorities.

12. Changes to this policy

When we change this policy in a meaningful way, we'll update the "Last updated" date at the top and, where appropriate, post a notice on the site or email people who have contacted us.

13. Contact

For any privacy question, request, or complaint, email support@getfluxly.com.