Email:
team@qback.au
Sydney:
5 Fleet St,
North Parramatta NSW 2151
Perth:
Level 1, FLUX 191 St Georges Terrace,
Perth WA 6000
Your data is protected through transparent practices, strong controls, and carefully vetted vendors.
We collect public market signals and limited customer-submitted content to deliver insights.
We ingest widely available information such as social posts, news, and ASX announcements. Although these sources are public, we still process them responsibly and in line with applicable laws and our contractual commitments.
Manual Activities like calls, meetings, presentations, events, and files are private within your organisation. Only authorised users in that organisation can view them.
Each ticker equals one organisation. Users only see organisations they belong to. Manual Activities are visible to users within that organisation by design to support collaboration.
Files are stored in Google Cloud Storage. We use short-lived, signed URLs for uploads and downloads to prevent unauthorised access.
We layer controls across identity, application, data, and vendors.
We use Outseta for auth and account gating. Outseta supports cookie-based tokens that can persist auth across domains if configured, and provides signed webhook verification using HMAC-SHA256.
Origin protection with CORS for approved domains
Input validation and structured error handling to avoid leaking sensitive details
Request timeouts and rate limiting to deter abuse
Our primary data store is PostgreSQL on Google Cloud SQL. All connections are encrypted in transit. Secrets are kept in secure environment variables. We follow documented retention and deletion processes and invalidate caches to ensure data freshness.
Google Cloud Storage with isolated buckets, tight IAM, and automatically generated paths to avoid collisions and enumeration.
We only share the minimum necessary data and use secure APIs.
Outseta for authentication, subscriptions, CRM and billing workflows. Outseta publishes a Privacy Policy that includes GDPR rights and offers a standard DPA for customers. Outseta notes its servers run on AWS and that Stripe is PCI-DSS compliant for payment processing.
Google Cloud Platform for hosting, databases, and storage.
Pinecone for vector storage of embeddings.
OpenAI for selected AI processing, with a DPA in place between us and OpenAI.
Webhooks to and from vendors are validated and signed. Outseta provides webhook signatures you can verify.
You can connect your organisation’s own Google Analytics 4 property to Quarterback, so your website traffic and sign-ups appear beside your announcements and investor activity. Connecting
is optional, and only a signed-in user of your organisation can do it.
What we access
When you sign in with Google, you grant Quarterback read-only access to Google Analytics (the analytics.readonly permission). We cannot change your Analytics settings, and we do not ask for your Gmail, Drive, contacts or any other Google data.
With that access, we read the names and IDs of the Analytics accounts and properties your Google account can see, so you can choose which property to connect. For the property you choose, we
read daily sessions, users and page views by page and traffic source, and the daily count of the event you choose as a sign-up. These are totals Google Analytics has already aggregated. We do not receive the names, email addresses or other personal details of your website visitors.
How we use it
We use your Google Analytics data only to show it to authorised users in your organisation inside Quarterback: charts of your website traffic and sign-ups beside your announcements and activity,
and answers to your own users’ questions to Quarterback’s assistant about your own figures. Like your Manual Activities, it is private to your organisation.
Quarterback’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 we protect it
Your Google Analytics data and the access Google grants us are stored on Google Cloud in Australia (Sydney). The access token is encrypted with a dedicated Google Cloud Key Management Service key and tied to your organisation, so it cannot be used for any other customer. We never show the token to anyone, and it never appears in our logs.
Sharing
We do not share your Google Analytics data with third parties, except the sub-processors that run Quarterback for us (listed in our sub-processor register), who may process it only to provide Quarterback to you, and where the law requires disclosure.
Removing access and deleting your data
You can disconnect Google Analytics at any time from Settings → Integrations in Quarterback. When you do, we stop collecting immediately and delete the stored access token, we ask Google to
revoke Quarterback’s access, and we delete the Google Analytics figures we collected for your organisation within 30 days. You can also remove Quarterback from your Google account at any time under Third-party apps and services, and we will then stop collecting at the next scheduled update. To ask us to delete your Google Analytics data sooner, email team@qback.au.
We support GDPR-style rights and offer a DPA for customers that require one. Australian businesses can be subject to GDPR when handling EU personal data — a DPA is the expected instrument.
We retain customer data for the life of the account unless your contract specifies otherwise. We honour deletion requests and remove data from active systems and backups on a defined schedule.
We monitor for anomalies, triage potential incidents, and notify affected customers without undue delay in line with our contractual and legal obligations.
We maintain a live list of sub-processors and notify customers before material changes.