Acceptable Use Policy

1. Permitted use

You may use the Service only:

• to power your own application(s) for the benefit of your direct users;
• within the scope and limits of your subscription plan and Order Form;
• in accordance with the API Documentation published at docs.stream.estate;
• in compliance with all applicable laws and regulations.

2. Prohibited uses

You may not use the Service, and you must not allow any third party to use the Service, to:

2.1 Illegal or harmful activities

• violate any law, regulation or third-party right;
• facilitate fraud, money laundering, illegal solicitation or illegal real-estate practices;
• harass, threaten, defame, intimidate or harm any individual;
• infringe any intellectual property right, privacy right or other legal right.

2.2 Data misuse and re-distribution

• resell, sublicense, lease, rent or publicly redistribute the API content to third parties beyond your direct users;
• extract or re-use, in a permanent or temporary manner, the whole or a qualitatively or quantitatively substantial part of the API content, with a view to building, directly or indirectly, a competing database, directory, index or derivative dataset (in accordance with Articles L. 341-1 et seq. of the French Intellectual Property Code);
• engage in repeated and systematic extraction or re-use of non-substantial parts of the content that would manifestly exceed normal use of the API;
• cache, store or retain content beyond what is strictly necessary for the operation of your application or beyond the retention limits stated in the Documentation.

2.3 Artificial intelligence and model training

Without our prior written consent, you may not:

• use any part of the API content to train, fine-tune or evaluate a machine learning model, an artificial intelligence system or any other predictive system;
• feed the API content to any such model or system where that model or system could reproduce, derive from or compete with our databases;
• use the API content to build, assemble or distribute a dataset intended for machine learning purposes.

For clarity, you may, without our prior consent, submit aggregate statistics that you have computed yourself from the API content (for example market averages, indices or counts) to a third-party artificial intelligence tool, provided that (i) no listing content and no substantial extract of the API content is transmitted, and (ii) the provider of the tool does not use the submitted material to train its models. Transmitting listing content to a third-party model provider is a redistribution prohibited under Section 2.2.

Any written consent we grant under this Section is given on the basis of the use described by the customer, applies to that use only, is non-transferable, and lapses if the described use changes.

2.4 Infrastructure abuse

• circumvent or attempt to circumvent any rate limit, quota, throttling or security mechanism we put in place;
• submit excessive, abnormal or automated traffic patterns that could degrade service for other customers;
• probe, scan or test the vulnerability of the Service without our prior written authorisation;
• attempt to gain unauthorised access to the Service, our infrastructure or another customer's account;
• distribute viruses, malware or any code intended to disrupt, damage or interfere with the Service.

2.5 Reverse engineering

You may not reproduce, modify, decompile, disassemble or reverse engineer the API or any part of the Service, except to the extent expressly permitted by applicable law.

2.6 Credential and identity misuse

• share, disclose or transfer your API keys to any third party;
• use the Service on behalf of, or for the benefit of, a third party that has not been authorised by us;
• misrepresent your identity, role or authority when interacting with the Service or our team.

3. Technical compliance

3.1 Rate limits and quotas

You must respect the rate limits, quotas and request-size limits documented at docs.stream.estate. Sustained breaches may result in throttling, temporary suspension or termination.

3.2 Retry policy

Clients implementing automatic retries must use exponential backoff with jitter. Tight retry loops or fixed-interval retries against failing endpoints are prohibited.

3.3 Identification

You must identify your application via a meaningful User-Agent header so that we can investigate operational issues and notify you of relevant changes.

3.4 API versioning

You must keep your integration on a supported API version. Versions move through the lifecycle stages of production, deprecated, then sunset. Continuing to call an API version after its sunset date is a breach of this AUP.

4. Privacy and personal data

The API is not designed to expose personal data. To the extent the content incidentally contains personal data relating to identifiable natural persons (for example professional contact details of real-estate intermediaries), you must:

• handle such data in compliance with the GDPR and applicable national data protection laws;
• not use it for direct marketing, prospecting or profiling without an appropriate legal basis;
• not attempt to re-identify pseudonymised or aggregated data.

5. Reporting violations

If you become aware of any actual or suspected violation of this AUP, of a security incident, of credential compromise or of any misuse of the Service, please notify us without undue delay at [email protected] (legal and compliance matters) or [email protected] (security matters).

6. Enforcement

We may, at our sole discretion and without prior notice where reasonably necessary, take any of the following actions in response to a breach of this AUP: investigate, request information, throttle traffic, suspend access, revoke API keys, terminate the Agreement or pursue legal remedies. The choice of remedy will depend on the nature and severity of the breach.

7. Updates to this AUP

We may update this AUP from time to time. The updated AUP is published on this page, with the date shown under “Last Updated”. Publication is the reference point for when a change takes effect.

A change that clarifies an existing rule, corrects an error or expands what you are permitted to do takes effect on publication.

A change that materially reduces your rights or imposes a new restriction takes effect thirty (30) days after publication. It is your responsibility to review this page periodically; we are not required to notify you individually of a change.

Continued use of the Service after a change takes effect constitutes acceptance of the updated AUP.

8. Contact

Questions about this AUP should be sent to [email protected].