1. Information we collect
| Category | Examples | Why we use it |
|---|---|---|
| Account information | Email address, Firebase user identifier, authentication/session information. | Sign-in, account security, customer support. |
| License information | Plan, license type, status, expiration, enabled features, device limits, activated device identifiers, activation timestamps. | Entitlement enforcement and license administration. |
| Download information | Authentication status, installer version/metadata, secure download authorization events. | Provide licensed software downloads and prevent unauthorized distribution. |
| Engineering request data | Filter specifications, dimensions, solver settings, analysis parameters, and calculated results sent to the hosted calculation service. | Perform the synthesis or analysis requested by the user. |
| Operational data | Service logs, timestamps, request paths, error information, security events, browser or device technical metadata made available by infrastructure. | Reliability, troubleshooting, abuse prevention, and security. |
| Communications | Messages sent to sales or support. | Respond to requests and provide support. |
2. Authentication and passwords
ResoSynth uses Firebase Authentication for account sign-in. The ResoSynth download page sends sign-in credentials to Firebase Authentication and does not intentionally store your plaintext password in ResoSynth application databases. Authentication tokens may be stored temporarily in your browser session or desktop application as needed to maintain a signed-in session.
3. Engineering data and cloud calculation
When you use cloud-backed synthesis or analysis, the engineering inputs required for that operation are transmitted to ResoSynth's hosted calculation service. The current architecture may keep active design data transiently in server memory so related response, tolerance, and analysis operations can reuse the current design. ResoSynth does not intentionally use the licensing database as persistent project-file storage for your filter designs.
Infrastructure and application logs may retain limited technical information associated with requests or errors. Do not submit information that is not needed for the engineering calculation.
4. How we use information
- authenticate users and maintain account sessions;
- verify subscription, perpetual-license, feature, and device entitlements;
- perform requested calculations and generate outputs;
- provide secure installer downloads;
- administer accounts, licenses, and customer support;
- detect abuse, troubleshoot failures, maintain security, and improve reliability;
- comply with legal obligations and protect ResoSynth, users, and third parties.
5. Service providers
ResoSynth uses third-party infrastructure providers to operate the service. The current production architecture uses Google services including Firebase Authentication, Cloud Firestore, Firebase Hosting, Cloud Run, and Cloud Storage. Those providers process information on our behalf subject to their applicable terms, security controls, and privacy practices.
6. Sharing
We do not sell customer engineering-design data to advertisers. We may disclose information to service providers that operate the Services; when required by law or valid legal process; to protect rights, security, and safety; or in connection with a merger, acquisition, financing, reorganization, or sale of relevant business assets, subject to applicable law.
7. Retention
We retain account and license records for as long as reasonably necessary to provide and administer the license, maintain business and security records, resolve disputes, and comply with legal obligations. Operational logs and transient calculation data may have shorter or provider-controlled retention periods. We may retain limited records after account closure when legally or operationally necessary.
8. Security
We use technical and organizational safeguards appropriate to the nature of the Services, including authenticated access, separate service identities, private storage for licensed installers, and short-lived download links. No system can guarantee absolute security.
9. Browser storage
The licensed download workflow may use browser session storage to maintain authentication state during the current browser session. Additional strictly necessary storage may be used as the Services evolve.
10. Children
ResoSynth is a professional engineering product and is not directed to children. We do not knowingly offer ResoSynth accounts for use by children under 18.
11. Your choices and requests
You may contact us to request reasonable access to, correction of, or deletion of account information, subject to authentication, legal retention requirements, security needs, and applicable law. Some license or transaction records may need to be retained even after an account is closed.
12. International use
If you access ResoSynth from outside the United States, information may be processed in the United States or other locations where our service providers operate, subject to applicable law.
13. Changes to this policy
We may update this Privacy Policy as the Services or legal requirements change. The current effective date and version appear above.
14. Contact
Privacy questions may be sent to sales@resosynth.com.