Privacy Policy

Draft for review. These documents are not final. Business details and proposed commitments are still being reviewed.

Draft · effective date: [TBA]

1. Who we are

Aerial Editor is operated by [legal entity or individual TBA], trading as Aerial Editor, ABN [TBA]. Our business address is [TBA]. Contact our privacy team at info@aerialeditor.com.

This policy explains how we handle personal information through aerialeditor.com, the browser editor, desktop software, account services and support. It does not make information in a private photograph public.

2. Information we handle

We may handle your name, email, organisation, account role and preferences; password hashes and login/device records; payment references, invoices, wallet transactions and export usage; property addresses, image metadata including GPS coordinates and camera information; and information you send to support.

If you use a hosted feature, we may also handle the images, masks, prompts, results, templates or skies submitted to that feature. Photos can contain faces, number plates and other personal information. Please only submit material you are authorised to use and avoid unnecessary sensitive information.

Operational records can include IP addresses, browser/device details, request times, errors and security events. We do not receive or store your full payment-card number or security code; our payment processor handles those details.

3. Local editing and optional uploads

Opening a photo for ordinary editing processes it in your browser or desktop environment. Local projects, originals, saved project files and exports remain on storage you control unless you choose a feature that uploads or shares them. Clearing browser data can remove local work, so keep backups.

Optional hosted AI, account libraries and connected delivery services work differently. The relevant image or asset and necessary instructions are sent to our server or service provider. Any feature that sends photo content for cloud AI should identify that processing before you start it. A local removal tool does not require the same cloud upload.

4. How we collect and use information

We collect information directly from you, from your files and use of the service, and from providers handling payments or integrations you connect. We use it to operate accounts, provide editing and requested integrations, manage payments and credits, restore requested results, provide support, prevent abuse and meet legal obligations.

Providing account and transaction details is necessary for those services. Optional uploads and integrations can be declined, although the corresponding features will then be unavailable. We do not sell personal information.

5. Photos and AI processing

Auto Detect on Removal uses a separate SAM 3 item-detection service on Modal. It sends a resized preview to suggest objects, nearby shadows and a small selection buffer. Its processing, credentials, jobs and model storage are separate from grass detection. You can change the suggested red mask before choosing Apply Removals; detection alone does not submit a generative fill.

Auto Detect Grass sends a resized preview of the current photo, including accepted object removals, to our private SAM 3 service on Modal. The service runs the model directly; Aerial Editor does not send this preview to Google or use it for model training. We do not write previews or masks to our model storage volume or application logs. Modal handles job inputs and outputs through its cloud processing infrastructure; completed job outputs can remain retrievable within our private workspace for up to seven days under Modal’s retention rules. The editor makes a grass result available for 15 minutes, and our job-routing records are removed by periodic cleanup. This feature does not modify your original file.

Hosted relighting uses Google Gemini. When requested, the image and lighting instructions are transmitted to Google and the resulting image may be kept in our private hosted storage for retrieval. Waiting requests temporarily store their submitted inputs in private hosted storage so they can survive a server restart. Waiting requests expire after 24 hours. Temporary input copies are scheduled for deletion after processing, cancellation or expiry; interrupted cleanup is retried when the service is available. AI features may be restricted to particular accounts or builds.

We do not use your photos to train our own models or to advertise your work without separate permission. Third-party AI processing is governed by the provider’s applicable terms. Google’s paid Gemini services state that prompts and responses are not used to improve its products; unpaid services have different terms. [Confirm paid-project configuration and processing arrangements before publication.] Provider security, abuse-monitoring and legally required retention may still apply. See Gemini API terms and Google Privacy Policy.

Object removal uses FLUX.2 Klein 4B in our private Modal workspace. The selected photo context and mask are uploaded for processing. Results are colour matched and saved privately for review. Processing continues while you edit other photos; the original file is retained. Modal job results can remain retrievable for up to seven days.

6. Maps and location data

Aerial Editor includes Google Maps features and content. Their use is subject to the Google Maps/Google Earth Additional Terms and Google Privacy Policy. Map requests may disclose an IP address, approximate area, property coordinates or search terms to the map provider.

Other configured location providers may include Geoapify and OpenStreetMap-based services. We use location information to find relevant places and assist pin placement. It is not a surveying service or a guarantee of geographic accuracy.

7. Who receives information

We share only information needed by hosting, storage, payment, AI and mapping providers to perform the requested service; authorised team members where you choose a shared workflow; and integrations you explicitly connect. We may disclose information where required by law or reasonably necessary to protect legal rights and service security.

If the business changes ownership, relevant information may be transferred under protections consistent with this policy and applicable law. Providers’ own policies govern information they collect directly, such as payment details.

8. Overseas processing

Our Render application is hosted in Singapore. Payment, storage and AI providers may process or support data in other countries. The verified country list is [TBA: confirm Supabase, Stripe, Google and any support processors]. We will take reasonable steps required by applicable law to protect information sent overseas; this policy does not ask you to waive those protections.

9. Cookies and browser storage

We use essential session cookies to keep you signed in and local storage for project data and preferences. Our demo video is hosted with the website. The current public website does not use advertising pixels. If optional analytics or advertising tracking is introduced, we will describe it and obtain any required choices or consent before use.

Blocking essential cookies may prevent login; clearing local storage may delete unsaved projects. Marketing messages will use a separate opt-in and an unsubscribe option. Account, security and transaction messages are service communications.

10. Security and retention

We use measures appropriate to the information we handle, including encrypted network connections, account access controls and password hashing. No system is completely secure. Keep credentials private and maintain copies of originals and project files.

We retain information for the period needed to provide services, resolve disputes and meet legal obligations. The proposed schedule is [TBA: active account records; support records; operational logs; AI originals/results; library assets; backups]. Financial records may be retained after account closure where legally required.

Account deletion removes access and initiates removal of account data. Some transaction and security records may need to remain, and backup removal may be delayed. [Complete and verify hosted image-object deletion and backup expiry before approving this clause.] Closing an account does not erase copies saved on your device or with a provider you control.

11. Access, correction and complaints

Contact info@aerialeditor.com to request access, correction or deletion of personal information, or to make a privacy complaint. We may verify your identity and explain any lawful reason a request cannot be met. Our proposed response target is 30 days.

If we cannot resolve your complaint, you may contact the Office of the Australian Information Commissioner where it has jurisdiction, or another relevant regulator. We will assess and notify eligible data breaches as required by applicable law.

12. Changes

We will date revised versions and communicate material changes through the website or account channels. New purposes requiring consent will not be authorised solely by changing this document.

Questions? info@aerialeditor.com