Privacy Policy for ModelView 3D for Bitbucket

Effective Date: August 3, 2026

This Privacy Policy applies to ModelView 3D for Bitbucket ("ModelView 3D", "the app", "we", "us", or "our"), an Atlassian Forge app for Bitbucket Cloud that lets users preview and review 3D model files directly inside Bitbucket repositories and pull requests.

1. Provider

ModelView 3D is provided by Ugurcan Sari. For privacy, security, or support requests, contact: [email protected].

2. Summary

ModelView 3D is designed so customer model data stays within Atlassian infrastructure and the user's browser.

• The app runs as an Atlassian Forge Custom UI app.
• The app uses Bitbucket read-only APIs to fetch repository files and pull request metadata.
• 3D model files are rendered in the user's browser using Three.js.
• We do not operate a separate model-processing server for this app.
• We do not upload model files, textures, source files, or rendered previews to our own servers.
• We do not sell customer data.
• We do not use model data for advertising, analytics profiling, or AI training.

3. Data the App Can Access

Depending on where the app is used, ModelView 3D may access the following data through Bitbucket Cloud and Atlassian Forge APIs:

• Repository file content for supported 3D file types, currently .glb, .gltf, .obj, and .stl.
• Relative GLTF companion resources from the same repository ref, such as .bin files and texture images.
• Pull request metadata needed to show changed 3D files, such as pull request ID, source branch, destination branch, commit hashes, changed file paths, and file status.
• Basic repository context provided by Bitbucket to the Forge iframe, such as repository identifier, file path, and commit hash.
• Browser/runtime information needed to render the app, such as viewport size and WebGL capability.

The app requests the following Bitbucket scopes:

• read:repository:bitbucket
• read:pullrequest:bitbucket

These scopes are used only to load model files and pull request change information needed for the app's viewing and review features.

4. How the App Uses Data

ModelView 3D uses accessed data to:

• Display supported 3D model files in the Bitbucket repository file viewer.
• Display changed 3D files in a Bitbucket pull request overview panel.
• Load GLTF companion files, such as relative buffers and textures, from the same repository ref.
• Show model metadata in the browser, such as mesh count, triangle count, material count, texture count, animation count, and bounds.
• Show source, split, and slider-style comparison views for pull request review.
• Show clear error messages for unsupported or missing resources.

5. Data Storage and Retention

ModelView 3D does not store customer repository files, model files, textures, source files, rendered images, pull request content, or model metadata on servers controlled by us.

Model data is loaded into browser memory for rendering and is discarded by the browser when the page, iframe, or app session is closed.

Atlassian may process and retain data according to Atlassian's own cloud service terms, Forge platform behavior, and Bitbucket Cloud logs. Atlassian acts independently for its own platform services.

6. Diagnostics and Support

The app includes a "Copy diagnostics" feature on error screens. This feature creates a support report in the user's browser.

Diagnostics may include:

• App name and timestamp.
• Whether the error happened in the repository viewer or pull request panel.
• The operation that failed.
• Error category and error message.
• File path, file extension, and file size when known.
• Workspace, repository, pull request ID, branch/ref information when relevant.
• Browser user agent, language, and viewport size.

Diagnostics do not include:

• Model file bytes.
• Source file contents.
• Texture contents.
• Rendered screenshots.
• Authentication tokens.
• Secrets.

Diagnostics are not automatically sent to us. A user must choose to copy and share diagnostics through a support channel.

7. External Resources and Egress

ModelView 3D is designed not to send model data to external services. The app blocks absolute external GLTF resource URLs by default. Relative GLTF resources are fetched from the same Bitbucket repository ref through Bitbucket APIs.

The app does not use third-party analytics, advertising trackers, AI services, or remote model-processing services.

8. Subprocessors

ModelView 3D is built on Atlassian Forge and runs inside Atlassian Cloud infrastructure and the user's browser. Atlassian is the primary platform provider involved in hosting and delivering the app.

We do not currently use additional subprocessors to store, process, analyze, or render customer model data.

9. Cookies and Tracking

ModelView 3D does not set its own cookies for analytics or advertising. Atlassian products and identity services may use cookies or similar technologies according to Atlassian's own privacy notices and product behavior.

10. Personal Data

ModelView 3D is intended to process repository and pull request data selected by users inside Bitbucket. Repository paths, branch names, commit metadata, pull request metadata, and diagnostics may contain personal data if customers place personal data in those fields.

We do not intentionally collect or store personal data from customer repositories. If a user voluntarily sends diagnostics or support information to us, we use that information only to provide support, troubleshoot issues, improve the app, and comply with legal obligations.

11. Legal Bases

Where applicable data protection law requires a legal basis, we process any personal data shared with us for the following purposes:

• To provide and support the app at the customer's request.
• To respond to support, privacy, or security requests.
• To maintain the security and reliability of the app.
• To comply with legal obligations.

12. Security

ModelView 3D follows a least-privilege approach and requests only read-only Bitbucket scopes required for app functionality.

The app does not store customer model data outside Atlassian and the browser. It does not include backend functions, remotes, or external egress for model processing.

No system can be guaranteed perfectly secure. Customers should avoid storing sensitive personal data in repository file names, branch names, pull request titles, model file paths, or model contents unless they are comfortable processing that data in Bitbucket Cloud and authorized apps installed in their workspace.

13. Data Residency

ModelView 3D does not maintain separate customer data stores controlled by us. Data processed by Atlassian Cloud and Forge is subject to Atlassian's data residency, hosting, and processing terms.

14. Children's Privacy

ModelView 3D is intended for professional software development and 3D asset review workflows. It is not directed to children.

15. User and Customer Rights

Depending on applicable law and location, individuals may have rights to access, correct, delete, restrict, object to, or receive a copy of personal data.

Because ModelView 3D does not store customer repository content or model files on our servers, most repository data requests should be handled in Bitbucket Cloud by the customer's workspace administrator or through Atlassian.

For personal data voluntarily sent to us through support requests or diagnostics, contact us to request access, correction, or deletion.

16. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the effective date and, where required, through Marketplace listing updates or other appropriate notice.

17. Contact

If you have questions about this Privacy Policy, contact: [email protected]