Access Control Policy
Access Control & Permissions Policy
Last Updated: November 15, 2026
1. Purpose and Scope
This Access Control and Permissions Policy defines how CostRadar manages access to systems, data, and resources to ensure the confidentiality, integrity, and availability of user data and services. This policy implements the principle of least privilege and ensures that access is granted only to authorized individuals and systems.
Radrly sp. z o.o. has one operator with production access: Marcin Nowak, CEO. This policy applies to merchant accounts, that operator, and any future contractor. It does not describe a multi-person security team.
2. Access Control Principles
Least Privilege
Users and systems are granted minimum necessary access rights to perform their functions
Separation of Duties
Critical functions are divided among multiple individuals to prevent fraud and errors
Regular Review
Access rights are reviewed quarterly and revoked when no longer needed
3. User Access Control
3.1 User Authentication
All users must authenticate before accessing CostRadar:
Email and Password: Primary authentication method using bcrypt-hashed passwordsPassword Requirements: Minimum length and complexity rules as enforced at registrationMust be changed if compromisedSession Management: JWT tokens with configurable expiration and inactivity handlingAbuse controls: Rate limiting on authenticated API endpoints by plan. Password login is locked for 30 minutes after 10 failed attempts (email + IP), matching Amazon SP-API Data Protection Policy expectations3.2 Multi-Factor Authentication (MFA)
Administrative access to production systems uses strong authentication practices appropriate to a small ops team (including MFA on critical vendor/hosting accounts where available). End-user TOTP MFA inside CostRadar is not currently a general product feature.
Ops devices with Solution Provider Portal or production access use a 15-minute idle screen lock (Amazon DPP).
3.3 User Data Isolation
CostRadar implements strict data isolation:
Row-Level Security (RLS): Database policies ensure users can only access their own dataUser ID Verification: All API requests verify user identity via JWT tokenNo Cross-User Access: Users cannot view or modify data belonging to other usersAPI Authorization: Every endpoint checks user permissions before processing requests4. Subscription Plan Based Access
4.1 Feature Access by Plan
Free Plan
Dashboard with key metricsMonthly cost breakdownManual cost entryStore platform connection (Shopify, Amazon, WooCommerce, BigCommerce, and/or Allegro per product limits)Basic analyticsAd-supported experienceAdvanced Plan ($29.99/mo)
All Free plan featuresAd-free experiencePriority email supportAdvanced analyticsPremium Plan ($49.99/mo /store)
All Advanced plan featuresAI-powered cost optimization insightsPersonalized savings recommendationsAutomated opportunity detectionStep-by-step implementation guides4.2 Plan Enforcement
User plan checked on every authenticated requestFeatures requiring higher plan tiers show upgrade promptsAPI endpoints enforce plan restrictions (403 Forbidden for unauthorized access)Integration connections validated against user's plan5. Integration Access Control
5.1 OAuth 2.0 Integration
Third-party integrations use OAuth 2.0 for secure authorization:
Shopify: OAuth with order/product/discount scopes as configured for the appAmazon Seller Central: SP-API authorization for marketplaces the merchant connectsWooCommerce: store API keys/credentials provided by the merchantOptional ads/email tools: OAuth when the merchant connects Meta, Google, TikTok, etc.Token Storage: Platform tokens are encrypted at rest with AES-256-GCM. The server will not store a token if the encryption key is missingToken Scope: Minimum necessary permissions requestedToken Revocation: Upon disconnection or account deletion where supported5.2 Integration Permissions
5.3 User Control
Users maintain full control over integrations:
Can connect/disconnect integrations at any time via SettingsView which integrations are connected and when last syncedDisconnect deletes the stored access and refresh tokens for that connection. TikTok Shop order and fee data is removed within 30 days. Historical orders on other platforms stay in the account until the account is deleted, unless a platform's own uninstall flow removes them.Data synced from disconnected integrations is retained per Data Retention Policy6. Employee and Administrative Access
6.1 Administrative Access Levels
CEO (sole operator)
Marcin Nowak holds production SSH, database, GitHub, and vendor admin access. There is no separate CTO, DBA, support staff, or developer with access.Deploys run through GitHub Actions with an encrypted deploy key.Separation of duties and just-in-time database access are not in place.Database queries by the operator are not written to a separate tamper-proof audit store.6.2 Employee Access Management
Onboarding: Access provisioned based on role and need-to-knowStrong auth: MFA on critical hosting/vendor accounts where availableRestricted admin paths: Production admin access limited to authorized operatorsOffboarding: Access revoked promptly upon departure6.3 Privileged Access Monitoring
Administrative actions logged where systems support itPeriodic access reviews for production credentialsUnusual access investigated when detected7. API and System Access
7.1 API Authentication
All API requests must be authenticated:
User API Calls: Bearer token (JWT) in Authorization headerServer-to-Server: Service role keys (never exposed to frontend)Webhook Signatures: HMAC verification for incoming webhooksRate Limiting: API calls limited to prevent abuse (implemented via sliding window algorithm) Advanced plan: 100 requests/minute, burst 150Premium plan: 1,000 requests/minute, burst 1,500Returns 429 status with Retry-After header when exceededRate limit headers (X-RateLimit-*) included in all responses7.2 CORS and Network Security
CORS configured to allow only trusted originsContent Security Policy (CSP) headers prevent XSS attacksAll external requests use HTTPS with TLS 1.2 or TLS 1.3. TLS 1.0 and 1.1 are disabled.Firewall rules restrict access to production database7.3 Third-Party Service Access
Access to sub-processors is controlled:
Self-hosted API: Service role / server secrets protected, used server-side onlyOpenAI: API key stays on the server. Prompts can include business metrics and chat text. OpenAI's standard API retention is up to 30 days for abuse monitoring. Zero Data Retention is not enabled.Shopify API: Per-user OAuth tokens, stored encryptedPayment Processors: Per-user OAuth tokens, read-only access8. Access Review and Audit
8.1 Regular Access Reviews
At least every 12 months, and after any personnel change: production and vendor accounts, SSH keys, GitHub collaborators, deploy keys, and API keys. No recorded review exists yet.There is no weekly or monthly staffed access-review rota.8.2 Access Audit Logs
Comprehensive logging of access events:
User login/logout eventsFailed authentication attemptsAdministrative actions and configuration changesDatabase queries by staffAPI requests with user ID and endpointIntegration connections and disconnectionsData access and modifications8.3 Audit Log Retention
Authentication, integration, Nginx, and deployment logs are kept up to 90 days unless an incident requires longer.Logs are files on the host and GitHub Actions history. They are not stored in separate tamper-proof storage.9. Access Violations and Enforcement
9.1 Violation Detection
Automated monitoring detects potential violations:
Unusual access patterns (time, location, volume)Attempts to access unauthorized resourcesMultiple failed authentication attemptsPrivilege escalation attemptsSuspicious administrative actions9.2 Enforcement Actions
Automatic: Rate limiting for API abuse where implementedInvestigative: Security team reviews alerts, determines if legitimateCorrective: Revoke access, reset credentials, notify affected usersThere is no HR function. A future contractor who misuses access loses that access the same day.9.3 Incident Response
Access violations trigger incident response per our Security Incident Response Policy.
10. User Responsibilities
Users are responsible for:
Keeping login credentials secure and confidentialNot sharing account access with othersUsing strong, unique passwordsLogging out when finished, especially on shared devicesReporting suspected unauthorized access immediatelyReviewing connected integrations regularlyDisconnecting integrations that are no longer needed11. Compliance and Standards
This policy complies with:
GDPR Article 32 (Security of Processing)CCPA security requirementsShopify App Store security standardsOWASP Authentication and Authorization best practicesISO 27001 and NIST are references only. Radrly is not ISO 27001 certified and does not claim an ISO audit.12. Contact Information
For access control questions or to report unauthorized access:
13. Policy Review
This Access Control Policy is reviewed and updated:
Annually as part of security policy reviewAfter security incidents involving access controlWhen new features or integrations are addedFollowing changes in regulatory requirementsBased on feedback from security audits