Privacy Policy — Textonomy

Textonomy (“Textonomy”, “we”, “us”) provides the Textonomy Chrome extension (the “Extension”) to help Bubble developers identify, structure, and manage App Texts and translations inside the Bubble editor.

During the beta period, Textonomy operates optional cloud translation-sync services using infrastructure hosted at https://www.satir-sa.com. This policy explains what data the Extension accesses or processes, how that data is used, and how you can contact us regarding privacy.

Data Controller & Contact

Product: Textonomy
Website: https://www.textonomy.com
Privacy & support: privacy@textonomy.com

Summary (Plain English)

• The Extension reads parts of your Bubble Editor app data locally in your browser.
• Authentication tokens are stored locally using Chrome extension storage.
• Data is sent to our servers only when you explicitly initiate actions.
• No analytics, tracking, or background monitoring is performed.

Information We Collect or Access

A. Data stored locally (on your device)

• Authentication tokens and session metadata stored using chrome.storage.local
• Non-sensitive UI preferences and basic diagnostic state

B. Data read locally from the Bubble Editor

While you are actively using the Bubble editor, the Extension reads in-memory editor data to detect text-bearing elements, build an App Text inventory, and determine the app’s default language. These reads occur locally in your browser.

C. Data written to the Bubble Editor (user-initiated)

The Extension writes changes into your Bubble app only when you explicitly confirm actions such as creating App Text IDs, replacing static text with App Text references, or applying translations. All changes are visible inside the Bubble editor and may be reverted using Bubble’s versioning tools.

D. Data transmitted to cloud services (optional)

When you choose actions such as “Upload texts” or “Fetch translations”, the Extension sends limited data over HTTPS to Textonomy’s translation-sync service, which during beta is hosted at satir-sa.com. This may include:

• Bubble app identifier
• App Text inventory (IDs and optional default-language values)
• Default application language

How We Use Data

Data is used solely to identify translatable strings, create and manage App Text IDs, and synchronize translations between your app and the translation service. We do not use data for advertising, analytics, profiling, or resale.

Storage, Retention & Deletion

Local data remains on your device until you log out or remove the Extension. Server-side data used for translation workflows is retained only as needed to provide the service.

You may request deletion of server-side data associated with your app by contacting privacy@textonomy.com.

Third-Party Services

We may use third-party infrastructure providers (such as cloud hosting) to operate the service. All providers are required to use appropriate security measures and encrypted connections. We do not sell or share your data.

Security

• All server communication uses HTTPS/TLS
• Authentication tokens are stored locally and only sent in authenticated requests
• No background tracking or analytics are performed

What the Extension Does Not Do

• No code injection into live, end-user Bubble applications.
• No access to live end-user data or production databases.
• No background activity, analytics, or tracking outside the Bubble Editor.
• No unattended or hidden changes; all editor modifications occur as part of user-initiated actions within the Extension interface.

Children’s Privacy

The Extension is not intended for use by individuals under the age of 16. We do not knowingly collect data from children.

Your Rights

You may request access to, correction of, or deletion of data associated with your use of the Extension by contacting privacy@textonomy.com.

Changes to This Policy

We may update this policy as the product evolves. Updates will be reflected on this page and the “Last updated” date will change accordingly.

Chrome Web Store Reviewer Notes

• The Extension transmits data only after explicit user action
• All Bubble editor reads occur locally
• Tokens are stored using chrome.storage.local
• Host permissions are limited to Bubble editor domains

Contact

Email: privacy@textonomy.com

Technical Appendix: Use of Bubble App JSON

For transparency, the Textonomy Extension interacts with Bubble’s internal editor data model (app.json) while you are actively using the Bubble Editor. This interaction occurs locally in your browser and is limited to editor-only contexts.

The Extension reads selected portions of the in-memory app.json structure to identify translatable text and App Text metadata. Examples of editor data accessed include:

• Page and element definitions used to enumerate text-capable elements (e.g. text, buttons, inputs).
• Reusable element definitions to include text from shared components.
• Application language settings, including the default language.
• Existing App Text ID mappings and language-specific text values, used to build a translation inventory.

When you explicitly confirm actions in the Extension UI, Textonomy may write changes back into the editor’s app.json structure, including:

• Creation of new App Text IDs.
• Replacement of static text entries with App Text references.
• Insertion or update of language-specific text values.

These read and write operations are performed only in the Bubble Editor, never at runtime, and do not provide Textonomy with access to live application data or end-user information.