Privacy Policy
Creable Pty Ltd ("we," "us," or "our"), the company that operates Creable, values the privacy of individuals who use our creator analytics platform at creable.app (the "Service"). This Privacy Policy explains how we collect, use, and share information from or about users of our Service. By using the Service, you agree to the collection, use, disclosure, and procedures this Privacy Policy describes. Beyond this Privacy Policy, your use of the Service is also subject to our Terms of Service.
1. Information We Collect
Account Information
When you create an account, we collect your email address and name. This is used to identify your account and communicate with you about the Service. During onboarding we also ask for your date of birth. It is optional — you can leave it blank and still use Creable. We ask because the Service is for adults only (section 10); where you give it, we store it on your profile alongside your email, with the same protection. To correct or remove it, email us (section 8).
Platform Data via OAuth
When you connect your social media accounts (YouTube, TikTok, or Instagram), we access the following data through each platform's official API with your explicit authorization:
- Public profile information (username, profile picture, bio)
- Video and post metadata (titles, descriptions, publish dates, thumbnails)
- Analytics and performance metrics (views, likes, shares, engagement rates)
- Comments on your content
- Captions or transcripts of your videos, where the platform makes them available
- OAuth access and refresh tokens needed to keep the connection working
We only access data that you explicitly authorize through each platform's OAuth consent flow. You can revoke access at any time through the platform's own settings, or by emailing us to revoke and delete the access tokens we hold.
Transcripts and Your Tone Profile
To describe how you write and speak, we obtain a transcript of your videos — either the captions the platform already holds, or by sending the video to the transcription service named in section 5, which reads the speech out of it. From those transcripts we derive a tone profile: a stored description of your voice, structure and recurring themes, used to make drafts and suggestions sound like you rather than like a generic assistant.
Information About Your Audience
Because we analyse the comments on your content, we necessarily hold information about the people who leave them. For each commenter we keep the platform's own account identifier, their public display name and avatar, the comments they left on your content, and counts of how often and how recently they engaged. We use this to show you who engages with your content and what they are saying, and to produce the sentiment and audience-theme summaries the app builds from those comments.
We do not contact these people, build profiles of them for any purpose other than the above, or disclose this information to anyone but you — other than to the providers in section 5 that run the Service for us. Two of those uses are worth stating plainly:
- Sentiment and audience themes. The text of the comments is sent to our AI providers to be summarised. Their authors' names are not: the summaries are built from what was said, not who said it.
- Drafting a reply. When you ask us to draft a reply, we send the comment you are replying to, the earlier messages in that thread, and the display names of the people in it, so the draft can address them and read as a conversation rather than a non-sequitur. You review every draft before anything is published.
Those providers act on our instructions and may not use the data for anything else.
If you are a commenter rather than a Creable customer and you want to know what we hold about you, or want it removed, write to privacy@creable.app.
Ideas, Sessions and Uploads
When you use our planning and brainstorming features we store the conversation — your prompts, our responses, the decisions you record, and any file you upload into a session — so the work is there when you come back and so later sessions can build on earlier ones. Uploaded images and PDFs are also sent to the AI providers in section 5, so the assistant can read what you have shown it.
Clients, Campaigns and Invoices
If you use Creable to manage brand deals, we store what you enter about your clients (company or contact name, address, email, phone, and tax registration numbers), the campaigns attached to them, the invoices you raise or import, and your own invoicing details, including bank account details where you provide them so they can print on an invoice.
Much of this is information about other people and businesses rather than about you. You are responsible for having a proper basis to put it into Creable; we process it only to provide the invoicing features to you.
Billing Information
Payments are processed by Stripe. We do not receive or store your full card number. We keep the record of your subscription — plan, status, renewal date, and an identifier that links your account to your Stripe customer record.
The Public Preview (No Account Needed)
Our website offers a preview that profiles a YouTube channel, or an Instagram or TikTok account, without anyone signing in. If you use it, we take the handle you type in, fetch that account's recent public videos — titles or captions, thumbnails, public view and like counts, and transcripts — and run them through the AI providers in section 5 to produce a sample tone profile and a draft script. We also collect your email address to send you a link to the result and marketing emails, as disclosed beside the submit button and described below. Once we accept your submission, we add your email address to Loops for marketing emails, even if the analysis or result email later fails.
The handle you type does not have to be your own, so this may involve a channel belonging to someone else. Only public content is used — nothing that needs anyone's authorisation — and the result describes their publicly posted videos. If a channel of yours has been profiled this way and you want the run removed, write to privacy@creable.app.
A preview run is not an account and is not joined to one. The whole run — the channel, the result, and the email address if you gave one — is deleted after 30 days, automatically. We keep your email address and marketing consent record separately for follow-up emails, as described below. Preview pages carry no analytics and are not indexed by search engines.
Following an Account by Its Handle
Where this option is available on your account, you can give us an account's public handle instead of connecting it. We then read that account's public data on a recurring basis for as long as your trial or plan covers it: about every 12 hours we fetch its profile and its recent public posts, meaning titles or captions, thumbnails, length, follower count, and public view, like, comment, share and save counts where the platform shows them. We import up to the 30 most recent posts per platform and new posts as they appear, transcribe the audio of videos up to 30 minutes long, and run them through the AI providers in section 5, so the studio can work from them. We read Instagram and TikTok through ScrapeCreators and YouTube through its public API. We hold no access token for the account, cannot see its private analytics or post to it, and do not store its comments.
The handle does not have to be your own, and we do not check that it is. So this data may be about someone else's account, kept under your Creable account on the timelines in section 7. It is only what that account publishes. If an account of yours is being followed this way and you want it removed, write to privacy@creable.app.
If you later connect an account on that platform, the connection replaces the handle. Where it is the same account, we keep what we already made from those posts and add the data the connection gives us. Where it is a different account, the posts we read from the handle are deleted.
The Free YouTube Comment Analyzer
Our website offers a comment analyzer that reads one public YouTube video, or a public channel's recent videos, without anyone signing in. If you use it, we take the video or channel link you paste, fetch the video's title and description (for a channel: its name and picture, and the titles of its recent videos, or the title and description when only one of them has comments to read) and up to 150 of the top public comments from YouTube, and run them through the AI providers in section 5 to group them into themes, questions, video ideas and sentiment. The report quotes some of those comments word for word; it never shows who wrote them, and we do not store commenters' names. We record the IP address you used only as a one-way hash, to limit how many free reports one visitor can run in a day. For a channel, the report also describes how the channel sounds: we run the same voice read as the voice preview above on its recent videos, and keep the result with the report.
The video or channel does not have to be your own. The report and the comments it quotes are deleted after 30 days, automatically, and the report page loads no third-party analytics tags and is not indexed by search engines. The report link alone shows a limited preview. To receive the full report, enter your email address: we collect your email address and send you one email with the report attached as a PDF and a secure link to open it. The link grants access only to that report, until it expires; anyone you share it with can read it. We keep its access credential in your browser’s session storage so refreshing the page works, and remove it from the address bar. The PDF is yours to keep; our copy of the report is still deleted after 30 days. After you open the secure link, "Save as PDF" builds the same file when you click it; we do not store it. By providing your email on the comment-report or voice-preview form, you agree to receive marketing emails from Creable, as disclosed beside the submit button. We record the wording and time of your consent and add your email address to Loops when we accept your submission. We send you marketing emails: tips, offers and ideas personalised to what you analysed. For a comment report that includes up to three video ideas drawn from the report, each with a short script our AI providers (section 5) write for it, in the channel's voice when we could read it. We use Loops to deliver those emails and manage unsubscribes. We share your email address, the tool you used, a public channel label when relevant, those ideas and scripts, and whether you have signed up; we do not share report access credentials, the comments a report quotes, or creator OAuth tokens. Each follow-up has an unsubscribe link. Unsubscribing stops future marketing emails. We retain your consent and suppression records so we can respect that choice. You can ask us to delete your details at privacy@creable.app.
If you accept website analytics, we keep a random analyzer visitor identifier in your browser for up to 30 days. We use it to count analyzer visits and successful report emails. If you follow a signup link in that browser and also allow analytics in your Creable account, we can connect those counts to a completed signup and trial activation. This measurement contains no email address, report content, report link or access credential. Declining analytics does not affect your report or its delivery. You can change website consent through Cookie preferences and account consent in Settings; our measurement logs are retained for one month.
Free Guides
Our website offers free guides (PDFs) that we email to you. If you ask for one, we collect your first name and email address, which guide you asked for, which post or link sent you to it, and whether you opened the download link in our email. We use your email address to send you the guide. By providing your email, you also agree to receive marketing emails from Creable, as disclosed beside the submit button. We record the wording and time of your consent and add you to Loops when we accept your submission, even if guide delivery later fails. We share your first name, email address, which tool you used, and whether you have signed up. Guide-specific follow-up sequences start after successful delivery when a sequence is available for that guide. Every marketing email lets you unsubscribe, and you can also ask us to stop or to delete your details at any time by writing to privacy@creable.app.
Asking for a guide does not create an account. We keep your details until you unsubscribe or ask us to delete them.
Usage Data
We collect basic information about how you interact with the Service, such as pages visited, features used, and the dates and times of your visits. This helps us understand how the Service is used and improve it.
Cookies and Analytics
On our public website (creable.app) we use Google Analytics 4, a service provided by Google LLC, to understand how visitors find and use the site. Google Analytics sets cookies and collects information such as pages viewed, approximate location (with IP addresses anonymized), and basic device and browser details.
Analytics cookies are off by default. We load Google Analytics with Google Consent Mode, and no analytics cookie is set or measurement data sent until you accept via our cookie banner. You can decline at any time, and you can change your choice later using the "Cookie preferences" link in the site footer. We do not use these cookies for advertising. For more information, see Google's Privacy Policy.
Inside the app itself, we use Google Analytics 4 and PostHog, a product-analytics service provided by PostHog Inc., to understand which features are used and where people get stuck. These record the pages you open and the actions you take in the app — including whether you scroll to the bottom of a page and whether you play a video embedded in it — and associate them with your account. You choose whether to allow them when you set up your account: the analytics box on the set-up screen is ticked, and you can untick it before continuing. Neither loads unless analytics is on. You can change it at any time with "Allow analytics cookies to help improve Creable" under Settings → Privacy & analytics. Turning it off stops both, taking full effect on your next visit — neither can be unloaded from a page that is already open. We do not record your screen, the contents of what you type, or the text displayed on the page; and before any event is sent we strip out the parts of the page address that would identify a commenter, a client or a piece of your content. So these two providers see which screens you opened and what you did there, not who or what was on them. See PostHog's Privacy Policy.
2. How We Use Your Information
We use the information we collect to:
- Provide, maintain, improve, and enhance our Service
- Provide analytics dashboards showing your content performance across platforms
- Automatically group related content, such as the same video posted on several platforms, into collections
- Generate AI-powered insights about your content performance, audience sentiment, and trends
- Draft replies to comments for you to review, and draft and plan content in your own voice
- Understand and analyze how you use our Service and develop new features and functionality
- Communicate with you, provide updates, respond to inquiries, and provide customer support
- Find and prevent fraud, and respond to trust and safety issues
- Comply with applicable laws, regulations, or legal processes
3. Instagram Data Usage
We access Instagram data through the Instagram Graph API, provided by Meta Platforms, Inc. Specifically, we access:
- Your Instagram Business or Creator account profile information
- Media metadata (captions, timestamps, media type, permalink)
- Media insights and analytics (impressions, reach, engagement)
- Comments on your media
We do not access your followers' personal data, private or direct messages, data from accounts you do not own, or any data beyond what you explicitly authorize through the Instagram OAuth consent screen.
Instagram data is used solely to provide you with analytics, collection grouping, and AI-generated insights about your own content. We do not use Instagram data for advertising, selling to third parties, or any purpose unrelated to providing the Service to you.
4. Google and YouTube Data Usage
When you connect a YouTube account, Creable uses Google's official APIs to access only the YouTube data needed to provide the Service to you. This may include your YouTube channel identifier, video metadata, video performance analytics, comments on your videos, and available caption or transcript data for your videos. We also store OAuth access and refresh tokens so we can refresh your connection and continue providing the Service until you revoke access or request deletion.
We use YouTube data to provide user-facing Creable features such as dashboards, per-video analytics, audience comment insights, collection grouping, transcript and tone insights, and creator recommendations. We do not use YouTube data to publish videos, edit your channel, or take public action on your behalf.
We do not sell Google user data. We do not use Google user data for advertising, transfer it to data brokers, or use it to determine creditworthiness. We do not use or transfer Google user data to train generalized artificial intelligence or machine learning models. Where AI service providers process YouTube-derived data for Creable, that processing is limited to generating the user-facing analytics and creative-assistant features you request in the Service.
Creable's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy , including the Limited Use requirements.
5. How We Share Your Information
We do not sell your data. We do not share your data with advertisers or data brokers.
We may share information in the following circumstances:
- Vendors and service providers: We share information with the companies that run parts of the Service for us. They act on our instructions, may use the data only to provide their service to us, and are named in full below.
- As required by law: We may access, preserve, and disclose your information if we believe doing so is required or appropriate to comply with law enforcement requests and legal process, or to protect your, our, or others' rights, property, or safety.
- Business transfers: We may disclose and transfer your information in connection with the consideration, negotiation, or completion of a corporate transaction in which we are acquired by or merged with another company, or we sell or transfer all or a portion of our business or assets.
- With your consent: We may also share information with your permission.
The companies that process data for us
These are the companies that store or process your content and your account information to run the Service. If we add one, we will update this page.
- Amazon Web Services — hosting, databases, file storage, sign-in, and the email we send you (Amazon SES). This is where the Service runs, so it holds everything described in section 1.
- Amazon Bedrock (also AWS), Baseten and Fireworks AI — the AI providers. Between them they do all of the analysis and generation in the Service. Bedrock and Baseten run on US infrastructure; Fireworks AI is the backup for Baseten, serving the same models when Baseten is busy or unavailable, and may process a request in a data centre outside the United States. They receive the content being worked on: video metadata, comment text, transcripts, your tone profile, the invoices and client details you enter, and your planning and brainstorming prompts — including any image or PDF you attach to a session, which is sent to them to be read. When you ask for a draft reply, that also includes the earlier messages in the comment thread and the display names of the people in it (section 1). We normally use Baseten for analysis and generation, and Amazon Bedrock for similarity embeddings and when the other two cannot answer. Routing may change as models improve. All three are bound by the same terms: they process your content to produce the output you asked for, and nothing else.
- ElevenLabs — transcribes the speech in your videos. It receives the whole video file, picture as well as sound: the transcription service reads the audio out of it directly, so we do not separate the two before sending.
- Supadata — retrieves transcripts that already exist for a YouTube video, for the public preview and for accounts followed by their handle, both described in section 1. It receives the video's public identifier.
- ScrapeCreators — reads a public Instagram or TikTok account for the same preview, and repeatedly for an account followed by its handle: its profile and recent public posts. It receives the handle you typed.
- Tavily — performs the web searches the planning assistant runs when researching a topic. It receives the search query derived from your session.
- Stripe — takes payments and manages subscriptions. It receives your email, your payment details (which you give to Stripe directly) and your subscription record.
- PostHog — product analytics inside the app, and only if you have turned analytics on. It receives your account identifier, your email, and which screens you opened and what you did there — never the text on the screen, and with the identifying parts of the page address removed before the event is sent.
- Google (Analytics 4) — website analytics, and in-app analytics if you have turned them on. It receives pages viewed, whether you scroll to the bottom of a page, whether you play an embedded video, approximate location, and device and browser details; in the app it also receives your account identifier, so the activity is tied to your account rather than being anonymous.
- Discord — our team's internal notifications. When you create an account, or a signup is turned away, it receives your email address, and your account identifier once the account exists. When you ask for a free guide, it receives your email address, the guide, and the post or link that sent you. When someone runs the comment analyzer, it receives the video or channel link and how the run went; when you ask for a report by email, it receives your email address.
We do not use your data, or data about your audience, to train generalized artificial intelligence or machine learning models. We engage the AI providers above to produce the specific output you asked for and for nothing else, and we have not authorised any of them to use what we send to train their own models. Amazon Bedrock, Baseten and Fireworks AI are all contractually barred from training on it, and none of them keeps a copy of what we send or what it returns once the request is answered.
6. Security
We make reasonable efforts to protect your information by using physical and electronic safeguards designed to improve the security of the information we maintain. However, as our Service is hosted electronically, we can make no guarantees as to the security or privacy of your information.
7. Data Retention
We retain your information for as long as your account is active or as needed to provide you with the Service. When you request deletion, we take measures to delete your information or keep it in a form that does not permit identifying you when this information is no longer necessary for the purposes for which we process it, unless we are required by law to keep this information for a longer period.
Two different events start a deletion clock, on different timings. They are set out separately below because which one applies to you depends on what happened.
If you disconnect a platform. You can disconnect any connected platform yourself at any time from the Connect page in the app. Disconnecting immediately deletes the access tokens we hold for that platform and stops all data collection from it; the analytics and insights we previously collected from that platform are hidden immediately and permanently deleted within 7 days. If you reconnect the same platform within those 7 days, your data is restored instead of deleted.
If you remove a handle you followed. Removing it stops all reads of that account at once. What we collected from it is hidden immediately and permanently deleted within 7 days, or restored if you add the same handle again within those 7 days. If your trial or plan ends, reads stop and the timeline below applies.
If your free trial expires without you choosing a plan. A longer window applies, because you have not chosen to remove anything — we have simply stopped. When the trial ends we stop processing your data, and everything already imported is kept and recoverable for 30 days. If you have not started a plan by then, we email you a deletion notice giving the exact date your data will be deleted, in your own time zone. Deletion happens 14 days after that notice — 44 days from the day your trial expired — and we send a second reminder 7 days beforehand. Starting a plan at any point before the deletion date keeps your data and everything we had built from it.
After a trial, we keep a record that the trial was used. Free trials are one per connected platform account, so once a trial has run we retain a minimal record of it: a salted, one-way hash of the platform account's identifier, the date the trial started, and how it ended. We store the hash rather than the identifier itself, but it is still information about you: comparing it against a channel connecting now is exactly how we tell that the channel has already had a trial, and that is the record's only purpose. It holds no handle, no profile, no content, no metrics and no access tokens. We delete it 12 months after the trial ends, after which that channel can start a fresh one. It is kept even where the imported data has been deleted under the timeline above, and deleting your account does not remove it — it is the only thing that makes the one-trial-per-channel rule work. If you believe your channel is recorded in error — for example because it changed hands — email privacy@creable.app and a person will review it.
If a trial is refused, we log the attempt for 90 days. When someone tries to start a trial on a channel that has already had one, we record that it happened: the same one-way hash of the channel described above, a one-way hash of the account that tried, the time, and the reason it was refused. No handle, no content, no metrics. It exists so we can tell a genuine case — a channel that changed hands, or someone retrying their own failed connection — apart from one account being attempted from many identities. Like the record above it is held outside your account and deleting your account does not remove it; it is deleted after 90 days either way.
We keep a record of what the AI features cost us, for 180 days. Each time a feature calls an AI model we record your account identifier, the date, which model ran, and the size and cost of the request. It holds none of the content of the request. We use it to understand what the Service costs to run and to enforce fair-use limits. These rows are deleted 180 days after they are written, and a deletion request does not remove them ahead of that schedule. Section 8 summarises the records that outlive a deletion request; the backup window described below applies on top of it.
We keep three dates about your first weeks, for as long as you have an account. We record the first time you open your dashboard with results, the first time you open a Weekly Replay, and the first time you come back during the second week after your first import. We use them, counted across accounts, to understand whether new accounts get value from Creable. They stay in our own database, are not sent to Google, PostHog or anyone else, and are kept whatever your analytics setting is, because that setting controls those two providers. They are deleted when your account is.
Backups lag deletion by up to 35 days. Our databases are backed up continuously so we can recover from a failure. When something is deleted it is removed from the live Service immediately, but it may remain inside a backup snapshot for up to 35 days before that snapshot rolls off. We do not read backups except to recover from an incident, and we do not restore data a creator has asked us to delete.
To delete your entire account and all associated data, use Delete account in the app's Settings, or email us at privacy@creable.app. Unless you are on a paid plan (below), deleting from Settings takes effect at once: we delete the access tokens we hold for your connected platforms — and revoke our access at the platform itself where it offers a way to (Google and TikTok do; Instagram does not, so there you can also remove Creable in its own settings) — stop processing your account and disable sign-in. The rest of your data is then erased within 30 days, and an emailed request is actioned within the same 30 days once verified. Deletion removes your stored analytics and generated insights along with those tokens. The records it does not remove are listed in section 8; each expires on its own schedule. You can also revoke our access at any time directly in each platform's own settings (for example, your Google, Meta, or TikTok account security settings); revoking there stops our access, but to have the already-collected data deleted, use the in-app disconnect or email us.
Deleting your account cancels a paid subscription, and it does not renew. The unused part of the current period is not refunded, as with any cancellation under our Terms — so you keep full access until the end of the period you have already paid for. On that date your access is revoked and disabled as above, and the 30 days to erase the rest run from then. If a payment is overdue when you delete, the subscription is cancelled straight away instead, since there is no paid-for period left to keep.
The record of what you paid stays with Stripe. Deletion removes our own billing rows — your plan, your subscription status, and the identifier linking you to Stripe — along with everything else. But the transaction itself (who paid, when, how much, and the invoice) is a financial record we are required to keep for tax and accounting purposes, and it lives in Stripe's systems rather than ours. It stays there for as long as that obligation runs, typically five years. It is kept for that purpose and no other: it is not used to contact you, and it plays no part in the Service once your account is gone.
8. Your Rights and Choices
You have the following rights regarding your data:
- Access: Request a copy of the personal data we hold about you. Email us and we will provide it within 30 days.
- Deletion: Request deletion of your account and all associated data, by email; we action verified requests within 30 days. Four records described in section 7 are not removed by it and expire on their own schedules instead: the trial-eligibility record (12 months after the trial), the log of refused trial attempts (90 days), the AI cost record (180 days) and, if you have paid us, the record of that transaction, which is held by Stripe rather than by us and kept for tax and accounting (typically five years). The first two are deliberately kept outside your account, because a deletion that erased them would turn "delete and sign up again" into an unlimited free trial. Separately, anything deleted can remain inside a backup snapshot for up to 35 days, as section 7 explains.
- Disconnect: Disconnect any connected platform in the app at any time — this deletes its access tokens immediately and its collected data within 7 days. You can also revoke our access through that platform's own settings, or email us.
- Portability: Request an export of your data in a machine-readable format. This is handled by us on request rather than being a button in the app; we provide it within 30 days. The export covers everything in section 1 except the OAuth tokens for your connected platforms — those are live credentials on someone else's platform, so we revoke and delete them rather than hand them over.
- Correction: Request correction of inaccurate personal data.
- Withdraw consent: You may withdraw any consent you previously provided to us regarding the processing of your information at any time. We will apply your preferences going forward, and this will not affect the lawfulness of the processing before you withdrew your consent.
To exercise any of these rights, contact us at privacy@creable.app. Before fulfilling your request, we may ask you to provide reasonable information to verify your identity.
9. Third-Party Services
Our Service may contain links to other websites, products, or services that we do not own or operate. We are not responsible for the privacy practices of these third-party services. This Privacy Policy does not apply to your activities on these third-party services or any information you disclose to them. We encourage you to read the privacy policies of any third-party services you visit.
10. Minors
Creable is for adults. You must be at least 18 to create an account — see section 2 of our Terms of Service — no part of the Service is directed to children, and we do not knowingly collect, maintain or use personal information from anyone under 18. If you learn that a minor has provided us with personal information, alert us at privacy@creable.app and we will delete it.
11. International Data Transfers
Creable Pty Ltd operates the Service from Australia, and the Service runs on infrastructure in the United States. Every provider listed in section 5 processes data in the United States, except Fireworks AI: when it stands in for Baseten (section 5), a request may be processed in another country where Fireworks AI or its sub-processors operate. So wherever you are, using Creable means your information is stored and processed in the US and is accessible to us in Australia. This is not occasional or incidental — it is how the Service works, every time you use it.
If you are in the European Economic Area or the United Kingdom, neither the United States nor Australia is covered by a general adequacy decision. We rely on the Standard Contractual Clauses approved by the European Commission — and, for UK transfers, the UK Addendum to them — which are incorporated into the data processing terms we are on with each provider in section 5, and which apply equally to our own access from Australia. You can ask us for details of the safeguards in place by writing to privacy@creable.app.
We do not rely on your consent as the basis for these transfers. Consent is meant for occasional transfers, and withdrawing it could not stop processing that the Service cannot run without — so treating it as the mechanism here would misdescribe what is actually happening. If you do not want your data processed in the United States, the remedy is to stop using the Service and ask us to delete your data, as described in sections 7 and 8.
12. Changes to This Policy
We will post any adjustments to this Privacy Policy on this page, and the revised version will be effective when it is posted. If we materially change the ways in which we use or share information previously collected from you through our Service, we will attempt to notify you through our Service or by email.
13. Contact Us
Creable Pty Ltd, operating from Australia, is responsible for processing your information. If you have any questions, comments, or concerns about our processing activities — or want to exercise any of the rights in section 8 — please contact us at:
- Email: privacy@creable.app