← All legal documents

Legal

Subprocessors

We use the providers below to operate Praxsys. A provider is a subprocessor under the DPA when it processes customer personal data on our behalf. Identity and payment providers may also have independent responsibilities for their own services.

Effective

1. Operator and contact

Praxsys is operated by Maher Khamiss. In this provider list, “we,” “us,” and “our” refer to the operator. Contact maher@praxsys.io for legal, privacy, and support questions.

2. Vercel · Hosting and website analytics

Vercel hosts and delivers the marketing website and its server endpoints and provides website analytics. Depending on the request, it handles network and device information, page requests, information passing through hosted endpoints, and usage measurements. It acts as a subprocessor where hosted services process customer personal data on our behalf.

3. Supabase · Authentication, database, and storage

Supabase provides app authentication, database services, and file storage. Relevant information includes account and sign-in details, memberships, and customer content stored in Praxsys. It acts as a subprocessor for customer personal data handled on our behalf.

4. Resend · Email and newsletter contacts

Resend provides inquiry acknowledgments, service and transactional email, and newsletter contact management. It handles email addresses, message contents, and delivery or subscription status. It acts as a subprocessor where it sends communications containing customer personal data on our behalf.

5. Google · Optional sign-in provider

When you choose Google sign-in, Google authenticates your Google account and supplies the basic identity information described in our Privacy Policy. Google operates its account service under its own privacy terms. Listing Google here does not mean Praxsys can access your Gmail, Drive, Calendar, or contacts through sign-in.

6. Paddle · Payment processing

For paid purchases processed through Paddle, Paddle acts as merchant of record and handles checkout, billing, transaction records, and related tax and fraud processing. It has its own responsibilities for that information and is not automatically a subprocessor for customer workspace content. Praxsys uses the subscription and transaction information returned to administer paid access.

7. Processing locations and safeguards

Providers operate infrastructure and support in multiple countries. Processing locations depend on the service, deployment, and provider arrangements; this page does not promise that data stays in a single country. Contact maher@praxsys.io for information about the arrangements relevant to your customer data.

Customer-data processing is subject to the DPA’s confidentiality, security, subprocessor, and international-transfer requirements. Provider privacy pages give additional information about their own services and responsibilities.

8. Changes and questions

We maintain this list as the providers used for Praxsys change. Affected customers will be informed of intended subprocessor additions or replacements and given an opportunity to raise data-protection objections as described in the DPA. Send questions, requests, or objections to maher@praxsys.io.

← All legal documents