Least privilege
Authorization scopes are limited to data needed for dashboards, synchronization, diagnostics, and reporting.
How semfeed protects connected commerce, advertising, and analytics data.
Authorization scopes are limited to data needed for dashboards, synchronization, diagnostics, and reporting.
OAuth tokens are exchanged and stored by backend services, not exposed on public website pages.
Users can disconnect integrations or request deletion of account and connected-source data.
semfeed is designed as an authenticated SaaS application. Production deployments should use HTTPS, environment-managed secrets, access-controlled databases, audit logging, separate development and production environments, and monitored backend services.
Authorization begins only when a signed-in user chooses to connect a platform. The service validates callback parameters, exchanges authorization codes on the server, records granted scopes, and associates authorized resources with the user's workspace.
Access tokens and refresh tokens are stored server-side and encrypted before persistence when supported by the integration path. Public pages do not expose platform credentials.
Product data is scoped to authenticated users and authorized shops or workspaces. Backend requests from the web application use internal authentication headers and user identity checks before accessing protected resources.
Users should be able to understand what the product does, what sources are connected, where connected data appears, and how to disconnect or request deletion. Connected platform data is used for user-facing dashboards, diagnostics, synchronization, alerts, action tasks, and reporting.
Users may disconnect data sources in the application. Account deletion, privacy, and data access requests can be submitted through support. For Shopify app privacy events, semfeed provides webhook endpoints for customer data requests, customer redaction, and shop redaction.
Security and privacy questions can be sent to taow23044@gmail.com.