Map what personal data you actually collect and why — the groundwork that makes your privacy policy true rather than template fiction.
Map my data handling for a truthful privacy policy. Business: {{business}}, systems: {{systems}} (website, CRM, email tools, payment, analytics, ads).
Build the map: per system — what personal data goes in (names, emails, payment, behaviour, sensitive categories?), why (the purpose in one honest sentence), where it's stored (and the offshore question: which tools host outside Australia?), who it's shared with (processors, ad platforms — the pixel counts as sharing), and how long it's kept (usually the most embarrassing answer: 'forever, by default'). Then: the gaps between this map and a standard policy template (that's where policies lie), the APP-relevant flags to raise with an advisor (do the Australian Privacy Principles bind us — turnover, data types?), and the 3 cheapest practices to fix before publishing (deletion routine, access tightening, unused-pixel removal).
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekSummarise a contract clause and flag what to watch.
Draft a clear internal policy from a few requirements.
You received a demand letter or legal threat: the don't-panic triage, what to preserve and not say,...
Review a contract before signing: the clauses that bite SMBs — liability, termination, auto-renewal,...
Draft the skeleton terms and conditions for your service — coverage of scope, payment, cancellation,...
Audit what intellectual property your business actually owns — brand, content, code, designs, client...