Security
Fahari uses practical safeguards for its client workspace. This page describes the safeguards in place without claiming a certification or guaranteeing that risk can be eliminated.
Authenticated client access
Fahari’s marketing pages are public so customers and reviewers can learn about the service. The client workspace requires an authenticated identity; business membership and role permissions are checked before workspace data or protected actions are available.
Business data boundaries
Workspace records are associated with a business, and access checks are applied when data is read or changed. The application includes Owner, Admin, Manager, and Viewer roles with different permissions. These controls are intended to prevent one business from accessing another business’s workspace.
Review before action
The current pilot prepares drafts, file reviews, and tasks. It does not automatically publish marketplace listings, edit ads, send buyer messages, or change inventory. Amazon approved Fahari’s SP-API developer profile; application registration and seller authorization remain incomplete, so Fahari does not receive live Amazon seller data. Review source information and every proposed action before relying on it.
Hosting and files
The application uses hosted database and object-storage services. Uploaded files are subject to supported type and size checks, and file access is handled through authenticated workspace routes. The infrastructure providers also apply their own safeguards and service terms.
Your role
Use a unique sign-in, keep devices and account access secure, invite only people who need access, assign the least access needed, and do not upload passwords or secrets. Tell the Fahari workspace owner promptly if you suspect unauthorized access or a security issue.
Scope and reporting
Security safeguards change as the service develops. Fahari has not represented this service as independently audited or certified. To report a security concern, email info@fahari.shop.