Privacy Policy
Last updated: April 2026
1. Information We Collect
Account information: When you sign in with Azure AD, we receive your name, email address, and organization identifier. We use this to authenticate your session and associate your projects.
Project data: Portal projects, pages, and component configurations you create are stored on our servers. This data is associated with your account and accessible only to you (and your team members on Team plans).
Usage data: We collect basic analytics about feature usage to improve the product. This includes page views, component usage counts, and publish frequency. We do not track individual Dataverse record content.
Payment information: Payment processing is handled by Stripe. We do not store credit card numbers. Stripe provides us with subscription status and billing identifiers.
2. How We Use Your Information
- To provide and maintain the PortalForge service
- To authenticate your identity and manage your subscription
- To store and sync your portal projects
- To send service-related communications (billing, security, downtime)
- To improve the product based on aggregate usage patterns
We do not sell your personal information to third parties. We do not use your data for advertising.
3. Dataverse Data
When you connect PortalForge to a Dataverse environment, the builder makes API calls directly from your browser to your Dataverse instance using your own Azure AD credentials. PortalForge acts as a client-side tool — your Dataverse data flows between your browser and your Microsoft environment. We do not proxy, store, or cache your Dataverse records on our servers.
Published portals run on your Power Pages environment using your Dataverse backend. PortalForge's role ends at deployment.
4. Data Retention
Your portal projects are retained as long as your account is active. If you delete a project, it is permanently removed from our servers. If you cancel your subscription, your projects remain accessible in read-only mode for 90 days, after which they may be deleted.
5. Security
Authentication is handled through Microsoft Azure AD (MSAL). All data in transit is encrypted with TLS. Project data at rest is stored in encrypted databases. We do not store Dataverse credentials — authentication is token-based with your Azure AD tenant.
6. Third-Party Services
- Microsoft Azure AD — authentication
- Stripe — payment processing
- Microsoft Dataverse — data source (your environment, your credentials)
7. Your Rights
You can export your project data at any time (JSON export). You can delete your projects individually. To delete your account entirely, contact us at hello@portalforge.dev.
8. Changes
We may update this policy from time to time. Material changes will be communicated via email or an in-app notification. Continued use of the service after changes constitutes acceptance.
9. Contact
For privacy-related questions, contact hello@portalforge.dev.