Anteriq Subprocessor List
This list identifies the third-party services Anteriq uses to provide the Service, and the third-party services a customer firm may choose to connect to it. It is incorporated by reference into the Data Processing Addendum (“DPA”). Anteriq may update this list with notice to customers as described in the DPA.
Anteriq’s own processing takes place in the United States, in Anteriq’s own AWS account. Beyond that account, this list does not state where a subprocessor processes data: the other vendors below operate their own infrastructure under their own regional practices. Customer-directed integrations are operated by their own vendors under the customer firm’s own account, and may use those vendors’ infrastructure.
Platform Subprocessors
These services are engaged by Anteriq at the platform level and apply to all customer firms using the Service.
| Subprocessor | Role / Service | Categories of Data Processed |
|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting & infrastructure — including Cognito (authentication), DynamoDB (database), S3 (file/document storage), SES (transactional email — available as an alternate to the configured provider), KMS (encryption key management), Lambda (compute), API Gateway, CloudFront (CDN), EventBridge (scheduled jobs), CloudWatch (logging/monitoring), SSM (configuration/secrets), and Bedrock (managed AI model inference for the Data Analysis module). Anteriq’s AWS resources are provisioned in the us-west-2 (US West, Oregon) region | All customer and end-client data processed by the Service; account and authentication data |
| BoldSign | Electronic signature platform — preparation, delivery, and execution of documents sent for e-signature | Documents submitted for signature; signer identity, contact information, and audit/event trail data |
| Postmark | Transactional email delivery — notification and system emails. Postmark is Anteriq’s configured transactional email provider; Amazon SES is available as a manually-selectable alternate, not as automatic failover | Recipient email addresses; message content for transactional notifications |
| Stripe (Anteriq’s account) | Subscription billing of customer firms — card capture at signup, stored payment method, monthly invoices, and refunds for the firm’s own Anteriq subscription | Firm billing-contact name and email; billing address; payment-card data entered directly into Stripe-hosted fields. Anteriq retains only a masked card summary (brand and last four digits) and a card fingerprint supplied by Stripe |
Note on AI processing (Amazon Bedrock). Anteriq’s AI features run on Amazon Bedrock within Anteriq’s own AWS account; content is never sent to a model vendor’s own API. According to AWS, inputs to and outputs from Amazon Bedrock are not used to train Amazon’s or any third-party foundation models, and are not shared with model providers — model providers have no access to the deployment accounts that run inference, and therefore no access to prompts or completions. Anteriq uses a United States inference profile, which keeps processing within AWS’s US regions; requests may be routed among those regions for capacity, and where AWS’s automated abuse detection stores inputs and outputs, that storage also remains within US regions.
Customer-Directed Integrations
These services are engaged by the customer firm, not by Anteriq. The firm holds its own account and agreement with each vendor and controls whether the integration is active. Anteriq connects to them on the firm’s instruction.
| Subprocessor | Role / Service | Categories of Data Processed |
|---|---|---|
| Stripe (the firm’s own account) | Payment processing for the firm’s billing of its own clients — a firm that invoices its clients through the platform does so through that firm’s own Stripe account; Anteriq does not store full card numbers | The end client’s billing contact information and payment amounts; payment-card and bank-account data entered directly into Stripe-hosted fields under the firm’s own account |
| LACRM (Less Annoying CRM) | Optional CRM synchronization — enabled only when a customer firm explicitly configures the integration; not active by default | Contact and client data that the firm elects to sync to their LACRM account |
| Optional read-only calendar connection. A planner authorizes access to their own Google account; the permissions Anteriq requests are read-only, and Anteriq never writes to a calendar | The planner’s email address; titles and times of calendar events read into Anteriq | |
| Microsoft | Optional read-only calendar connection to Outlook / Microsoft 365, equivalent to the Google integration above and likewise read-only | The planner’s email address; titles and times of calendar events read into Anteriq |
| Calendly | Optional scheduling. When a firm supplies a Calendly booking link, a scheduling view is shown in the client portal; it loads from Calendly in the client’s browser | The end client’s name, email address, IP address, and browser information, together with any booking details they enter |
Changes to This List
Anteriq may add, remove, or replace a platform subprocessor by updating this page with at least 30 days’ advance notice to customers, as described in DPA Section 8.1 (notice may be provided by updating this page, by email to Customer’s account owner at the email address on file for the account, or through the Service). Customers who object to a new platform subprocessor may exercise any rights provided in the DPA.
Customer-directed integrations are not subject to that notice period, because the customer firm adds and removes them itself.
The “Last updated” date shown with this list indicates when it was most recently changed.