Privacy

Privacy Policy

What we collect, what we do with it, and what we never do with it. Written to be read, not to be survived.

Last updated 21 October 2026

Who we are

Unsocial Studiio (ABN 88 998 861 786) operates the Unsocial Studiio platform at app.unsocialstudiio.com. We are based in Wollongong, New South Wales, Australia.

This policy covers the platform. If you are a client of our agency services rather than a user of the platform, the same principles apply and the same contact details reach us.

For anything in this policy, write to support@unsocialstudiio.com.

Who this is about

Four kinds of people appear in this policy, and it matters which one you are.

Studios. Agencies and studios who hold an account with us, and the people on their teams. They sign in, and connect their own accounts on other platforms.
A studio's clients. Businesses a studio works for, and the people at them. A studio can invite a client to sign in to a portal and see what the studio chooses to share, and can send a client a link to connect its own Instagram and Facebook. Otherwise a client's information reaches us because a studio, acting with their permission, typed it in or connected an account that contains it.
The people a client deals with. Someone who comments on or reviews a client's business, a lead, someone who books a call through a studio's booking page, or someone whose street is a job on a client's map. Their information reaches us through the accounts a studio connects and what a studio types in, or, for a booking, from the person themselves.
Visitors. Anyone who opens our pages, and anyone who joins our waitlist.

If you are a studio's client, or somebody a client deals with, and want to know what is held about you, ask the studio you work with first. They control the account. You can also contact us directly and we will help.

What we collect

Information you give us

Your name, email address and the name of your business, when you create an account, and a phone number and contact name if you add them.
About your clients: their business details and, if you add them, a contact person's name, email address, phone number and location, and a billing email address.
Anything you type into the product: content plans, drafts, captions, notes, task details.
Photos, videos and files you upload. They can show your clients, their staff and their customers.
Your hours, if you use the clock in the side menu: when you start and stop it, and how long each run was. It is kept for your studio so you can see your own time by day and by week, and you can remove any run from Settings. A removed run stops counting at once, and the record that it existed is kept until your studio's account is deleted. Nobody outside your studio sees it, apart from the people who run the platform, as the Security section says.
A problem report, if you press Send a report: your name, the page, what did not load, your note if you write one, and your browser.
If you book a call through a studio's booking page: your name and email address, and your phone number, business name and notes if you give them. They go into the host's Google Calendar and, if the studio's plan includes leads, onto the studio's list of leads, which we keep a copy of.
If you join our waitlist: your email address, your studio's name if you give it, the plan you chose, and the wording you agreed to and when.
Correspondence with us.

Information recorded as you use the platform

The IP address and browser of each device you sign in on, so you can see your signed-in devices and sign them out.
A record of who did what in an account, such as inviting someone, changing the plan, connecting or disconnecting an account, downloading the account's data or closing it, with the email address and IP address behind it. A failed attempt to sign in with Google is recorded the same way.
A record of each fault, so we can fix it. If a page breaks in your browser, the page sends us its address without anything after a question mark, the error message, where in our code it happened, and how many times. It never sends what is on the page or what you typed. Anything shaped like a password, a key or a token is removed from every fault record before it is kept. A record is filed under your studio, not your name, only the people who run the platform can read it, and it is deleted 30 days after the fault last happened.
Counts of attempts at things like signing in, resetting a password or booking a call, so nobody can flood them. Each count is filed under a code made from the IP address or email address with a secret key, never under the address itself, and is deleted within an hour of its window ending. No window is longer than a day.
If an email we send you bounces for good, you mark it as spam, or our email provider refuses to send to your address from its own list, your email address, which of these it was, what was said and when, so we stop sending that address our notices. Emails you ask for, such as a password reset, still go. Only the people who run the platform can see this list.

Information from accounts you connect

The platform is useful because it reaches the accounts you already run. You choose which to connect, and you can disconnect any of them at any time. We only ever request the narrowest set of permissions the feature needs.

Billing information

Subscriptions are handled by Stripe. Card numbers never reach our systems. Stripe holds them. We hold a customer reference, the plan you are on, the status of your subscription, the billing email address you give us, and a record of each message Stripe sends us about your payments. Once we have acted on a message we keep only what we acted on; if acting on it fails, we keep the whole message, which can include the name, email address and billing address on the account. Stripe's own privacy policy governs the payment data itself.

The detail

What we access from Google

When a studio connects its Google Business Profile, we ask for two permissions and no others.

Permission	What it lets us do
business.manage	Read the Business Profile locations you manage, read the reviews left on them, and post a reply to a review when you press send.
userinfo.email	Show you which Google account you connected, so you can tell one from another. Nothing else.

How we handle it

We store an encrypted refresh token, and little else. That is the credential that lets us reconnect to Google on your behalf. It is encrypted at rest. Beside it we keep the Google account's email address, the permissions it granted, and which Business Profile location belongs to each client.

Review text is displayed, never copied into our own store. When you open the reviews page we fetch it from Google, show it to you, and let it go. We do not keep a copy.

Nothing is ever posted automatically. Every reply to a review or a comment is sent because a person read it, wrote a response, and pressed send.

Disconnecting actually disconnects. When you disconnect a Google account we call Google's own revoke endpoint, which invalidates the token at Google's end, rather than simply deleting our copy and leaving the grant standing.

Google Calendar

Anyone at a studio can also connect their own Google Calendar. It is a separate connection from the Business Profile, with its own Google consent screen. We ask for the four permissions below, and the fifth only if that person presses Allow bookings.

Permission	What it lets us do
calendar.calendarlist.readonly	List the calendars on the account, so the person can choose which to show and which count as busy. We keep that list: each calendar's name and colour, and those two choices.
calendar.events.readonly	Read the events on the calendars they chose to show, for the days open on the app's Calendar: each event's title, start and end, whether it is marked free, and its link. Only that person sees them. Read when the page asks, and never stored.
calendar.events.freebusy	Read when the calendars they marked as busy, and the one booked calls go on, are free or busy, so the studio's booking page offers only free times. This gives times only, not what the events are.
userinfo.email	Show which Google account it is, so a person with more than one can tell them apart.
calendar.events.owned	Only with Allow bookings. When somebody books a call on the studio's booking page, put it in a calendar the host owns, with the name, email address, and any phone number, business name and notes the person booking typed, and invite them, so Google emails them the invitation, with a Google Meet link unless the studio switched that off. We create nothing else in the calendar and never change or delete an event.

For each calendar connection we store an encrypted refresh token, the account's email address and that list of calendars. Disconnecting deletes them and calls Google's revoke endpoint.

Unsocial Studiio's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data to train generalised artificial intelligence models, we do not sell it, and we do not transfer it except as described in this policy.

What we access from Meta

When a studio connects an Instagram professional account and the Facebook Page linked to it, we ask for the following nine permissions and no others.

Permission	What it lets us do
ads_read	Read the spend and results of ad accounts you manage, to show them to you. We never create, change, pause or delete an ad.
business_management	See the Facebook Pages and Instagram accounts your business owns in Meta Business Suite, when we list the ones you can connect. We never change your business settings.
instagram_basic	Read the account's profile and its published posts, so we can show them to you.
instagram_content_publish	Publish a post you have composed, at the moment you press publish.
instagram_manage_comments	Read comments on your posts, post a reply when you press send, and hide or unhide a comment when you press Hide.
pages_manage_engagement	Post a reply to a Page comment when you press send, like or unlike it when you press like, and hide or unhide it when you press Hide.
pages_read_engagement	Read your Page's own posts and how they are doing, such as likes and comment counts.
pages_read_user_content	Read comments other people leave on your Page's posts, so you can see and answer them.
pages_show_list	List the Facebook Pages you manage, so you can choose which one to connect.

The same rules apply as for Google: nothing is published or replied to without a person pressing the button, and disconnecting removes our access. One difference: so the Today page opens quickly, we keep the most recent batch of comments across a studio's clients, with each commenter's name and what they wrote. Each new batch replaces the one before, and the last one is deleted with the account.

So a studio can see who answered what, we record which person at the studio replied to, liked or hid a comment, and when. That record holds the comment's id and the person's name, not the comment itself, and is deleted with the account.

Other services we connect to

Notion. If you connect a Notion workspace, we read and write only the pages and databases you explicitly share with the integration. Notion's permission model means we cannot see anything you have not shared. If your workspace has no page we can build in, we offer to create one page at the top of it. That only happens when you press the button that offers it, and we write only inside the page we made and the databases we create in it.
Stripe. Billing, as described above. And if a studio connects its own Stripe account to invoice its clients, we create and read those invoices in the studio's account, with each client's billing email address.

What we do with it

We use information to run the product for you and for nothing else. Specifically: to show you your content and your accounts, to publish and reply when you tell us to, to produce the reports you asked for, to bill you, to keep the platform secure and find and fix what goes wrong, to answer you when you contact us, and, if you joined the waitlist, to tell you when your plan opens.

We do not sell your information. We do not share it with advertisers. We do not use content from your connected accounts to train generalised artificial intelligence models.

Where it lives, and who else touches it

We use a small number of providers to run the platform. They process information on our instructions only.

Provider	What for
Netlify	Hosting the application, and storing the files you upload and the app's working state. Those are stored in the United States, in Netlify's US East (Ohio) region.
Supabase	The database, and signing in. Each night it also receives a backup copy of the files you upload, the videos we host for your studio, and the app's working state.
Bunny	Storing and playing video
Stripe	Subscription billing and payments
Notion	Where a studio's own content lives, when connected
Google	Signing in with Google; the Business Profile a studio connects, as described above; a person's Google Calendar when they connect it, which also receives the details of a call booked through the booking page; and counting the Google reviews on a client's business listing
Meta	The Instagram and Facebook accounts a studio connects, as described above
AssemblyAI	Turning the speech in a video into text, when you ask for a transcript. It fetches the video to do it, and we delete the transcript there once we have read it back.
Resend	Sending some of our notification emails, and telling us when one bounces for good or is marked as spam
Cloudflare	Its Turnstile check that a person, not a program, is signing up, signing in, setting a password or booking a call
Push services	Delivering the notifications you switch on, through your browser maker's push service (for example Google, Mozilla or Apple)
OpenStreetMap	Finding where a job is on the Operations map, when you add a pin, through the OpenStreetMap Foundation's Nominatim service. It receives the street and suburb typed for the pin, without the house or unit number.
Slack	Posting notices about our own agency's clients to our own team's Slack. No other studio's information goes to it.
Make.com	Running two automations used only for our own agency's clients. They receive a client's short name and, for a search for leads, an industry and a location.
Anthropic	Generating drafts and suggestions when you ask for them; suggesting a name and tags for photos you add to a library, from a small copy of each photo, unless you switch that off; drafting replies to new comments overnight, for clients whose studio switched that on; and sorting new comments into positive, question and flagged when you open the Community page. For sorting, the comment, the name of the person who wrote it and the network it was left on are sent; we keep only the label, against the comment's id, for up to 60 days. Under Anthropic's commercial terms it may not train its models on what we send, and its data processing addendum applies.
Link previews	Fetching the title and picture of a link pasted onto a mood board, from Canva, TikTok, YouTube or Meta. They receive the link.
Domain.com.au	Property market figures for a suburb, on the Operations page. It receives the suburb, state and postcode, nothing about a person.
Wix	Reading website visitor figures for our own agency's clients' Wix sites. No other studio's information goes to it.
Web resources	Some pages load fonts from Google Fonts, scripts from cdnjs and unpkg, and map tiles from CARTO, and some show an Instagram post or a studio's Google booking calendar inside the page. Your browser fetches these straight from them, so they see your IP address and which page asked, and for map tiles, which area the map is showing.

Some of these providers store or process data outside Australia, including in the United States. By using the platform you consent to that transfer. We choose providers that offer contractual protections for personal information.

How long we keep it

We keep your account information and your content for as long as your account is open. When you close your account we keep it for 14 days in case you change your mind, then delete it, along with every connected credential. A few records outlast an account. See Data deletion for which ones, and for exactly how and how long.

We and Stripe keep billing records for the period Australian tax law requires, currently five years. Those records contain the fact and amount of a payment, not the content of your account.

Security

Connection tokens are encrypted at rest. Access to production systems is restricted and protected by multi factor authentication. Traffic to and from the platform is encrypted in transit.

The people who run the platform can see any studio's account. That is how a support question gets answered, and how we find out why something broke.

No system is perfect, and anyone who tells you otherwise is selling something. If we ever suffer a breach that is likely to cause you serious harm, we will notify you and the Office of the Australian Information Commissioner as the Notifiable Data Breaches scheme requires.

Your rights

We handle personal information in line with the Privacy Act 1988 (Cth) and the Australian Privacy Principles. Under the Australian Privacy Principles you can ask us to show you the personal information we hold about you, correct it if it is wrong, or delete it. You can also disconnect any connected account yourself, at any time, from Settings.

Write to support@unsocialstudiio.com and we will respond within 30 days. If you are not happy with how we handle a privacy complaint you can take it to the Office of the Australian Information Commissioner.

Cookies

We use cookies to keep you signed in, and cookies and your browser's own storage to remember your preferences. We do not use advertising cookies and we do not track you across other websites.

Children

The platform is a business tool and is not intended for anyone under 18. We do not knowingly collect information from children.

Changes

If we change this policy we will update the date at the top. If a change materially affects how we handle your information, we will tell you by email before it takes effect.