Privacy Policy
Last updated: 3 October 2026
1. Who we are
ListingRush is operated by OceanEdge AS, a Norwegian company with organisation number 834 944 952. In this policy, "ListingRush", "we", "us", and "our" mean OceanEdge AS.
ListingRush provides web and mobile tools that let real estate professionals capture property photos and guided room capture, upload property material, generate listing visuals, and publish shareable property tours.
Privacy contact: silas@oceanedge.no. If you contact us about privacy, please use the email address connected to your ListingRush account where possible.
2. Scope
This policy applies to the ListingRush website, dashboard, iOS app, APIs, hosted tours, the ListingRush integration for ChatGPT, support communications, and related services. It also explains the information we provide for App Store privacy disclosures.
Customers are responsible for making sure they have a lawful basis to upload property content, including photos or videos that may contain people, personal belongings, addresses, or other identifying details.
3. Personal data we collect
Account and identity data
- Name, email address, profile image, and authentication identifiers.
- Sign-in, sign-up, password, session, and account status information.
- Role, plan, subscription tier, credits, usage limits, and account settings.
Property and user content
- Property photos, floor plans, room photos, guided panorama captures, uploaded footage, video plans, camera settings, and generated outputs.
- Project names, room names, capture structure, virtual tour links, hosted tour content, and publication settings.
- Free-form prompts, instructions, edits, and support messages you submit.
Mobile app device data
- Camera access is used to capture room photos and guided room capture images when you choose to take them.
- Motion sensor data is used during guided 360-degree capture to help align shots. We use it to operate the capture flow and do not use it to infer sensitive characteristics.
- The app stores authentication/session tokens on the device using secure storage so you can stay signed in.
- We do not request precise location, contacts, microphone access, or health data for the current ListingRush iOS app.
Billing and commercial data
- Billing provider customer and transaction IDs, subscription plan and status, purchase and expiry dates, credit purchases, refunds, and invoice or billing portal status. For App Store purchases, RevenueCat links Apple transactions to your ListingRush account so we can provide purchased access and credits.
- We do not store full card numbers. Web payments are processed by Stripe; App Store payments are processed by Apple.
Live demo registrations
- Name, work email, mobile number, brokerage, selected session, and registration status.
- Consent records and delivery status for practical event information sent by email and SMS.
- Registering for a live demo does not subscribe you to general product marketing.
Technical, analytics, and security data
- IP address, device type, browser or app version, operating system, language, pages or screens viewed, events, timestamps, and referring URLs.
- Cookie preferences, session identifiers, logs, diagnostics, error information, and API request metadata.
- Approximate location may be inferred from IP address for security, fraud prevention, localization, and service operation.
- On the website, PostHog replay follows your analytics preference. In the mobile app, replay covers signed-in product screens to help us diagnose usability problems. Ordinary interface text, project and room images, product form entries, plan choices, and navigation can be visible. Passwords, verification codes, payment fields, and marked private account details are protected. Console logs are not recorded. Replay is disabled on authentication, administration, bearer-link, and public-tour pages.
- Published tours use cookieless first-party measurement. A random visit identifier exists only in page memory, while the server derives a project- and day-limited visitor estimate from request data. Raw IP addresses and user-agent strings are discarded rather than written to the analytics database. We retain aggregate-ready room views, active time, completion and share events, coarse source and device categories and, where available, a country code. We do not use this data to recognise buyers across days, devices, tours or websites.
4. How we collect data
- Directly from you when you create an account, upload content, capture photos, publish tours, buy credits, contact us, or use the dashboard or app.
- Automatically through cookies, local storage, device APIs, server logs, and analytics tools.
- From service providers such as Clerk for authentication and Stripe, Apple, and RevenueCat for billing and purchase events.
5. Why we use personal data and our legal basis
- Provide the service: create and manage accounts, authenticate users, process uploads, generate outputs, publish tours, sync projects, and provide customer support. Legal basis: performance of a contract.
- Billing: manage checkout, subscriptions, credit purchases, invoices, refunds, and payment status. Legal basis: performance of a contract and legal obligation.
- Security and abuse prevention: protect accounts, detect misuse, troubleshoot errors, maintain audit logs, and keep the service reliable. Legal basis: legitimate interests and, where required, legal obligation.
- Product improvement: understand how features are used, fix bugs, improve capture quality, and plan product changes. Legal basis: legitimate interests or consent where consent is required for optional analytics cookies.
- Published-tour measurement: provide tour owners with aggregate performance reporting, including views, room reach, engaged time, completion, source, device and share metrics. This measurement does not use cookies, browser storage, advertising identifiers or persistent visitor profiles. Legal basis: our legitimate interests in providing limited aggregate service statistics, subject to data minimisation and an interests-balancing assessment.
- Marketing and communications: send service messages, respond to requests, and, where permitted, send product updates or marketing. Legal basis: legitimate interests or consent, depending on the communication.
- Live demos: manage your registration and send the confirmation, meeting link, reminders, changes, or cancellation information you requested. Legal basis: your consent and steps taken at your request before participation.
- Legal compliance: comply with bookkeeping, tax, consumer, platform, and data protection obligations. Legal basis: legal obligation.
6. AI processing and generated content
ListingRush may process uploaded property content, prompts, and project metadata with AI and media-processing providers to produce floor plans, listing visuals, panoramas, and interactive tours. Depending on the selected workflow and configuration, this may include providers such as OpenAI, Google Gemini, World Labs, and internal processing workers.
Do not upload content you are not authorised to use, and avoid uploading sensitive personal data unless it is necessary for the service and you have a lawful basis. Generated outputs may be inaccurate and should be reviewed before publication.
7. Cookies and privacy choices
We use strictly necessary cookies and similar technologies for sign-in, security, and core functionality. With your consent, we may also use functional, analytics, and marketing cookies. You can manage optional cookie choices at any time on our Cookie preferences page.
Cookie choices are saved on the device or browser where you make the choice. If you clear site data or use another device, you may need to set your preferences again.
8. Who we share data with
We do not sell personal data. We share personal data only where needed to provide, secure, improve, or comply with legal obligations for ListingRush. Our service providers may include:
- Clerk: authentication, account management, sessions, and user identity.
- Stripe: web checkout, subscriptions, invoices, billing portal, tax/payment status, and fraud prevention.
- Apple and RevenueCat: App Store purchase processing and validation, subscription status, restoration, transaction records, and purchased access linked to your account.
- Amazon Web Services: storage, hosting, presigned uploads, and infrastructure.
- MongoDB: application database for account, project, usage, and billing state.
- OpenAI, Google Gemini, and World Labs: AI generation, image processing, and media analysis workflows where used.
- PostHog and Google Analytics where enabled: analytics, product usage, diagnostics, and feature improvement.
- Resend: transactional email delivery.
- Twilio: SMS delivery for practical live demo and service messages where you have consented.
- Sanity: content management and internal administration.
- Pinecone: vector storage/search for supported knowledge or content features where enabled.
- Professional advisers, authorities, or platform providers: where necessary for legal, accounting, tax, compliance, dispute, security, or App Store review purposes.
We require service providers to protect personal data and process it only for agreed purposes. Where personal data is transferred outside the EEA, we use an adequacy decision, Standard Contractual Clauses, or another lawful transfer mechanism where required.
9. Public and shared content
If you publish or share a ListingRush tour, people with access to the link may view the published property content and related tour information. You control what you upload and publish. Remove, unpublish, or edit content if it contains personal data you should not make available.
10. Retention
- Account data is kept while your account is active and for a limited period after closure where needed for legal, security, backup, or dispute purposes.
- Project files, uploaded photos, generated outputs, and hosted tours are kept while your account or project remains active, unless deleted earlier through account or project deletion features.
- When you delete your account, we start deleting account records, projects, uploads, vector namespaces, and related application data, except where we must keep limited information for legal, billing, security, tax, or accounting reasons.
- Norwegian accounting records and invoice-related information may be retained for the period required by Norwegian bookkeeping and tax rules.
- Server logs, diagnostics, and security records are kept only as long as reasonably needed for security, debugging, legal, and operational purposes.
- Live demo registration contact data is normally deleted or anonymised within 90 days after the session, unless a longer period is required for a dispute, legal obligation, or separate consented purpose.
- Pseudonymous published-tour analytics session records are automatically deleted after 395 days. Country totals are withheld from tour owners until at least five viewers are represented.
- Backups may retain deleted data for a limited period before they rotate out of backup storage.
11. Account deletion
You can request account deletion from the iOS app settings or the web dashboard. Account deletion is intended to remove your ListingRush account and associated application data that we are not legally required to keep. If deletion fails or you need help, contact silas@oceanedge.no.
12. Your rights
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a portable copy of your personal data. You may also have the right to withdraw consent where processing is based on consent.
To exercise rights, email silas@oceanedge.no. We may need to verify your identity before responding. We normally respond within one month unless the request is complex or the law allows a longer period.
EEA, UK, and Swiss users may complain to their local supervisory authority. In Norway, the supervisory authority is Datatilsynet.
13. International users and US state privacy rights
ListingRush is operated from Norway and may be used by customers in other countries. If US state privacy laws apply to your use of the service, you may have additional rights, such as the right to know, access, correct, delete, or opt out of certain sharing or targeted advertising. We do not sell personal data for money. You can contact us at silas@oceanedge.no to exercise applicable rights.
14. Children
ListingRush is a professional real estate tool and is not intended for children. We do not knowingly collect personal data from children. Contact us if you believe a child has provided personal data to us.
15. Security
We use technical and organisational measures designed to protect personal data, including access controls, encrypted transport, secure storage practices, provider security controls, and deletion procedures. No online service is completely secure, so please use strong passwords, protect your account, and contact us if you suspect unauthorised access.
16. App Store privacy summary
For App Store Connect, ListingRush may collect data linked to you, including contact information, user ID/account identifiers, user content such as photos and project data, product interaction, usage data, diagnostics, purchase or subscription status, and device or technical identifiers. We use this data to provide app functionality, process uploads, manage accounts, improve the product, provide support, prevent abuse, and meet legal obligations. We do not use the current iOS app to track you across third-party companies' apps or websites for advertising purposes.
17. ListingRush for ChatGPT
Connecting ListingRush to ChatGPT lets ChatGPT request supported actions on your behalf. The integration uses your ListingRush account and project permissions. It requires an active account and your opt-in in ListingRush Settings. The purposes and legal bases in section 5 also apply to these actions.
Information exchanged
- Clerk provides the authenticated account identifier, application identity and authorized access scope used to verify the connection. ListingRush checks account status and your integration setting. A timestamp of successful authenticated tool use lets Settings show when the connection was last verified; turning access off clears that timestamp.
- ListingRush receives the action and arguments ChatGPT sends, such as a project identifier, creative brief, selected file reference, scene edit or soundtrack choice. Selected attachments are copied into your ListingRush project. The integration does not request your entire chat history.
- Responses to ChatGPT can include your display name, accessible workspace names and identifiers, project titles, property notes, media names and identifiers, scene plans, camera settings, soundtrack details, status and links to the ListingRush editor or owned outputs. This information may appear in your conversation.
- When you open the camera editor in ChatGPT, bounded photo previews and available depth or camera geometry are sent to the embedded editor to display the requested scenes. These previews are kept out of the ordinary text response to the model; they are still delivered within the ChatGPT host.
- When you ask ChatGPT to inspect saved photos, the integration sends reduced-size copies of up to five selected whole photos per request to the model, with their project identifiers and photographed dimensions. A full-project review can use several requests. These images can become part of your ChatGPT conversation; they are separate from the private camera-editor previews.
- Opening saved property photos can deliver selected full-resolution files to ChatGPT through its supported attachment capability. Requested exports use private expiring download links for the exact saved versions. ChatGPT performs requested image edits under its own plan and policies. Actual returned edits are saved as candidates and reviewed before selecting them for display; originals and previous versions remain in ListingRush. An explicit upload fallback is available when the host cannot transfer edited files.
- Preparing a video from saved photos copies the exact selected stored versions into a draft in the same property and workspace. It does not itself start generation. Owned virtual-tour analytics responses include collected aggregate counts, engagement measures and privacy-filtered breakdowns; individual visitor and session records are not returned.
- When you ask ChatGPT to inspect saved footage, the integration can send up to four sampled image frames and their timestamps to the model. Completed video playback is delivered to the embedded component through short-lived private links. Playback and generation-approval capabilities are kept out of model-facing responses.
- Soundtrack choices and saved excerpt times can be returned to the model for each video format. Listening uses short-lived private audio links in the embedded component; those links are kept out of model-facing responses. Audio-preview capabilities expire after five minutes and their records are scheduled for deletion at expiry.
- Photo classification and planning can send selected property content and instructions to the AI providers used for those features. Storage, authentication and processing use the service providers described in sections 6 and 8. Where video generation is enabled, processing also includes the approved scene instructions and reference material needed for that workflow.
OAuth credentials and storage credentials are used to authorize requests, not returned as project content. We process request metadata and error information for operation, security and support as described above. OpenAI separately processes your use of ChatGPT under its own policies and your ChatGPT account settings.
Saved work, retention and your controls
Imported media, saved briefs, scene plans and camera or music edits become part of your ListingRush project and follow the retention criteria in section 10. Disconnecting does not erase that work. Queued ChatGPT operation records are scheduled to expire after 24 hours; this does not delete the saved project or its outputs. Playback capabilities expire after five minutes, and hashed approval-capability records are scheduled for removal after seven days. Accepted generation receipts remain with the saved job for retry safety. Deletion of project files uses background cleanup and can take additional time if a storage operation must be retried. Logs, backups and records retained for legal purposes follow section 10.
Disable ChatGPT in ListingRush Settings → Integrations to block subsequent integration actions, or remove the connection in ChatGPT. Use ListingRush project or account controls to request deletion, or contact silas@oceanedge.no. ListingRush cannot delete the copy of information in your ChatGPT conversation; use OpenAI's controls for that history. See the integration support guide for connection, access and deletion help.
18. Changes to this policy
We may update this policy when ListingRush, our providers, or legal requirements change. The "Last updated" date shows when this policy was last revised. For material changes, we will provide notice where required by law.