Advisory API Systems LLC

Business Continuity and Data Portability Statement

Effective Date: Upon First API Use
Version: 1.2
Last Updated: March 2026

1. INTRODUCTION

1.1 Purpose

This Business Continuity and Data Portability Statement describes Advisory API Systems LLC’s (“Company”) plans and procedures for:

Maintaining service continuity during disruptive events
Recovering from disasters affecting service availability
Enabling customers to maintain access to their data and transition to alternative solutions if needed

1.2 Commitment

Advisory API Systems is committed to providing reliable, continuous service to our customers. We recognize that API customers depend on our services for their advisory operations, and we take this responsibility seriously.

1.3 Scope

This statement covers:

Business continuity planning
Disaster recovery procedures
Data portability provisions
Service transition support

2. BUSINESS CONTINUITY PLANNING

2.1 Business Continuity Program

Advisory API Systems maintains a Business Continuity Plan (BCP) designed to:

Identify critical business functions and dependencies
Assess potential threats and their impacts
Establish procedures for maintaining operations during disruptions
Define recovery priorities and timelines
Ensure customer communication during incidents

2.2 Plan Components

The BCP addresses:

Critical Functions:

API service availability
User support operations
Billing and account management
Security monitoring

Threat Categories:

Natural disasters (earthquakes, fires, floods)
Technology failures (hardware, software, network)
Cybersecurity incidents
Utility outages (power, telecommunications)
Pandemic and public health events
Key personnel unavailability

2.3 Plan Maintenance

The Business Continuity Plan is:

Reviewed and updated annually
Tested through tabletop exercises
Revised following significant incidents
Updated for changes in infrastructure or operations

3. DISASTER RECOVERY

3.1 Recovery Objectives

Advisory API Systems maintains the following recovery objectives:

Metric	Objective	Description
Recovery Time Objective (RTO)	4 hours	Maximum time to restore service
Recovery Point Objective (RPO)	1 hour	Maximum acceptable data loss

Note: RPO applies to system configurations, operational data, and customer input and output data.

3.2 Infrastructure Resilience

Geographic Redundancy:
API infrastructure is deployed on servers located in Germany (European Union), benefiting from the strict data protection requirements of the GDPR. Redundancy is maintained across multiple geographic locations within the EU to protect against regional disasters.

High Availability:

Load balancing distributes requests across multiple servers
Automatic failover to healthy instances
No single point of failure for critical components

Backup Systems:

System configurations backed up daily
Backups stored in geographically separate locations
Backup restoration procedures tested quarterly

3.3 Disaster Recovery Procedures

In the event of a disaster affecting service availability:

Phase 1: Detection and Assessment (0-30 minutes)

On-call personnel alerted
Initial impact assessment conducted
User notification prepared

Phase 2: Containment and Stabilization (30 minutes - 2 hours)

Affected components isolated
Traffic redirected to healthy infrastructure
Interim measures implemented
Regular status updates provided

Phase 3: Recovery (2-4 hours)

Full service restoration from redundant systems
System integrity verified
Performance monitoring intensified
Users notified of resolution

Phase 4: Post-Incident (Following Recovery)

Root cause analysis conducted
Remediation measures implemented
Incident report prepared
Lessons learned documented

3.4 Communication During Incidents

During service-affecting incidents, customers will be notified via:

Email to registered contacts
Status page updates (if applicable)
Direct communication for critical customers

Communications will include:

Nature and scope of the incident
Expected duration (if known)
Workarounds (if available)
Regular updates until resolution

4. SERVICE CONTINUITY PROVISIONS

4.1 Ongoing Service Commitment

Advisory API Systems commits to:

Maintaining the API service as a going concern
Providing reasonable advance notice of any planned service discontinuation
Supporting customer transitions in the event of service changes

4.2 Service Discontinuation Notice

In the unlikely event that Advisory API Systems decides to discontinue the API service:

Notice Period:
Users will receive a minimum of ninety (90) days written notice before service discontinuation.

Notice Contents:

Reason for discontinuation
Final service date
Data export options
Recommended transition steps
Support available during transition

4.3 Service Transition Support

During any service discontinuation period, Advisory API Systems will provide:

Continued API access through the final service date
Data export assistance
Technical consultation (reasonable scope)
Documentation to facilitate transition
Refund of prepaid fees for services not rendered

5. DATA PORTABILITY

5.1 User Data Ownership

Principle: User owns all User Data submitted to the API.

Advisory API Systems processes User Data solely to provide the API services, including generating investment advice for User, and does not claim ownership of User Data.

5.2 Data Processing Model

The API data processing model:

User Data is submitted with each API request
Data is processed in real-time
Results are returned immediately
User Data, including API requests and responses, are retained by Advisory API Systems after the response for audit and compliance purposes.

5.3 Data Available for Export

Upon customer request, Advisory API Systems can provide:

Data Category	Format	Availability
API Usage History	JSON	Upon request
Billing Records	PDF/CSV	Upon request
API Request Logs	JSON	Upon request

Note: API request logs contain request metadata (timestamps, endpoints, status codes).

5.4 Export Request Process

To request data export:

Submit request via email to [email protected]
Specify data categories and format preferences
Verify identity and authorization
Receive data within ten (10) business days

5.5 No Vendor Lock-In

Advisory API Systems is designed to avoid vendor lock-in:

Standard Inputs:
The API accepts standard financial data that customers can compile from their own records. No proprietary data formats are required.

Portable Outputs:
API outputs are recommendations expressed in terms of standard asset classes. Users can implement recommendations through any investment vehicles.

No Proprietary Dependencies:
Users are not required to use proprietary systems or formats that would impede transition to alternative solutions.

6. ALTERNATIVE SOLUTIONS

6.1 Market Alternatives

In the event customers need to transition from Advisory API Systems, alternative approaches include:

In-House Development:
Users with technical resources may develop internal portfolio optimization tools.

Alternative Vendors:
Other providers offer portfolio optimization APIs, though methodologies may differ.

Manual Processes:
Traditional portfolio construction approaches using spreadsheets and financial planning software.

6.2 Transition Considerations

When evaluating transitions, customers should consider:

Methodological differences between providers
Integration requirements with existing systems
Data formatting and migration needs
Training and change management
Regulatory disclosures to end clients

6.3 Transition Support

Advisory API Systems will provide reasonable transition support, including:

Documentation of API inputs and outputs
Historical usage data
Technical consultation (reasonable scope, by arrangement, hourly fees assessed)
Extended access during transition (case-by-case basis)

7. KEY PERSONNEL CONTINUITY

7.1 Key Personnel Risk

Advisory API Systems acknowledges that as a small firm, key personnel continuity is a relevant consideration.

7.2 Mitigation Measures

To mitigate key personnel risk:

Documentation:

Technical systems and processes documented
Operational procedures recorded
Critical knowledge captured in accessible form

Professional Network:

Relationships with technical professionals who could provide emergency support
Vendor relationships that could provide interim services

Legal Structure:

Business entity structured to survive individual unavailability
Insurance coverage for key personnel events

7.3 Emergency Contact

In the event of unavailability of primary contacts, customers may reach:

Name: Thomas Seehusen
Email: [email protected]
Phone: (310) 839-0358

8. FINANCIAL STABILITY

8.1 Financial Responsibility

Advisory API Systems maintains financial resources to:

Support ongoing operations
Fund necessary technology investments
Weather temporary revenue disruptions
Fulfill obligations to customers

8.2 Fee and Billing Policy

Advisory API Systems charges per-API-use fees as set forth in Schedule A of the User Agreement. Individual Clients pay a flat fee of $79.95 per successful API use. RIA Clients pay on a graduated monthly tier schedule ($34.95 per call for the first 25 calls in a calendar month, $27.95 per call for calls 26 through 100, and $21.95 per call for calls 101 and above).

RIA Clients: Advisory API Systems charges RIA Clients monthly in arrears via the payment method on file with our payment processor, Stripe, Inc. The payment method is automatically charged at calendar month-end for the closing month’s API Uses. This limits RIA Client financial exposure to one month of usage.

Individual Clients: Payment is collected at the time of each API use via credit card through our payment processor, Stripe, Inc. Individual Clients are charged only upon successful delivery of an API response. This pay-per-use model means Individual Clients have no prepayment exposure.

Advisory API Systems does not accept substantial prepayments that would create customer exposure in the event of service discontinuation.

8.3 Refund Commitment

In the event of service discontinuation:

No charges for services not rendered
Refund of any prepaid amounts
Pro-rata adjustment for partial periods

9. REGULATORY CONTINUITY

9.1 Registration Maintenance

Advisory API Systems maintains its investment advisor registration and will provide notice to customers if registration status changes materially.

9.2 Compliance Continuity

Business continuity planning includes maintaining regulatory compliance, including:

Record retention requirements
Required disclosures and filings
Client communication obligations

9.3 Regulatory Notifications

Users will be notified of:

Material changes to registration status
Regulatory actions affecting the firm
Changes in regulatory requirements affecting the API

10. TESTING AND VALIDATION

10.1 Business Continuity Testing

Business continuity procedures are tested through:

Test Type	Frequency	Scope
Plan Review	Annually	Document review and updates
Tabletop Exercise	Annually	Scenario walkthrough with key personnel
Failover Testing	Quarterly	Technical failover to redundant systems
Backup Restoration	Quarterly	Verification of backup restoration procedures

10.2 Test Results

Testing results are:

Documented and reviewed
Used to identify improvement opportunities
Incorporated into plan updates

10.3 User Notification of Testing

Users will be notified in advance of any planned testing that may affect service availability.

11. CUSTOMER PREPAREDNESS

11.1 User Responsibility

While Advisory API Systems maintains business continuity capabilities, customers should also prepare for potential service disruptions:

Recommended User Actions:

Maintain contingency plans for temporary API unavailability
Document current API integrations and dependencies
Preserve copies of API outputs as part of client records
Identify alternative approaches for critical operations

11.2 Integration Best Practices

To maximize resilience, customers should:

Implement appropriate error handling and retry logic
Design systems to degrade gracefully during API unavailability
Cache results where appropriate (subject to data freshness requirements)
Monitor API health and respond to degradation alerts

11.3 Communication Preferences

Users should maintain current contact information in the API developer portal to ensure receipt of critical communications.

12. COMMITMENTS SUMMARY

Commitment	Description
Service Availability	99.5% monthly uptime target (per SLA)
Recovery Time	4-hour RTO
Discontinuation Notice	90 days minimum
Data Ownership	User owns User Data
Data Export	Available upon request
Transition Support	Reasonable assistance provided
No Lock-In	Standard inputs/outputs, no proprietary dependencies

13. CONTACT INFORMATION

Advisory API Systems LLC

Email: [email protected]
Phone: (310) 839-0358

Data Export Requests:
Email: [email protected]
Subject: Data Export Request - [User Name]

This Business Continuity and Data Portability Statement is incorporated by reference into the User Agreement. By using the API, you acknowledge that you have reviewed this statement.