Privacy Policy
Effective Date: February 13, 2026
•Last Updated: February 13, 2026
1. INTRODUCTION
This Privacy Policy describes how B:Side Assist (“we,” “us,” or “our”) collects, uses, discloses, and protects your personal information when you use our financial management and AI-powered business insights platform (the “Platform”).
Beta Release Status
B:Side Assist is currently in beta release. As a beta product, our data practices, features, and security measures are continuously evolving. This Privacy Policy reflects our current data handling practices and will be updated as the Platform develops.
Technology Stack
The Platform is built on Next.js with TypeScript, utilizes Supabase PostgreSQL for data storage, and Groq Cloud for AI inference. Understanding our technical architecture helps explain our data collection and processing practices detailed below.
By accessing or using the Platform, you acknowledge that you have read, understood, and agree to be bound by this Privacy Policy. If you do not agree with our policies and practices, do not use the Platform.
2. INFORMATION WE COLLECT
We collect information that you provide directly, information generated through your use of the Platform, and information from third-party services. All data is stored in our Supabase PostgreSQL database with specific security measures detailed in Section 7.
2.1 Account and Profile Information
We collect the following information when you create an account:
- Email address
- Full name
- Business name
- NAICS (North American Industry Classification System) code
- Industry classification
- Revenue range
- Employee count
- Account creation timestamp
- Premium subscription status
- Onboarding completion status
This information is used to create and maintain your account, provide personalized services, and deliver appropriate business insights based on your industry and business size.
2.2 Financial Account Information
When you connect your financial accounts through Plaid:
Account Data:
- Account ID (unique identifier)
- Account name and official name
- Account type and subtype (checking, savings, credit card, etc.)
- Account mask (last 4 digits)
- Current balance
- Available balance
- ISO currency code
- Account creation and update timestamps
Plaid Connection Data:
- Item ID (connection identifier)
- Plaid access token (stored as a confidential secret)
- Financial institution ID and name
- Webhook URL for real-time updates
- Connection creation and update timestamps
- Consent expiration time
Security Note: Plaid access tokens are stored in our database and treated as sensitive secrets. They are protected by access controls and encryption in transit and at rest. We do not store your actual banking credentials—these are managed securely by Plaid Inc.
2.3 Transaction Data
We collect and store detailed transaction information:
- Transaction ID (unique identifier)
- Associated user ID and account ID
- Transaction amount
- Transaction date
- Merchant name
- Transaction category
- Pending status
- ISO currency code
- Payment channel (online, in-store, etc.)
- Location data: City, Region/state, Country
- Transaction creation timestamp
This transaction data forms the foundation of our financial insights, spending analysis, anomaly detection, and business intelligence features.
2.4 Financial Alerts and Monitoring
When you configure financial alerts:
- Alert ID (unique identifier)
- Alert type (spending threshold, unusual activity, etc.)
- Threshold amounts or parameters
- Active/inactive status
- Alert creation timestamp
- Last triggered timestamp
- Preferred notification method
2.5 Machine Learning and Analytics Data
To provide AI-powered insights and anomaly detection, we collect:
ML Models:
- Model ID
- Associated user ID and account ID
- Trained model data (Isolation Forest algorithm)
- Training timestamp and model version
- Feature names used in training
- Performance metrics
Feature Cache:
- Cache ID
- Associated transaction ID and user ID
- Computed feature vectors (numerical representations)
- Computation timestamp and feature version
This data enables personalized anomaly detection and improves the accuracy of our AI recommendations over time.
2.6 Conversational AI Data
When you interact with our AI assistant, we collect:
- Conversation ID and title
- User ID
- Message content (your questions and AI responses)
- Role (user or assistant)
- Creation and update timestamps
- AI model used for each response
- Token count (computational usage)
Your conversation history is retained to provide context-aware responses and improve your experience with the AI assistant.
2.7 Document and Invoice Data
When you upload invoices or documents:
- Document ID
- User ID
- Original file name
- File storage URL
- Document embedding (vector representation for AI processing)
- Document metadata
- Upload timestamp
Documents are processed using Supermemory (api.supermemory.ai) to enable intelligent document search, retrieval, and document-based question answering.
2.8 Subscription and Billing Data
If we offer paid plans, we may collect billing-related metadata such as your plan tier and subscription status. We will update this Privacy Policy if billing features materially change our data practices.
2.9 Preferences and Settings
Notification Preferences:
- User ID
- Email notifications enabled/disabled
- Push notifications enabled/disabled
- SMS notifications enabled/disabled
- Specific alert types preferences
Expense Categories:
- Category ID
- User ID
- Custom category name
- Budget limit for category
- Category color (UI preference)
2.10 Financial Goals and Planning
Goals:
- Goal ID
- User ID
- Target amount
- Current amount saved
- Deadline date
- Goal category
Recurring Transactions:
- Recurring ID
- User ID
- Identified pattern
- Next expected date
- Expected amount
- Merchant name
2.11 Tax Documents
- Document ID
- User ID
- Tax year
- File storage URL
- Document type
- Upload timestamp
2.12 Session and Authentication Data
- Session ID
- User ID
- Session creation timestamp
- Expiration timestamp (30-day default)
- Device information
- IP address
Session data is used for security monitoring and to maintain your authenticated state across the Platform.
2.13 API Usage and Activity Logs
API Usage:
- Log ID
- User ID
- API endpoint accessed
- Request data
- Response status
- Timestamp
Audit Logs:
- Log ID
- User ID
- Action performed
- Resource type accessed
- Resource ID
- Timestamp
- IP address
These logs are maintained for security monitoring, debugging, billing accuracy, and compliance purposes.
2.14 Onboarding Progress
- User ID
- Completed step identifier
- Completion timestamp
- Step-specific data
2.15 Webhook Events
- Event ID
- User ID
- Associated Plaid item ID
- Webhook type
- Event payload
- Processed status
- Creation timestamp
Webhook events enable real-time updates when your financial accounts have new transactions or status changes.
2.16 Bank Connection Activity
- Log ID
- User ID
- Plaid item ID
- Connection action (link, relink, remove)
- Action status
- Timestamp
3. HOW WE USE YOUR INFORMATION
We use the collected information for the following specific purposes:
3.1 Core Platform Functionality
- Account Management: Creating and maintaining your user account using the information you provide
- Financial Account Integration: Connecting and synchronizing your bank accounts via Plaid
- Transaction Tracking: Retrieving, categorizing, and displaying your financial transactions
- Balance Monitoring: Providing real-time account balance information
3.2 AI-Powered Financial Insights
- Anomaly Detection: Training and deploying machine learning models (Isolation Forest) to identify unusual spending patterns
- Conversational AI: Powering our AI assistant using multiple models (e.g., openai/gpt-oss-120b, openai/gpt-oss-20b, llama-3.3-70b-versatile)
- Document Processing: Indexing and analyzing uploaded invoices/documents via Supermemory to support search and Q&A
- Spending Analysis: Generating insights based on transaction patterns
- Financial Forecasting: Predicting future cash flow and identifying potential financial issues
3.3 Alerts and Notifications
- Custom Alerts: Monitoring financial thresholds and triggering notifications based on your configured alert settings
- Email Notifications: Sending alerts via Resend email service based on your notification preferences
- Real-time Updates: Delivering instant updates through real-time notifications when new transactions or account changes occur
3.4 Business Intelligence
- Industry Benchmarking: Comparing your business metrics against industry standards using NAICS codes
- Expense Categorization: Organizing expenses using system and user-defined categories
- Recurring Transaction Detection: Identifying subscription services and regular payments from transaction patterns
- Goal Tracking: Monitoring progress toward financial objectives you configure
3.5 Platform Improvement
- Performance Optimization: Using derived features and caching to accelerate repeated calculations
- Usage Analytics: Analyzing usage signals to optimize system performance
- Feature Development: Understanding user behavior through anonymized analytics via Vercel Analytics
- Model Training: Improving AI accuracy by training on anonymized transaction patterns
3.6 Security and Compliance
- Fraud Prevention: Monitoring account activity for suspicious patterns
- Access Control: Implementing Row-Level Security (RLS) policies to ensure users can only access their own data
- Audit Trail: Maintaining comprehensive logs of user actions and system events
- Webhook Processing: Handling secure communications from Plaid via webhook processing
3.7 Subscription Management
- Billing: Managing subscriptions and plan status (if billing features are enabled)
- Feature Access: Controlling premium feature availability based on subscription status
- Usage Tracking: Monitoring API usage for billing and rate limiting purposes
3.8 Tax and Financial Documentation
- Document Storage: Securely storing documents you upload (e.g., invoices and receipts)
- Invoice Processing: Analyzing uploaded invoices and supporting document Q&A using Supermemory and our AI providers
3.9 Communication
- Transactional Emails: Sending account-related communications via Resend
- Support: Responding to customer inquiries using conversation history
- Updates: Notifying users of platform changes, security updates, or important alerts
3.10 Legal and Regulatory
- Compliance: Maintaining records required by financial services regulations
- Dispute Resolution: Preserving transaction history and audit logs for dispute investigation
- Legal Obligations: Responding to lawful requests for user data when required
4. THIRD-PARTY SERVICES AND DATA SHARING
B:Side Assist integrates with multiple third-party services to provide core functionality. Your data is shared with these services as described below.
4.1 Plaid Inc. (Banking Integration)
Privacy Policy: https://plaid.com/legal/#privacy-statement
Purpose: Plaid enables secure connections to your financial institutions, retrieves transaction data, and provides account balance information.
Data Shared:
- Banking credentials (encrypted, managed by Plaid, never stored by us)
- Account numbers and routing numbers
- Transaction data retrieved from your bank
- Account balances and account details
- Financial institution information
Your Control: You can disconnect Plaid connections at any time through account settings, which will revoke our access to future transaction updates.
4.3 Groq Cloud (AI Model Inference)
Privacy Policy: https://groq.com/privacy-policy/
Purpose: Groq provides high-speed AI model inference for our conversational AI assistant and financial analysis features.
AI Models Used:
- openai/gpt-oss-120b - Advanced reasoning and complex analysis
- openai/gpt-oss-20b - Secondary model for fallback and support tasks
- llama-3.3-70b-versatile - Tertiary fallback model for general queries
- compound-beta - Web search + synthesis for certain research workflows
Data Shared:
- User prompts and questions from chat messages
- Financial context (transaction summaries, account balances)
- Anonymized business metrics where possible
4.2 Supabase (Database and Authentication)
Privacy Policy: https://supabase.com/privacy
Purpose: Supabase provides our PostgreSQL database infrastructure, user authentication system, and real-time data synchronization.
Data Shared: Data you provide and data generated through your use of the Platform is stored and processed within Supabase's cloud-hosted infrastructure.
Security Measures:
- Encryption at rest and in transit
- Row-Level Security (RLS) enabled with policies restricting users to their own data
- Bcrypt password hashing
- JWT token-based authentication
Data Location: Supabase cloud infrastructure (region determined by service configuration)
4.6 Delphi AI (Conversational AI)
API Endpoint: https://api.delphi.ai
Purpose: Delphi AI provides specialized conversational capabilities using a “chrismyers” clone configuration.
Data Shared:
- User messages and questions
- Conversation context and history
- Conversation identifiers
Data Flow: User message → B:Side Assist → Delphi AI API → Response → B:Side Assist → User
4.8 Resend (Email Services)
Privacy Policy: https://resend.com/legal/privacy-policy
Purpose: Resend handles transactional emails, financial alerts, and notification delivery.
Data Shared:
- Email addresses associated with your account
- Notification content generated from your alert settings
- Transactional email content (account confirmations, password resets, etc.)
Email Types:
- Financial alert notifications
- Account security notifications
- Onboarding and welcome emails
- Platform update announcements
User Control: You can unsubscribe from non-essential emails via links in email footers where available.
4.9 Vercel Analytics (Usage Analytics)
Privacy Policy: https://vercel.com/legal/privacy-policy
Purpose: Vercel Analytics provides privacy-friendly usage analytics and performance monitoring.
Data Collected:
- Page views and navigation patterns
- User interactions (anonymized)
- Performance metrics (page load times, etc.)
- Device and browser information
- General geographic location (country/region level)
Privacy: Vercel Analytics is designed to be privacy-focused and does not use cookies or track personal information beyond aggregate usage patterns.
4.10 Google Maps API (Location Visualization)
Privacy Policy: https://policies.google.com/privacy
Purpose: Google Maps enables visualization of transaction location data to provide geographic spending insights.
Data Shared:
- Transaction location data (city, region, country)
- Coordinates for map rendering
Usage: Only aggregated location data from transactions is displayed; no real-time location tracking is performed.
4.12 Convex (Real-Time Database for Webhook Notifications)
Status: Used for real-time webhook update notifications
Purpose: Convex provides real-time delivery of Plaid webhook update notifications so the UI can refresh without polling.
Data Shared:
- User identifier (Supabase user ID)
- Item identifier (database item UUID)
- Webhook code/event type and timestamp
Data Minimization: We do not store bank credentials or full transaction content in Convex; it is used for lightweight event notifications only.
4.13 Supermemory (Document Indexing & Memory)
API Endpoint: https://api.supermemory.ai
Privacy Policy: https://supermemory.ai/privacy-policy
Purpose: Supermemory supports document search/Q&A and memory features (e.g., storing document metadata and conversation exchange summaries to improve retrieval and personalization).
Data Shared:
- Uploaded documents and file metadata (e.g., file name, type, size, upload timestamp)
- Document identifiers to associate indexed content with your account
- Document Q&A queries you submit and related context
- AI conversation exchange summaries (as part of product memory/personalization features)
Isolation: Content is tagged to your user identifier to isolate your documents and memory from other users.
4.14 Web Search Providers (Exa Primary, Tavily Fallback)
Primary API Endpoint: https://api.exa.ai
Fallback API Endpoint: https://api.tavily.com
Purpose: Exa is our primary web search provider for up-to-date information. Tavily is used as a backup provider if Exa is unavailable.
Data Shared:
- Search queries derived from your request (which may include personal information if you include it)
- Request metadata (e.g., IP address and user agent from our server making the request)
4.15 E2B (Sandboxed Code Execution)
API Endpoint: https://api.e2b.dev
Purpose: E2B provides a sandbox environment for executing Python code used in advanced financial analysis (e.g., complex calculations or generating charts).
Data Shared:
- Python code executed on your behalf
- Structured financial datasets provided to the sandbox (e.g., transactions and account data) when required for the requested analysis
4.16 Have I Been Pwned (Password Breach Checking)
API Endpoint: https://api.pwnedpasswords.com
Purpose: We use the Have I Been Pwned “Pwned Passwords” service to help detect commonly breached passwords during signup.
Data Shared:
- A short prefix of a cryptographic hash of the password (k-anonymity model)
- Standard request metadata from the device making the request (e.g., IP address, user agent)
Important: Your plaintext password is not sent to Have I Been Pwned.
4.17 External Image Providers (Merchant Logos)
Purpose: We use third-party image services to display merchant avatars/logos in the UI (e.g., transaction lists and dashboards).
Services:
- UI Avatars (https://ui-avatars.com)
- Logo.dev (https://img.logo.dev)
Data Shared: When your browser loads these images, the provider may receive your IP address and standard browser request headers (such as user agent and referrer) and the image URL requested.
6. DATA RETENTION
Our data retention policies are designed to balance operational needs, legal compliance requirements, and your privacy rights.
6.1 Account Data
Retention: Account profile data is retained for the duration of your account plus 30 days after an account deletion request to allow for recovery in case of accidental deletion.
Deletion: After the 30-day grace period, all personal account data is permanently deleted, except as required for legal or regulatory compliance.
6.2 Financial Transaction Data
Retention: Transaction data is retained indefinitely while your account is active.
Purpose:
- Long-term financial analysis and trend identification
- Tax preparation and financial reporting
- Anomaly detection model accuracy
- Compliance with financial record-keeping regulations
Post-Deletion: Upon account deletion, transaction data may be retained in anonymized form for up to 7 years to comply with financial services record-keeping requirements.
6.3 Conversation and Chat Data
Retention: Chat conversations and messages are retained indefinitely while your account is active to provide context-aware AI assistance.
Deletion: Upon account deletion, chat history is deleted within 30 days unless specific messages are flagged for quality improvement purposes (in which case they are anonymized).
User Control: You can delete individual conversations or messages at any time through the chat interface.
6.4 Machine Learning Models
Retention: Trained anomaly detection models are retained indefinitely while your account is active.
Purpose
- Tracking model performance over time
- Reverting to previous model versions if needed
- Analyzing model evolution for research purposes
Post-Deletion: Models are deleted within 90 days of account deletion after being anonymized for potential aggregated research use.
6.5 Transaction Feature Cache
Retention: Derived feature caches are maintained while your account is active to optimize performance.
Purpose: Pre-computed features accelerate repeated calculations and improve platform responsiveness.
Deletion: Feature cache data is deleted within 7 days of account deletion.
6.6 Document and Invoice Data
Retention: Uploaded documents and derived data (such as indexes/embeddings) are retained while your account is active or until you manually delete them.
Post-Deletion: All documents and their embeddings are permanently deleted within 30 days of account deletion.
User Control: You can delete individual documents at any time through the document management interface.
6.7 Session Data
Automatic Expiration: Sessions automatically expire after 30 days of inactivity.
Cleanup: Expired session records are purged from the database within 7 days of expiration.
6.8 API Usage and Audit Logs
Retention: API usage and audit logs are retained for 2 years from creation.
Purpose:
- Security monitoring and incident investigation
- Billing accuracy and dispute resolution
- Compliance with audit requirements
Post-Deletion: Even after account deletion, anonymized audit logs may be retained for up to 2 years for regulatory compliance.
6.9 Webhook Events
Retention: Webhook event logs are retained for 90 days.
Purpose: Debugging integration issues and ensuring transaction synchronization accuracy.
Cleanup: Events older than 90 days are automatically purged.
6.10 Subscription and Billing Data
Retention: If billing features are enabled, billing records are retained as required by applicable tax and financial record-keeping laws.
Purpose: Compliance with tax and financial record-keeping regulations.
Post-Deletion: Where permissible, billing records may be dissociated from personal identifiers and retained only as required by law.
7. DATA SECURITY
7.1 Current Security Measures
We implement multiple layers of security to protect your data:
7.1.1 Encryption
- In Transit: All data transmitted using TLS 1.2 or higher
- At Rest: Data stored in Supabase PostgreSQL is encrypted
- Sensitive Data: Plaid access tokens are stored as secrets and protected by access controls and encryption in transit and at rest
7.1.2 Database Security
Row-Level Security (RLS): Enabled with policies that restrict users to their own data across our database tables.
7.2 Beta Security Status
Important: B:Side Assist is currently in beta release.
Security vulnerabilities may exist and are being proactively identified and remediated by our development team. Security measures are subject to continuous enhancement.
Active Security Initiatives:
- Updating session cookie configuration to set httpOnly: true
- Continuously reviewing and tightening RLS policies and access controls
- Implementing additional rate limiting on API endpoints
- Enhancing input validation and sanitization
- Strengthening encryption for sensitive data fields
7.3 Security Monitoring
Audit Logs: We maintain audit logs of significant actions (with timestamps and, where applicable, IP addresses) to support security monitoring.
Anomaly Detection: Unusual account access patterns are flagged for review.
Session Monitoring: Active sessions may be monitored to detect suspicious activity and protect accounts.
7.4 Third-Party Security
We carefully select third-party services with strong security practices and review their security documentation (where available).
7.5 Data Breach Response
In the event of a data breach:
- Detection: Our monitoring systems and audit logs help detect unauthorized access
- Containment: Immediate steps are taken to contain the breach and prevent further unauthorized access
- Assessment: We assess the scope and impact of the breach
- Notification: We notify affected users and, where required, regulators consistent with applicable law
- Remediation: Security measures are strengthened to prevent recurrence
- Reporting: We comply with all regulatory reporting requirements
7.6 User Security Responsibilities
You can enhance your account security by:
- Using strong, unique passwords
- Not sharing your login credentials
- Logging out when using shared devices
- Keeping your email account secure (password reset emails)
- Reviewing account activity regularly
- Reporting suspicious activity immediately
8. YOUR PRIVACY RIGHTS
8.1 Rights Under GDPR (European Users)
If you are located in the European Economic Area (EEA), United Kingdom, or Switzerland, you have the following rights under the General Data Protection Regulation (GDPR):
- Right to Access: Obtain confirmation and access to your personal data
- Right to Rectification: Correct inaccurate or incomplete personal data
- Right to Erasure (“Right to be Forgotten”): Request deletion of your personal data
- Right to Restrict Processing: Request restriction of processing your personal data
- Right to Data Portability: Receive your data in a machine-readable format
- Right to Object: Object to processing for certain purposes
- Right to Withdraw Consent: Withdraw consent at any time
- Right to Lodge a Complaint: File complaint with supervisory authority
8.2 Rights Under CCPA (California Residents)
If you are a California resident, you have the following rights under the California Consumer Privacy Act (CCPA):
- Right to Know: Request disclosure of personal information collected
- Right to Delete: Request deletion of personal information
- Right to Opt-Out of Sale: We do NOT sell your personal information
- Right to Non-Discrimination: No discriminatory treatment for exercising rights
8.3 Rights for All Users
Regardless of location, all users have the right to:
8.3.1 Account Access and Updates
- View and update your account and profile information
- Manage connected financial accounts
- Review your transaction history
- Delete chat conversations and messages
- Remove uploaded documents
8.3.2 Communication Preferences
- Manage notification settings and communication preferences
- Unsubscribe from non-essential emails via email footer links
- Control alert configurations and alert notifications
8.3.3 Data Download
Request a complete export of your data in JSON format.
8.3.4 Account Deletion
Delete your account and request permanent removal of personal data (subject to retention policies in Section 6).
8.4 Verification Process
To protect your privacy, we verify your identity before fulfilling rights requests:
Verification Methods:
- Email verification sent to your registered email address
- Account login authentication
- Additional verification questions if needed for sensitive requests
Timeline: Most requests are processed within 30 days; complex requests may take up to 60 days with notification of extension.
9. INTERNATIONAL DATA TRANSFERS
9.1 Data Storage Locations
Primary Database: Data is stored in Supabase's cloud infrastructure. The specific geographic region depends on service configuration.
Third-Party Services (may process data in the U.S. and other jurisdictions):
- Plaid (banking integration)
- Supabase (database and authentication)
- Groq Cloud (AI inference)
- Delphi AI (conversational AI)
- Supermemory (document indexing/search)
- Resend (email services)
- Vercel (hosting and analytics)
- Google APIs (e.g., Maps/OAuth, if enabled)
- Convex (real-time updates)
- Exa and Tavily (web search)
- E2B (sandboxed code execution)
9.2 Legal Basis for Transfers
For EEA, UK, and Swiss Users: We rely on the following mechanisms for international data transfers:
- Standard Contractual Clauses (SCCs): European Commission-approved clauses with third-party processors
- Adequacy Decisions: Transfers to countries deemed adequate by the European Commission
- Necessity for Contract Performance: Some transfers necessary to perform our contract with you
10. ARTIFICIAL INTELLIGENCE AND AUTOMATED DECISION-MAKING
10.1 AI and Machine Learning Systems
B:Side Assist uses artificial intelligence and machine learning extensively. This section provides transparency about how AI affects you.
10.2 Anomaly Detection (Isolation Forest)
Technology: Custom-trained Isolation Forest machine learning models
Purpose: Automatically identify unusual transactions that may indicate fraudulent activity, billing errors, unexpected spending, or business anomalies
Models: We may train user-specific anomaly detection models based on transaction history and feedback.
Your Control:
- You can dismiss false-positive anomaly alerts
- You can provide feedback to improve model accuracy
10.3 AI-Powered Conversational Assistant
Technology: Large language models via Groq Cloud and other providers (including tool-based web search and sandboxed code execution)
Models Used (examples):
- openai/gpt-oss-120b - Complex reasoning and detailed analysis
- openai/gpt-oss-20b - Secondary fallback and support tasks
- llama-3.3-70b-versatile - Additional fallback coverage
- compound-beta - Web search + synthesis for certain research workflows
Specific model IDs may change over time as we improve quality, safety, and reliability.
Data Used:
- Your chat messages and conversation context
- Financial information you connect or provide (e.g., account and transaction summaries)
- Business profile details you provide (optional)
- Uploaded document content and derived context (if you use document features)
Purpose:
- Answer financial questions and explain insights
- Provide analysis of spending patterns and trends
- Help you understand documents and extracted information
Your Control:
- You control what information you share in prompts
- You can delete conversations and messages (where available)
- You can choose to ignore AI-generated suggestions
Limitations:
- AI responses may contain errors or inaccuracies
- Recommendations are informational, not professional financial advice
- Outputs depend on the data you provide and the data available through connected services
10.4 Transaction Categorization
Technology: AI-powered categorization using merchant names, transaction amounts, and patterns
Data Used: Transaction details such as merchant name, amount, and description
Purpose: Automatically assign spending categories to transactions
Impact on You:
- Affects spending reports and category breakdowns
- Influences budget tracking
- Used in financial insights generation
Your Control:
- You can manually override suggested categories (where available)
- Your corrections can help improve future categorization accuracy
10.5 Document Processing and OCR
Technology: Supermemory (document indexing/search) and AI models for analysis
Data Used:
- Uploaded invoices, receipts, and other documents
- Associated metadata you provide (e.g., filenames, tags, or categories)
Purpose:
- Extract text and structured data from documents
- Enable semantic search across documents
- Categorize and organize financial documents
Impact on You:
- Automated invoice data extraction
- Intelligent document search
- Document-based financial insights
Your Control:
- You control which documents are uploaded
- You can delete documents and associated derived data (where applicable)
- You can review extracted data for accuracy
10.6 Recurring Transaction Detection
Technology: Pattern recognition algorithms
Data Used: Historical transaction patterns
Purpose: Identify subscription services and recurring payments
Impact on You:
- Alerts for upcoming recurring charges
- Subscription spending analysis
- Identification of potentially unwanted subscriptions
Your Control:
- You can confirm or dismiss identified patterns
- You can manually mark transactions as recurring
10.7 Financial Forecasting
Technology: Time series analysis and predictive modeling
Data Used:
- Historical transaction patterns
- Business profile information
- Industry benchmarks
Purpose:
- Predict future cash flow
- Forecast upcoming expenses
- Identify potential financial issues
Impact on You:
- Proactive financial alerts
- Business planning insights
- Risk identification
Accuracy: Forecasts are estimates based on historical patterns; actual outcomes may vary significantly.
10.8 Right to Human Review
GDPR Compliance: For EU users, you have the right not to be subject to automated decision-making with legal or similarly significant effects.
Our Practice: No automated decisions have legal or contractual effects without human oversight. AI recommendations are informational and require your action to implement. You can always request human review of AI-generated insights.
10.9 AI Bias and Fairness
Awareness: We acknowledge that AI systems may exhibit biases based on training data.
Mitigation Efforts:
- Regular review of AI outputs for bias
- Diverse training data where possible
- User feedback mechanisms to identify issues
- Transparency about AI limitations
Reporting Bias: If you believe AI systems are producing biased or unfair results, please report this at verification@bsideassist.ai.
11. CHILDREN'S PRIVACY
11.1 Age Restriction
B:Side Assist is intended exclusively for business users aged 18 years or older. We do not knowingly collect personal information from individuals under the age of 18.
11.3 COPPA Compliance
The Platform is not directed to children under 13 years of age. We do not knowingly collect personal information from children under 13 in compliance with the Children's Online Privacy Protection Act (COPPA).
12. CHANGES TO THIS PRIVACY POLICY
12.1 Beta Product Evolution
As B:Side Assist is currently in beta release, our data practices, features, and security measures are continuously evolving. This Privacy Policy will be updated to reflect new features, additional third-party service integrations, enhanced security measures, changes in data retention policies, and regulatory compliance updates.
12.2 Notification of Material Changes
Material Changes include:
- New categories of personal data collected
- New third-party data sharing arrangements
- Reduced data security protections
- Changes to data retention periods
- New uses of personal data not previously disclosed
Notification Methods:
- Email notification to your registered email address
- Prominent notice on the Platform dashboard
- Update to the “Last Updated” date at the top of this policy
Advance Notice: We will provide at least 30 days' notice of material changes before they take effect.
13. CONTACT INFORMATION
13.1 Privacy Questions and Requests
For questions about this Privacy Policy or to exercise your privacy rights, please contact:
Email: verification@bsideassist.ai
Response Time: We aim to respond to all privacy inquiries within 5 business days and to fulfill verified requests within 30 days.
13.4 Third-Party Privacy Policies
For questions about how third-party services process your data, please refer to their privacy policies:
- • Plaid: https://plaid.com/legal/#privacy-statement
- • Supabase: https://supabase.com/privacy
- • Groq: https://groq.com/privacy-policy/
- • Delphi: https://www.delphi.ai/privacy
- • Supermemory: https://supermemory.ai/privacy-policy
- • Resend: https://resend.com/legal/privacy-policy
- • Convex: https://www.convex.dev/privacy
- • Vercel: https://vercel.com/legal/privacy-policy
- • Google: https://policies.google.com/privacy
- • Exa: https://exa.ai/privacy
- • Tavily: https://tavily.com/privacy
- • E2B: https://e2b.dev/privacy
Legal Compliance Summary
This Privacy Policy is intended to address key privacy requirements, including (where applicable):
- General Data Protection Regulation (GDPR) - EU Regulation 2016/679
- California Consumer Privacy Act (CCPA) - California Civil Code Section 1798.100 et seq.
- Children's Online Privacy Protection Act (COPPA) - 15 U.S.C. §§ 6501–6506
- CAN-SPAM Act
- State data breach notification laws
Version: 1.0 (Beta)
By using B:Side Assist, you acknowledge that you have read and understood this Privacy Policy and agree to the collection, use, and disclosure of your information as described herein.