Skip to main content

ARISE Events OS — Privacy Policy

Last updated: 17 April 2026

Effective date: 17 April 2026

Published at: https://arisegtm.com/events-os/privacy

1. Who we are

ARISE Events OS is a HubSpot Marketplace application developed and operated by ARISE GTM Ltd ("we", "us", "our").

Registered address: Available at arisegtm.com/about-us Privacy contact: support@arisegtm.com Data Controller: ARISE GTM Ltd (for data processed as part of providing the Application) Data Processor: ARISE GTM Ltd acts as a data processor for personal data held in your HubSpot portal


2. What this policy covers

This policy explains how ARISE Events OS ("the Application") collects, stores, uses, and protects data when installed on a HubSpot portal.

This policy applies to:

  • HubSpot portal administrators who install the Application
  • Users who interact with the Application's features (event setup, registration, check-in, reporting)
  • Contacts in the HubSpot portal whose data is processed by the Application when running events
  • Visitors to the arisegtm.com/events-os website

3. Data we collect and why

3.1 Data read from your HubSpot portal

When installed, the Application accesses data from your HubSpot portal to provide its services:

Data type Properties accessed Purpose
Contact records Name, email, job title, company, lifecycle stage, deal associations, events_os_* rollup properties Match event registrants to contacts; calculate pipeline attribution; generate post-event intelligence
Company records Name, industry, employee count Audience analysis; attribution reports
Deal records Name, amount, stage, close date, associated contacts Pipeline attribution; Deal Room intelligence
Event records (custom/app object) All event properties Core application data
Registration records (custom/app object) All registration properties Attendee lifecycle management
Owner/user records Name, HubSpot Meetings link Meeting URL resolution for virtual events
HubSpot account settings Portal ID, timezone, currency Application configuration

 

3.2 Event registration data

When contacts register for events managed by the Application:

  • Name, email address, job title, company name
  • Registration date, ticket type, invite source
  • RSVP decisions and timestamps
  • Check-in status, check-in time, check-in method
  • Waitlist status and fit score (AI-generated, not stored in HubSpot)

This data is stored as Registration records in your HubSpot portal, associated to the registrant's Contact record.

3.3 Portal authentication data

  • OAuth access tokens and refresh tokens — stored encrypted at rest (AES-256-GCM, 32-byte key) in our Railway backend database. Used to make authorised API calls to your HubSpot portal on your behalf.
  • Portal ID — used to isolate your data from all other customers. Every database query includes a portal_id constraint.

3.4 AI-generated intelligence outputs

The Application generates intelligence outputs using Anthropic's Claude API:

Output Where stored Retention
Post-event narratives Supabase (intelligence layer) Duration of active subscription + 30 days
Pipeline attribution calculations Supabase Duration of active subscription + 30 days
No-show risk scores Computed fresh on each request; not persisted Not retained
Waitlist fit scores Written to Registration record in HubSpot Subject to HubSpot retention settings
Invite recommendations Returned in real-time; not stored Not retained

 

3.5 Anonymised benchmark data

Performance metrics from completed events (attendance rates, pipeline per attendee, event type) are contributed to a shared benchmark dataset. This data is fully anonymised — it contains no portal IDs, contact names, email addresses, company names, or any other personally identifiable information. It is aggregated statistical data only.

3.6 Notification log

When the Application generates post-event alerts and notifications:

  • Portal ID, event ID, notification title and body
  • Created timestamp and delivery timestamp
  • Stored in our Railway SQLite database
  • Retained for 90 days then automatically deleted

3.7 Usage and operational data

  • Agent run logs — records of AI intelligence operations (portal ID, timestamps, success/failure status, duration, model used). No content of agent outputs is stored here.
  • Command audit trail — orchestrator commands (portal ID, event ID, command type, subscriber results). Last 50 per portal retained.
  • Server access logs — IP addresses, request timestamps, HTTP status codes. Retained for 30 days.
  • Error logs — sanitised before storage. No tokens, credentials, or personal data included.

3.8 Website visitor data

The arisegtm.com/events-os website may collect:

  • Standard web server access logs (IP address, browser type, pages visited, referrer)
  • Any information you voluntarily submit via contact or demo booking forms

4. How we use your data

Purpose Data used Lawful basis
Operating the Application (event builds, registration, check-in, workflows) HubSpot CRM data, OAuth tokens Contract performance
Pipeline attribution calculations Deals, contacts, registrations Contract performance
AI-generated intelligence (narratives, risk scores, recommendations) Event and registration data Contract performance
Anonymous cross-portal benchmarks Aggregated, anonymised event metrics Legitimate interest
Security monitoring and abuse prevention Access logs, error logs Legitimate interest
Billing and subscription management Portal ID, plan data Contract performance
Support and troubleshooting Audit trail, command log Legitimate interest
Product improvement Anonymised usage patterns Legitimate interest
Chrome extension functionality Portal ID from HubSpot URL, notification preferences Contract performance

5. Data sharing

We do not sell your data. We do not allow advertisers to target users based on data processed by the Application.

We share data with the following sub-processors:

Sub-processor Purpose Data shared Location
HubSpot, Inc. CRM platform host All CRM data lives in your HubSpot portal — we read/write via OAuth USA (EU SCCs in place)
Anthropic, PBC Claude AI API Event context, attendee summaries for intelligence generation USA
Railway Corp. Backend hosting (Node.js/SQLite) Encrypted OAuth tokens, operational data USA
Supabase, Inc. Intelligence data storage Post-event narratives, attribution data, anonymised benchmarks EU (by configuration)
Resend, Inc. Transactional email Email addresses for operational notifications only USA

All sub-processors are bound by data processing agreements. For transfers to the USA, we rely on Standard Contractual Clauses (SCCs) or equivalent adequacy mechanisms.

We may disclose data to competent authorities where required by law, or to protect against fraud, security threats, or abuse.


6. Data storage and security

6.1 Where data is stored

Data Location Encryption
OAuth access/refresh tokens Railway, SQLite AES-256-GCM at rest
Post-event narratives, attribution Supabase (EU) At rest + TLS in transit
Anonymised benchmarks Supabase (EU) At rest + TLS in transit
Notification log Railway, SQLite At rest
HubSpot CRM data Your HubSpot portal HubSpot's own security controls

 

6.2 Security measures

The Application implements the following security controls:

  • Encryption at rest — OAuth tokens encrypted with AES-256-GCM, 32-byte randomly generated key
  • Transport encryption — All API communication over HTTPS/TLS 1.2+
  • Rate limiting — Tiered per-route rate limiting on all endpoints
  • Input validation — Zod schema validation on all 27+ mutation endpoints
  • Webhook verification — HMAC-SHA256 signature verification on all inbound HubSpot webhooks
  • Portal isolation — Every database query includes a portal_id constraint; one customer cannot access another's data
  • RSVP token security — 256-bit cryptographically secure random tokens, single-use only, 48-hour TTL
  • Error sanitisation — Stack traces and internal paths stripped from all error responses
  • Secret-safe logging — No tokens or credentials logged at any verbosity level
  • Dependency security — Regular npm audit; all dependencies pinned to exact versions
  • Admin route protection — Admin endpoints gated by server-side API key

6.3 Security breach notification

In the event of a personal data breach, we will notify affected customers and relevant supervisory authorities in accordance with GDPR Article 33 (within 72 hours of becoming aware) and Article 34 where applicable.


7. Data retention

Data Retention period
HubSpot CRM data (events, registrations, contacts) Held in your HubSpot portal — subject to your own retention settings and GDPR obligations
Post-event narratives + attribution (Supabase) Duration of active subscription + 30 days after cancellation
OAuth access and refresh tokens Duration of active subscription; deleted on uninstall
Server access logs 30 days
Notification log 90 days
Command audit trail Last 50 entries per portal (rolling)
Agent run logs 90 days
Anonymised benchmark data Indefinitely (no personal data)
Billing records 7 years (UK/EU legal requirement)

 

On cancellation: Post-event intelligence data stored in Supabase (narratives, attribution calculations) is deleted within 30 days of subscription cancellation. HubSpot CRM data (Event records, Registration records, contact rollup properties) remains in your portal under your control and is not deleted by us.

On uninstall: OAuth tokens are deleted immediately on uninstall. Supabase data is scheduled for deletion within 30 days.


8. Your rights (GDPR / UK GDPR)

If you are located in the United Kingdom or European Economic Area, you have the following rights regarding personal data we process:

  • Right of access — Request a copy of personal data we hold about you or your contacts
  • Right to rectification — Request correction of inaccurate personal data
  • Right to erasure — Request deletion of your personal data ("right to be forgotten")
  • Right to restriction — Request that we limit processing of your data in certain circumstances
  • Right to data portability — Request your data in a structured, machine-readable format
  • Right to object — Object to processing based on legitimate interests
  • Rights related to automated decision-making — The Application uses AI for scoring and recommendations but no decision with legal or significant effect is made automatically without human review

To exercise any of these rights, contact support@arisegtm.com. We will respond within 30 days. We may need to verify your identity before processing your request.

Right to complain: You have the right to lodge a complaint with the Information Commissioner's Office (ICO) at ico.org.uk (UK), or your local EU supervisory authority.


9. Event registrant rights

If you are a contact who registered for an event managed by this Application, your personal data is held in the HubSpot portal of the organisation that ran the event. To request access, correction, or deletion of your personal data, contact that organisation directly — their contact details will be in the confirmation email you received when registering.

ARISE GTM Ltd acts as a data processor for this data on behalf of the event organiser (the data controller). If you cannot reach the event organiser or believe your rights are not being respected, contact us at support@arisegtm.com and we will direct you to the appropriate contact.


10. HubSpot Marketplace

ARISE Events OS is distributed via the HubSpot App Marketplace. Your use of the Application is subject to:

  • This Privacy Policy
  • HubSpot's Privacy Policy (legal.hubspot.com/privacy-policy)
  • HubSpot's Acceptable Use Policy

HubSpot manages billing and subscription for Marketplace applications. Payment data is processed by HubSpot, not by ARISE GTM Ltd.


11. Anthropic API

The Application sends event context data to Anthropic's Claude API to generate intelligence outputs. This includes:

  • Event details (name, type, date, capacity)
  • Anonymised or pseudonymised attendee summaries (job titles, industries, deal counts — never full names or emails in AI prompts)
  • Registration and attendance statistics

Data sent to Anthropic is processed in accordance with Anthropic's API Data Usage Policy. We do not send personally identifiable information (names, email addresses) to the Anthropic API.


12. Chrome Extension

The ARISE Events OS Chrome Extension:

  • Reads the current HubSpot URL to extract the portal ID (stored locally in chrome.storage.local)
  • Injects a branded visual element adjacent to the Events OS card (does not read or modify card data)
  • Polls our backend for post-event notification alerts
  • Sends report creation requests to our backend on user request

The extension does not collect browsing history, read page content outside HubSpot, or transmit any data except portal ID and explicit user-triggered report requests.


13. Cookies

The arisegtm.com/events-os website may use essential cookies for session management. We do not use tracking, advertising, or analytics cookies without consent.

The Application itself (HubSpot card, RSVP pages, check-in pages) does not set cookies.


14. Children's data

The Application is not designed for use by children under 13 and we do not knowingly collect data from children. If you believe we have collected data from a child, contact support@arisegtm.com immediately.


15. Changes to this policy

We will update this policy when material changes are made. We will notify HubSpot portal administrators of significant changes via email at least 14 days before they take effect. The date at the top of this page indicates when it was last updated.

For non-material changes (formatting, clarifications that do not affect data practices), we will update the policy without separate notification.


16. Contact

Privacy enquiries and data subject requests: Email: support@arisegtm.com

Security vulnerability reports: Email: support@arisegtm.com

General support: Email: support@arisegtm.com Website: arisegtm.com/events-os

ARISE GTM Ltd United Kingdom arisegtm.com