Privacy Policy

Who we are

SELLERFLAG is the registered business name of Priya Mathai, Individual/Sole Trader (ABN 60 569 344 758), in Australia. We trade as SellerFlag ("we", "us", "our").

This policy covers sellerflag.com.au, the SellerFlag app, customer support, sales activity, missed-call text-back and the Voice AI assistant. We apply Australian privacy requirements that apply to us and use the Australian Privacy Principles as our handling framework.

Agents, prospects & account information

We collect information you provide when requesting a test, signing up or contacting support, including your name, agency, Australian mobile number, email address, carrier, message preferences and the details of your request.

For subscribers we also keep account status, forwarding and live-test results, service-health events, billing identifiers, support history and actions taken in the app. Stripe handles card details; SellerFlag stores only limited payment references and card information such as brand and last four digits.

If you respond to a SellerFlag advertisement or sales call, we may keep your contact details, agency, source, contact history, factual notes, suppression status and agreed follow-up. Imported or sourced leads are reviewed before calling and a do-not-contact request is recorded and respected.

If you start setting up an account and stop partway, we record the setup step you reached. Our team is alerted through Telegram and by a text to Priya from SellerFlag, who may call or text your account mobile to offer help with setup. Tell us if you’d rather not be contacted and we’ll stop. We delete these alert records after 30 days; Telegram and Twilio may keep their own copies under their policies.

If calls reach your SellerFlag number before setup is finished, we text your account mobile about each one (up to 10 a day, then one evening summary) and tell our team. Reply STOP to stop these texts.

Our team’s sales coach uses Anthropic’s Claude, reached through OpenRouter (both process in the United States), to help prepare calls. It can receive a lead’s first name, business name, setup stage and our call notes, never phone numbers or emails. Coach conversations are deleted after 30 days.

Callers who contact an agent

When you call an agent who uses SellerFlag and the agent does not answer, their carrier may forward the call to a SellerFlag number. We receive the caller and destination numbers, provider identifiers, timestamps and delivery events needed to create a Catch and send the agent’s configured text-back.

On the SMS plan, SellerFlag plays a short automated message and ends the forwarded call without recording it or taking voicemail. If you reply by text, we store the message and related delivery events so the agent can read and answer it.

On the Voice plan, Twilio and ElevenLabs process the call audio to let the AI assistant respond. Isabel identifies herself as AI and explains that a transcript is created. We store the transcript, caller-provided details, call metadata and a brief for the agent to review and follow up. Audio recording is disabled. The agent reviews the greeting and business instructions before the assistant is connected.

The agent can see the conversation and classify its outcome. Reply STOP, UNSUBSCRIBE, CANCEL, END or QUIT to stop further automated messages through that SellerFlag number. We keep the suppression record so the opt-out continues to work.

Automated seller suggestions

SellerFlag first checks a reply for limited seller-related phrases. When a reply remains ambiguous and the classifier is enabled, a short portion of the message may be sent to OpenRouter and the configured AI model solely to suggest whether it contains possible seller intent.

The model is instructed not to invent details and can return only short reasons found in the message. The result is a suggestion, not an automated decision: the agent must confirm, correct or dismiss it.

Free Voice demonstration

When you request a Voice demo, you ask for a verification text, one transcribed AI demo call, a flag SMS and one separate trial-invitation SMS. The invitation follows only after carrier confirmation of flag delivery, subject to availability and limits. This does not start a subscription or enrol you in recurring marketing.

Use fictional details. Twilio carries the call and texts; ElevenLabs processes the conversation. We do not store call audio. The private transcript and captured demo details are scheduled for deletion within seven days; provider outages can delay deletion. Reply STOP to prevent further demo texts.

If the Meta Pixel is active in your browser (see Website data & analytics), we also tell Meta that a demo call was requested, without your name, mobile number or call details.

Free SMS demonstration

When you request the sample flag, you ask us to send a fictional sample SMS and one trial-invitation SMS to the Australian mobile you enter. Requesting a sample does not create an account or start a subscription. We do not add the number to recurring marketing texts.

We use your first name, mobile number, request time and consent version to deliver those two messages through Twilio. The invitation is sent only after carrier confirmation of sample delivery, subject to demo availability and limits. Reply STOP to prevent further demo texts.

Demo session records expire after one day. We then keep a copy with your first name, mobile number, consent version, the demo’s times, campaign and page labels and delivery status for 30 days from your request, so we can look up your demo and answer questions about it. We don’t use this copy to contact you. Our background cleanup deletes it after 30 days, or sooner if you reply STOP. Hashed number counters expire after eight days; opt-out records are kept to respect your choice. Twilio may retain delivery and billing records under its own policies. A temporary browser-session token lets you check delivery without entering your number again. Aggregate demo events contain no name or mobile number. If the Meta Pixel is active in your browser (see Website data & analytics), we also tell Meta that a sample was requested, without your name or mobile number.

When you request the sample on our website, our server may also report that request and the demo’s later steps to Meta through Meta’s Conversions API: that the sample was delivered, that you opened the trial link and that you replied CALL or SETUP. This can happen even if your browser blocks the Meta Pixel itself. These reports carry any Meta ad-click reference and Meta browser ID from your browser, plus the IP address and browser details of your request, never your name or mobile number. Nothing is reported if your browser sends Do Not Track or Global Privacy Control when you request the sample, and a trial link opened in a browser that sends either signal is not reported. We delete these details after 7 days, or sooner if you reply STOP.

We retain daily totals of sample requests, carrier-confirmed deliveries, trial-link opens and CALL or SETUP replies after demo sessions expire. These totals contain no names, phone numbers, IP addresses or individual identifiers. They may be grouped by a fixed campaign label and page version. Internal test activity is reported separately. For 7 days after a request, a trial-link open or CALL or SETUP reply is counted toward that demo’s campaign and page labels. For this, the labels are also stored with the demo’s trial-link record, which holds no name or mobile number and is deleted after 7 days, and with the hashed number counter above, which expires after eight days and also keeps your first name, so our team knows who replied. Opening a link is not proof of signup or a human visit.

If you reply CALL or SETUP to a demo text, you are asking us to help you set up SellerFlag: we record your name, mobile number, the demo’s ad, your reply and its time, and alert our team through Telegram and by a text to Priya from SellerFlag. Priya may call you from 0491 630 448 up to twice within 7 days of your reply, during calling hours, and text you once if she misses you. We send one acknowledgement text. We delete these records 30 days after your latest reply, and queued alerts after 30 days; Telegram and Twilio may keep their own copies under their policies. If you send any other reply, we alert our team through Telegram and send one text asking you to reply CALL if you’d like a call; we don’t call or text you about it otherwise. Reply STOP at any time to stop demo texts and calls.

How we use information

We use personal information to provide and secure SellerFlag, verify accounts, provision numbers, process calls and messages, show Catch receipts, deliver alerts, manage billing, answer support requests, prevent abuse, maintain opt-outs and improve service reliability.

We use prospect information to respond to enquiries, arrange demonstrations and conduct lawful sales follow-up. We do not sell personal information or use caller conversations to market SellerFlag.

Website data & analytics

Our website and application hosts receive ordinary technical request data such as IP address, device and browser information, request time and security logs. The app uses necessary browser storage to keep you signed in, preserve setup state and save unsent reply drafts on your device.

SellerFlag measures its own website using fixed page, campaign and event labels, such as a page visit or a demo button click. A random identifier in tab session storage rotates daily to limit duplicate counts; it is not a cross-site identifier. The analytics endpoint does not store full URLs, names, phone numbers, transcripts or raw IP addresses. It honours browser Do Not Track and Global Privacy Control signals. Short-lived duplicate-protection records are scheduled for deletion after two days and website aggregates after 180 days; outages may delay cleanup. Ordinary hosting security logs are separate.

Our public website at sellerflag.com.au also loads the Meta Pixel so we can measure and improve our Facebook and Instagram advertising. It sets Meta cookies on this site and sends Meta the page address, browser and device information, your IP address and any Meta ad-click reference, which Meta may link to a Facebook or Instagram account. When you request a free SMS sample or Voice demo call, we also tell Meta that a demo was requested; for SMS samples our server may report the same request and the demo’s later steps (see Free SMS demonstration). We do not send Meta your name, mobile number or anything else you type into our forms, and automatic collection of form entries is switched off. The pixel does not load if your browser sends Do Not Track or Global Privacy Control, and it is never loaded inside the SellerFlag app. Meta processes this information under its own privacy policy and may process it outside Australia.

If you turn on optional advertising measurement in your account, we use Meta’s Conversions API to report confirmed account registration and trial activation. This shares event times, a limited SellerFlag page address, Meta ad-click references when available, browser/device information, IP address and a coded (hashed) account identifier. Hashing does not make the information anonymous. We do not send your name, email, mobile number, caller details, conversations, property addresses or card information through this integration. No Meta tracking script is loaded inside your SellerFlag inbox or admin dashboard.

The advertising choice starts off and does not affect your service, price or trial. Change it at Account → Privacy choices. Turning it off stops future reports; data already sent to Meta is not automatically recalled. We remove the locally stored matching context when you opt out or after 90 days. Advertising-click references may be retained temporarily in browser session storage as you move from the website to signup. Meta processes information under its own privacy policy, including for ad measurement and delivery, and may process it outside Australia.

Service providers & disclosure

We use service providers only as needed to run SellerFlag: Netlify for the public website; Railway for the application and API; Google Firebase for authentication and the Australian-hosted Firestore database and first-party analytics; Google Workspace for business email; Twilio for calls and SMS; ElevenLabs and its configured model providers for the Voice assistant and transcription; Stripe for payment setup and subscriptions; OpenRouter and the selected model provider for optional classification; Anthropic for our team’s internal sales coach; Telegram for restricted operational alerts; Meta Platforms for advertising measurement on the public website and optional Conversions API reporting; and Hnry for sole-trader accounting and tax administration.

Providers process information under their own security and privacy terms. We may also disclose information where required by law, to investigate misuse or security incidents, or in connection with a business transfer subject to appropriate protections.

Overseas access

Some providers may process or support data outside Australia. Authorised sales contractors may work from the Philippines and receive only the prospect information needed for compliant outreach. Subscriber conversations and caller data are not part of the caller sales workspace.

Operational support personnel access account or conversation information only where needed to resolve a specific service issue and are subject to role restrictions and confidentiality obligations.

Security, sharing & retention

We use role-based access, Firebase authentication, expiring one-time verification codes, signed provider webhooks, audit events and other reasonable safeguards. No internet service can guarantee absolute security.

Agent-created proof links hide caller numbers and message content by default, use an unguessable token and expire after seven days. An agent can choose to include a caller quote and is responsible for that choice.

We keep information only for as long as reasonably needed to provide the service, maintain opt-outs, resolve disputes, prevent fraud and meet tax or legal obligations. Some operational and billing records must be retained after an account closes. We delete or de-identify information when it is no longer required, subject to backups and lawful retention requirements.

Access, correction & complaints

You can ask to access or correct personal information we hold, request deletion where applicable, or make a privacy complaint by using support inside your SellerFlag account, emailing hello@sellerflag.com.au, or calling the number below. We may need to verify your identity first.

If information belongs to an agent’s caller conversation, we may involve that agent because it forms part of their customer relationship. If a privacy complaint is not resolved, you may contact the Office of the Australian Information Commissioner at oaic.gov.au.

Changes to this policy

We may update this policy as SellerFlag changes. The current version and its last-updated date will remain available on this page.