MyStreet Privacy Policy
Effective date: 12 September 2026
Policy version: 1.0
1. Who we are
MyStreet is a service for finding publicly available development-application information and receiving updates about selected locations in New South Wales.
MyStreet operates under the trading name Stack Applications, ABN 90 200 899 631 ("MyStreet", "we", "us" or "our").
This policy explains how we handle personal information through our website, apps, alert services and support channels. It also explains how to contact us about access, correction, deletion and privacy complaints.
Privacy contact: Admin@stackstore.org
We handle personal information in accordance with applicable Australian privacy laws. This policy describes our practices; it is not a request for blanket consent to unrelated uses of your information. Where an activity requires your consent, we ask for it separately.
2. Information we collect
What we collect depends on the features you use. You do not need to supply payment details to browse the public map or use a free feature.
Contact and account information. We collect your email address when you request email alerts, verify access, contact support or create an account. We collect your name if you choose to provide it, and a phone number if you choose a feature that needs it, such as SMS. We also process account identifiers and authentication information where accounts are available. A password-free alert subscription still involves storing the information needed to provide it.
Searches and monitored locations. We process addresses or suburbs you search, the resulting coordinates, and the locations, labels, radiuses, filters and delivery preferences you save. A monitored address can be a place you are interested in; we do not treat it as proof that you own or live at that property. The fact that you monitor an address is kept separate from public planning records.
Optional device location. If you choose a feature such as “Use my location” and grant permission, we use the location supplied by your device or browser to centre the map or help select an address. You can instead enter an address manually. MyStreet does not need continuous background location tracking to monitor a saved address. You can withdraw location permission through your device or browser settings.
Alerts and communication preferences. We record the alert areas and channels you request, verification status, consent and preference changes, alert events, and delivery outcomes such as delivery, failure, bounce or unsubscribe. If app notifications are enabled, this can include a device push token and notification-permission status. Any optional engagement tracking must be described in section 5 and the technology schedule below.
Subscription and payment information. If you subscribe, we process the plan, billing status, trial eligibility, transaction or receipt identifiers, renewal dates, and information needed to manage billing and refunds. Our payment provider or app store processes your payment method. MyStreet does not store your full payment-card number or card security code. The provider may supply limited billing information, such as card brand and last four digits.
Technical and service-use information. Our systems and service providers process information such as IP address, browser or device type, operating system, request times, security events, errors and basic service activity. Cookies and similar technologies are explained below. We limit diagnostic data to what is reasonably needed and avoid putting private monitored addresses or message contents into general analytics.
Support information. We collect correspondence and information you choose to send us about a problem, correction request, billing question or complaint. Please do not send identity documents, sensitive personal information or information about another person unless it is necessary and we have explained how to provide it safely.
Referral information. Where a referral program operates, we may record a referral code or campaign identifier and the related signup or purchase so that we can measure a campaign or calculate a referral payment. We do not give referral partners your private monitored addresses or contact list. Optional referral cookies are covered by your privacy choices.
3. How we collect information
We collect information directly when you search, submit a form, save an alert, change a preference, make a purchase or contact us. We also receive information from your device, from the service providers involved in delivering the relevant feature, and from payment or app-store providers about your transaction.
We obtain public planning information from sources such as the NSW Planning Portal and relevant authorities. It can include a development address, application reference, proposal, status, dates, location and other planning fields. We use the fields needed for the planning service rather than creating a directory of applicants' personal contact details.
Public planning information and your private subscription information are different datasets. Looking up a property does not make your name, email address or interest in that property public.
Where you provide another person's contact details, you must have authority to do so. Do not sign someone up to emails or texts without their permission. A future gift or postal service will explain any recipient-information requirements before collecting them.
4. Why we use information
We use information to provide the features you request: resolve an address, show planning applications, calculate proximity, save monitored areas, match new or updated records, and send your selected alerts.
We also use it to verify contact details and secure access; manage subscriptions, payments, cancellations and refunds; answer questions and handle complaints; investigate errors and improve reliability; prevent fraud, spam and misuse; maintain necessary business records; and meet legal obligations.
If you separately opt in to promotional communications, we use the relevant contact details and preferences for that purpose. Requesting development alerts does not automatically enrol you in unrelated advertising or partner mailing lists.
We may use aggregated or appropriately de-identified service statistics to understand product use. We do not treat a hashed email address, a private property coordinate or a reversible identifier as anonymous merely because a name is absent.
We do not sell your personal information to data brokers, advertisers, estate agents or developers, or trade your private monitored-location list as a data product. We do not disclose those lists to developers, estate agents or advertising partners for their own targeting.
5. Cookies, analytics and external map services
Essential cookies or similar local storage may be used for security, authentication, verification, remembering preferences and providing requested functionality. Disabling these can affect the relevant features.
Any optional analytics, advertising, session-replay or referral tracking we use is identified in our current technology schedule. Optional tracking is off until you enable it through Privacy choices, and can be withdrawn there. Refusing optional tracking does not prevent you from using core address search and alert functionality.
We do not send private monitored addresses, precise device coordinates, email addresses, phone numbers or access tokens to advertising platforms as tracking parameters. We do not enable automatic collection of alert-form contents for advertising.
An external map or address-search provider may receive the query or location needed to provide its service, together with technical information such as IP address and device details. Payment, verification and security providers may also process necessary technical information when you use their features. These functional disclosures are separate from optional advertising tracking and are identified in the schedule.
Current providers, technologies, purposes and controls:
This schedule covers the MyStreet website and relevant iOS app services. A provider receives information only when the feature that uses it is available and used.
| Provider or technology | Purpose and information handled | Availability and controls |
|---|---|---|
| Supabase | Stores planning records and provides the shared account database, authentication and saved-location services. Handles account identifiers, email addresses, saved locations, preferences and related security records when those features are used. | Public planning records are separate from private account and monitoring records. |
| OpenAI Sites and Cloudflare | Website publishing, hosting and delivery. Requests may include an IP address, browser information, requested page and information submitted to the website. | Necessary to deliver the hosted website. |
| NSW Spatial Services | Resolves website address searches through its ArcGIS address service. Receives the search text or address identifier and server connection information. | Used for address search; MyStreet does not send subscriber email addresses or private monitored-property lists to this service. |
| OpenStreetMap Foundation | Supplies website map tiles. Receives the requested map area and connection details such as IP address and browser information. | Used when the web map loads. Leaflet displays the map in the browser; it is software, not a separate recipient of the data. |
| Apple Maps / MapKit | Maps, address lookup and map images in the iOS app. Apple receives relevant search terms, visible map area and technical information; device location is used where permission is granted. | Device location permission can be declined; an address can be entered manually. |
| Apple App Store / StoreKit | Processes iOS purchases where offered. Apple handles payment information; MyStreet uses product, transaction, receipt and entitlement information. | Purchasing through Apple is separate from browsing the website. MyStreet does not receive full card details. |
| MyStreet cookies and optional analytics | Essential cookies support sessions, verification and preferences. Optional analytics count named product events in MyStreet's own database. | Optional analytics are off until enabled in Privacy choices. MyStreet's event payload contains the event name, not an email or property address. No third-party advertising pixel or session replay is installed in the website. |
| Cloudflare Turnstile | Abuse prevention on configured verification forms. Processes security challenge results and browser/network signals. | Used only when configured for that form; it is separate from optional analytics. |
| Cloudflare Email Routing | Routes email sent to Admin@stackstore.org to the support inbox. Processes email addressing, routing information and message content for delivery. | Used when you contact support. Your email provider and the destination mailbox service also process the message. |
Email and SMS delivery integrations
The shared notification service integrates with Resend for email and Twilio for SMS. Each provider is used only when its channel is enabled and the recipient has requested that delivery. Resend receives the recipient email address, message content and delivery information. Twilio and participating carriers receive the recipient phone number, message content and delivery information. A property address may appear in an alert you request.
Website accounts use email verification codes without a password. Development alerts are sent only for locations and delivery settings you request. Website paid checkout is not currently open. Listing these integrations does not make a coming-soon feature available. No website payment processor, physical Letters fulfilment provider or third-party advertising service is currently enabled.
6. Who can receive information
We disclose information only as reasonably needed for the purposes in this policy and as permitted by law. Recipients can include:
- Hosting, database, authentication, mapping, geocoding, email, SMS, push-notification, payment, security and support providers that operate the relevant parts of MyStreet.
- Authorised team members, contractors and professional advisers who need access to carry out their work and are subject to appropriate confidentiality or other protective obligations.
- Regulators, courts, emergency services or other parties where disclosure is required or authorised by law, or necessary to address a serious safety or security issue in accordance with law.
- Parties to a genuine business restructure or transfer, only where disclosure is lawful and necessary, with appropriate confidentiality and safeguards. We prefer de-identified information during preliminary due diligence.
A provider receives only the information needed for its role. For example, an email provider processes the recipient address and email content, while a map provider processes a relevant address query or map location. Some providers, including app stores and payment providers, also handle information under their own privacy policies.
We do not notify property owners, applicants or councils that a particular user is monitoring their property as part of our ordinary alert service. This does not prevent a disclosure required by law.
7. Storage and overseas handling
MyStreet uses cloud infrastructure. Selecting an Australian database region does not mean every provider, backup, support function or delivery service operates only in Australia.
The following schedule identifies our current relevant providers, the information they handle, and the countries in which overseas recipients are likely to be located, where practicable. It also distinguishes the primary database location from other processing or support locations.
Provider and overseas-disclosure schedule:
Provider information checked on 12 September 2026. These locations describe the primary database and providers' published processing arrangements; they are not a promise that every request, backup or support operation remains in one country.
| Provider | Storage or processing locations | Privacy information |
|---|---|---|
| Supabase | MyStreet's primary project database is in Sydney, Australia. Supabase describes broader international processing, including the United States and Singapore; its service providers and support may operate outside the database region. | Privacy policy, data processing addendum and subprocessor list. |
| OpenAI Sites | OpenAI describes processing in the United States and other countries where its affiliates and service providers operate. Website delivery also uses Cloudflare. | OpenAI privacy policy. |
| Cloudflare — hosting, security and email routing | Global processing. Cloudflare describes primary storage in the United States and European Economic Area, with access and transfers in other countries where it operates. This is not an Australia-only arrangement. | Cloudflare privacy policy. |
| NSW Spatial Services | NSW Government service in Australia. Its public privacy information does not establish that every infrastructure or support operation is confined to Australia. | Spatial Services privacy information. |
| OpenStreetMap Foundation | Map requests use a global tile-cache network; the serving location varies. The Foundation identifies the United Kingdom and Netherlands for other personal data, with backups in the EU. Those locations are not a residency guarantee for tile requests. | OpenStreetMap Foundation privacy policy. |
| Apple — Maps and App Store services | Apple processes information internationally, including in the United States and through its global affiliates and service providers. The handling depends on the Apple service used. | Apple privacy policy and Apple Maps privacy information. |
| Resend — when email delivery is enabled | Resend identifies the United States as its primary processing location; email delivery also involves the recipient's mail provider. | Resend data processing addendum. |
| Twilio — when SMS delivery is enabled | Twilio identifies primary processing facilities in the United States and international transfers. Delivery also involves telecommunications providers in the recipient's country and along the delivery route. | Twilio privacy notice. |
Optional MyStreet analytics use the Supabase database described above. Support email passes through Cloudflare Email Routing and the destination mailbox service; that mailbox's provider and storage location are separate from the MyStreet database. Provider arrangements may change, and we update this schedule when the services we use change.
Where applicable Australian privacy law requires safeguards for overseas disclosures, we take reasonable steps to put those safeguards in place. We do not rely on your acceptance of this policy as a blanket waiver of protections for overseas handling.
8. Keeping information secure
We take reasonable technical and organisational steps to protect personal information against loss, misuse, interference and unauthorised access, change or disclosure. This includes restricting access according to role, protecting credentials and access links, and maintaining appropriate safeguards for the services we use.
No online service can promise absolute security. Please keep sign-in and management links private, secure your email account, and tell us promptly if you suspect unauthorised access.
If we become aware of a suspected personal-information breach, we investigate and take reasonable steps to contain it and reduce harm. We notify affected people and regulators where required by applicable law.
9. Retention and deletion
We keep personal information only for as long as reasonably needed for the purposes described here, or as required or permitted by law.
Active alert settings are retained while you use the alert service. When you remove an alert or request deletion, we stop the relevant monitoring and remove or de-identify information no longer needed. Stopping email delivery alone does not necessarily delete your account or cancel a paid subscription; those controls are explained separately.
Limited billing, transaction, consent, complaint, security or dispute records may need to remain for legal or legitimate recordkeeping purposes. We minimise that retained information and restrict its use. We may retain a minimal suppression record so that an unsubscribe request remains effective; we do not use that record to market to you.
Copies in backups are protected, kept out of ordinary use, and removed or overwritten under the applicable retention cycle. If a backup is restored, applicable deletion and suppression requests must be reapplied. Retention periods are reviewed rather than treating inactive personal information as something to keep indefinitely.
Deleting your MyStreet account does not delete an independently published government planning record. You may separately ask us to review how we display information about you; section 12 explains how.
10. Your choices and communication preferences
You can browse public planning information without creating a password-based account. Some technical information is still processed to deliver and secure the website. You can decline optional location access and enter an address manually.
You can change monitored locations and delivery choices through the controls provided in MyStreet or a secure management link. You can unsubscribe from emails through their unsubscribe link, without logging in or creating an account. SMS messages provide a supported opt-out method. You can disable push notifications through device settings.
We act on unsubscribe requests as soon as practicable and, for commercial electronic messages, within five working days. Email marketing unsubscribe facilities remain usable for at least 30 days after the message is sent. You do not need to provide additional personal information or pay us to unsubscribe.
Essential communications about a transaction, security incident, requested access link or legal matter may still be sent where appropriate. We do not use this exception to continue promotional messages after you opt out.
Unsubscribing from messages and cancelling a paid subscription are different actions. Billing controls explain how to stop renewal, and we do not conceal that distinction.
11. Access, correction and deletion requests
Contact Admin@stackstore.org to request access to personal information we hold about you, correct it, or ask us to delete information that is no longer needed. These options are also available to password-free alert subscribers.
We may take proportionate steps to confirm your identity and authority before disclosing or changing personal information. We do not require unnecessary identity documents. There is no fee to submit a request. If a lawful, reasonable charge for providing access is proposed, we explain it in advance.
We aim to respond within 30 days. If we need more time, or cannot fulfil some or all of a request, we explain the reason and available complaint options, subject to any lawful limits. Some information may need to remain for the reasons in section 9.
12. Public planning records and concerns about displayed information
If a planning record about you is incorrect or raises a privacy or safety concern, contact Admin@stackstore.org with the application reference and a brief explanation. We will review our own handling of the information and any reasonable correction, restriction or removal request.
Corrections to the authoritative planning record may also need to be made by the council or agency responsible for that record. We cannot change its database, but this does not remove our responsibility to consider our own display and handling of personal information. We do not promise to keep every publicly available personal detail visible simply because it appeared in a source feed.
13. Children
MyStreet is designed primarily for adults interested in property and planning information, not as a service directed to children. A paid subscription must be held by an adult, as explained in the Terms. We do not seek sensitive information about children or require a date of birth simply to browse the map. Contact us if you believe a child has supplied personal information that should not be held.
14. Complaints and changes to this policy
For a privacy complaint, contact Admin@stackstore.org and describe what happened and the outcome you seek. We aim to acknowledge the complaint within seven days and respond substantively within 30 days. We will let you know if more time is reasonably needed.
If you are dissatisfied, you can contact the Office of the Australian Information Commissioner (OAIC) where the matter is within its jurisdiction. Its website explains how to complain and contact the office. For concerns about unsolicited commercial messages, you can also contact the Australian Communications and Media Authority (ACMA).
We may update this policy to reflect changes in our practices or legal requirements. We update its version and effective date and give appropriate notice of significant changes. A policy update does not itself supply consent for a new use that requires your consent.
MyStreetAccount