Privacy Policy

To provide the prototyping features, the extension may read and modify webpage elements in the active browser page while RWP is running. This can include text, images, media URLs, styles, layout information and other page elements you choose to work with.

RWP also stores certain information locally in Chrome so the extension can operate between sessions. Depending on the feature used, this can include:

• RWP settings and interface state.
• Project names and information used to manage saved prototype files.
• License-validation cache and device information.
• Per-tab prototype-mode state.

Saved prototypes and local assets are written to your computer through Chrome's Downloads capability. They are not uploaded to RWP simply because you save them.

RWP uses a licensing service at license.rapidwebprototype.com to validate trials and paid licenses.

Licensing requests can include:

• A randomly generated installation identifier.
• Your license key when you activate a license.
• A device name you provide or that RWP generates for identification.
• The RWP application version.
• License status, activation information and device-slot information needed to manage the license.

This information is used to validate access, manage device activations, provide an offline grace period and prevent unauthorized license use.

RWP uses Stripe for subscription billing and hosted subscription management. When you choose Manage Subscription, RWP opens Stripe's secure customer portal in a new browser tab.

RWP does not collect or store your full payment-card number through the extension. Payment information entered into Stripe's hosted pages is handled by Stripe under Stripe's own privacy and security practices.

RWP's billing service may use your installation identifier and application version to create the appropriate Stripe customer-portal session for your subscription.

RWP requests Chrome permissions that are necessary for its core prototyping workflow:

• Storage — stores RWP settings, project information and licensing state in Chrome.
• Scripting — allows RWP to operate its editing interface on webpages.
• Downloads — saves prototype HTML files and related local assets to your computer.
• Website access (HTTP/HTTPS) — lets RWP work on the webpages you choose to prototype.
• File URL access — when you enable Chrome's file-access setting, RWP can reopen and continue editing locally saved prototype pages.

These permissions allow RWP to work across different sites. They are not used to sell browsing information or build an advertising profile.

The RWP extension does not include behavioral advertising or extension-usage telemetry that sends the content of pages you edit to RWP.

Google may provide aggregate Chrome Web Store listing metrics, such as store-page views or installs, under Google's own terms. Those Chrome Web Store metrics are separate from the content you edit with the extension.

RWP does not sell personal information or webpage content to advertisers.

RWP can work with URLs and media that you choose to add to a prototype. For example, you may add a YouTube or Vimeo video, an external image URL or other third-party media. Loading that content may connect your browser to the third-party provider under that provider's own privacy policy.

RWP also relies on:

• Google Chrome / Chrome Web Store for extension distribution and browser platform services.
• Stripe for subscription billing and customer-portal management.
• RWP licensing services for trial and license validation.

Information stored locally by the extension generally remains in Chrome until it is replaced, cleared, or the extension/browser data is removed.

Licensing and subscription-related records may be retained for as long as reasonably necessary to provide the service, maintain license and device records, support billing and accounting, prevent abuse, resolve disputes and meet legal obligations.

Prototype files saved to your computer remain under your control and can be deleted using your normal file-management tools.

RWP uses reasonable technical and operational safeguards appropriate to the information it processes. Subscription management is intentionally handled through Stripe's hosted environment rather than being embedded inside RWP.

No method of transmission or storage is completely secure, so absolute security cannot be guaranteed.

• You can turn RWP OFF at any time from the extension interface.
• You can deactivate a licensed device to release its device slot.
• You can manage or cancel a subscription through Stripe's hosted customer portal.
• You can remove local prototype files from your computer at any time.
• You can disable Chrome's access to local file URLs if you do not want RWP to edit saved local pages.

This Privacy Policy may be updated as RWP changes. When the policy is materially revised, the effective date at the top of this page will be updated.

If future versions add new analytics, cloud-storage, collaboration or other data-handling features, this policy should be updated before those features are released.