Platform
RetailPropertyHealthChildcareFranchisingPublic sector
InsightsAPIPricing
Log inSign up
  • Platform
  • Sectors
    • Retail
    • Property
    • Health
    • Childcare
    • Franchising
    • Public sector
  • Insights
  • API
  • Pricing
Log inSign up
Home/Security and data

Security and data

How Censible stores and protects data: where it is hosted, who can access it, and how long each kind is kept. What we collect, and why, is in the privacy policy.

Last updated 22 October 2026

On this page
  1. Where data is hosted
  2. Encryption
  3. Sign-in and API keys
  4. Who can see your data
  5. How long data is kept
  6. Certifications
  7. Breaches
  8. Reporting a security issue

Where data is hosted

  • The Censible app and API run on Fly.io in Sydney.
  • Accounts, saved areas and site sets are stored in Supabase, in its Sydney region.
  • Census figures are stored with Cloudflare. They contain no personal information.
  • This website is hosted by Cloudflare and its text is stored in Sanity. Neither holds personal information.

Encryption

Data travelling between your browser, your code or your AI assistant and Censible is encrypted. Supabase and Fly.io encrypt the data they store.

Sign-in and API keys

  • You sign in with your email address and either a password or a one-time link sent to that address. Passwords are stored by Supabase as one-way hashes, so they can't be read back from the database.
  • API keys are stored as hashes, so a key can't be read back from the database. Each key has its own rate limits.
  • AI assistants you connect are listed on the Use with AI page, where you can remove them.

Who can see your data

  • Your saved areas and sites are visible only to you. Every request is checked against your sign-in.
  • Sites you upload are used only to show you your own analysis. They aren't shown to other people, added to Censible's data or used to train AI models.
  • Access to the production systems at Supabase, Fly.io and Cloudflare is limited to the people who run Censible. Those accounts, and the code repository, require two-factor sign-in.

How long data is kept

  • Your account, saved areas and sites: until you delete them or close your account.
  • Daily usage counts: 35 days.
  • Database backups: taken daily and kept for 7 days.
  • Hosting providers' request logs: for a limited time, under each provider's own policy.

When you close your account, your information is removed from the live database within 7 days, and from backups as they expire 7 days after that. Records the law requires us to keep, such as billing and tax records, are kept for as long as it requires.

Certifications

Censible does not hold SOC 2 or ISO 27001 certification. The providers above publish their own certifications.

Breaches

If we become aware of a breach that is likely to cause you serious harm, we will tell you.

Reporting a security issue

Email the details to the address below. Please give us time to fix an issue before making it public.

Contact

Questions about security, or something to report? hello@censible.com.au

hello@censible.com.au

Products

  • Platform
  • Reports
  • Catchments
  • API
  • MCP server
  • Pricing

Sectors

  • Retail
  • Property
  • Health
  • Childcare
  • Franchising
  • Public sector

Resources

  • Insights
  • Guides
  • Glossary
  • Data and sources
  • Coverage
  • Citing Censible
  • Changelog

Compare

  • vs. QuickStats
  • vs. TableBuilder
  • vs. .id
  • vs. GapMaps
  • vs. REMPLAN
  • vs. AreaSearch

Company

  • About
  • Contact
  • Support
  • Security and data
Censible 2026PrivacyTermsBased on Australian Bureau of Statistics data, CC BY 4.0. Censible is not affiliated with the ABS, and its figures are not official ABS statistics.

Censible is built on the lands of the Wurundjeri Woi-wurrung people of the Kulin Nation, and its servers run on the lands of the Gadigal people of the Eora Nation. We acknowledge the Traditional Custodians of Country throughout Australia and their continuing connection to land, waters and community, and pay our respects to their Elders past and present.