134 lines
8.8 KiB
HTML
134 lines
8.8 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en" class="space_grotesk_25f324d0-module___WK4EG__variable inter_3d9c7ff2-module__6cOLqa__variable ibm_plex_mono_a3877f56-module__sxIMvq__variable">
|
||
<head>
|
||
<meta charset="utf-8" />
|
||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||
<link rel="preload" href="/fonts/0c89a48fa5027cee-s.p.2cyn07wtgehh0.woff2" as="font" type="font/woff2" crossorigin />
|
||
<link rel="preload" href="/fonts/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2" as="font" type="font/woff2" crossorigin />
|
||
<link rel="preload" href="/fonts/effe91970fc4db64-s.p.0oace-s_gkfks.woff2" as="font" type="font/woff2" crossorigin />
|
||
<link rel="preload" as="image" href="/images/eventbuzz-logo.png" />
|
||
<link rel="stylesheet" href="/css/site.css" />
|
||
<link rel="stylesheet" href="/css/legal.css" />
|
||
<title>Security — EventBuzz Live</title>
|
||
<meta name="description" content="How EventBuzz Live protects event, attendee, and organiser data — access controls, encryption, infrastructure, and responsible disclosure." />
|
||
<link rel="icon" href="/favicon.ico" />
|
||
</head>
|
||
<body>
|
||
<nav>
|
||
<div class="wrap navrow">
|
||
<a href="/" class="logo">
|
||
<img alt="EventBuzz" width="160" height="36" decoding="async" src="/images/eventbuzz-logo.png"/></a>
|
||
<div class="navlinks navlinks-desktop">
|
||
<a href="/#platform">Platform</a>
|
||
<a href="/#concierge">AI Concierge</a>
|
||
<a href="/#event-engagement">Engagement</a>
|
||
<a href="/#pricing">Pricing</a>
|
||
<a href="/#proof">Customer stories</a>
|
||
</div>
|
||
<a href="#cta" class="btn btn-primary nav-demo-desktop" data-demo-open="true">Request demo</a>
|
||
<button type="button" class="nav-menu-btn" aria-label="Open menu" aria-expanded="false" aria-controls="nav-drawer">
|
||
<svg stroke="currentColor" fill="none" stroke-width="2" viewBox="0 0 24 24" stroke-linecap="round" stroke-linejoin="round" height="22" width="22" xmlns="http://www.w3.org/2000/svg"><line x1="3" y1="12" x2="21" y2="12"></line><line x1="3" y1="6" x2="21" y2="6"></line><line x1="3" y1="18" x2="21" y2="18"></line></svg>
|
||
</button>
|
||
</div>
|
||
</nav>
|
||
<a class="join-event-fab" href="https://join.eventbuzz.live" target="_blank" rel="noopener noreferrer"><span>Join Your Event</span></a>
|
||
<main class="legal-page">
|
||
<div class="wrap">
|
||
<a href="/" class="legal-back">← Back to home</a>
|
||
<div class="legal-kicker">Trust</div>
|
||
<h1>Security</h1>
|
||
<p class="legal-updated">Last updated: 4 August 2026</p>
|
||
<p class="legal-intro">EventBuzz Live is built for events where schedules change, rooms shift, and attendee data must stay protected. This page summarises how Stratawiz Technologies designs, operates, and monitors security for EventBuzz — from organiser workspaces to the AI concierge and live engagement features.</p>
|
||
<div class="legal-content">
|
||
<section>
|
||
<h2>1. Our approach</h2>
|
||
<p>Security is part of how we ship product, not a separate layer we add later. We focus on protecting confidentiality, integrity, and availability of organiser accounts, event configuration, and attendee information processed through the platform.</p>
|
||
<p>Practices below describe our current controls. They may evolve as the product and infrastructure change. For contractual security commitments, refer to your agreement with Stratawiz.</p>
|
||
</section>
|
||
<section>
|
||
<h2>2. Application security</h2>
|
||
<ul>
|
||
<li>Role-based access so organisers can limit who manages events, views reports, or changes settings</li>
|
||
<li>Authenticated sessions with industry-standard password hashing for account credentials</li>
|
||
<li>Input validation and output encoding on forms and APIs to reduce common web risks</li>
|
||
<li>Separation between customer workspaces so one organiser’s event data is not exposed to another by default</li>
|
||
<li>Least-privilege internal access for Stratawiz staff supporting the product</li>
|
||
</ul>
|
||
</section>
|
||
<section>
|
||
<h2>3. Data protection</h2>
|
||
<h3>In transit</h3>
|
||
<p>Traffic to EventBuzz websites and APIs is protected with TLS (HTTPS) so data exchanged between browsers, apps, and our services is encrypted in transit.</p>
|
||
<h3>At rest</h3>
|
||
<p>Customer data stored in our managed databases and object storage is encrypted at rest using provider-supported encryption capabilities.</p>
|
||
<h3>What we process</h3>
|
||
<p>Depending on how you configure an event, this may include organiser profiles, registration fields, check-in records, engagement activity (polls, quizzes, Q&A), and messages handled by the AI concierge. See our <a href="/privacy">Privacy Policy</a> for how personal information is collected and used.</p>
|
||
</section>
|
||
<section>
|
||
<h2>4. Infrastructure & operations</h2>
|
||
<ul>
|
||
<li>Hosting on reputable cloud providers with physical and network controls appropriate for business SaaS</li>
|
||
<li>Environment separation (for example production vs. non-production) to reduce risk from testing and development work</li>
|
||
<li>Regular backups of critical data with restoration procedures reviewed as part of operations</li>
|
||
<li>Monitoring and alerting for availability and unusual error patterns that may indicate incidents</li>
|
||
<li>Dependency and package updates as part of ongoing maintenance</li>
|
||
</ul>
|
||
</section>
|
||
<section>
|
||
<h2>5. Access control & people</h2>
|
||
<p>Access to production systems and customer data is limited to personnel who need it for support, operations, or engineering. Accounts use strong authentication where available. Offboarding processes revoke access when team members leave or change roles.</p>
|
||
<p>Organisers should also apply good hygiene on their side: unique passwords, careful invitation of team members, and prompt removal of users who no longer need access to an event workspace.</p>
|
||
</section>
|
||
<section>
|
||
<h2>6. AI concierge considerations</h2>
|
||
<p>The AI concierge answers from your live event context so attendees get accurate, timely information. Prompts and responses may be processed by model providers under our configuration to deliver the feature. We design flows so answers stay grounded in the event data you manage in EventBuzz, and we continue to refine safeguards against misuse.</p>
|
||
<p>Organisers remain responsible for keeping agenda, room, and policy information up to date so automated answers stay correct.</p>
|
||
</section>
|
||
<section>
|
||
<h2>7. Customer responsibilities</h2>
|
||
<p>You help keep events secure when you:</p>
|
||
<ul>
|
||
<li>Protect account credentials and enable available security options</li>
|
||
<li>Collect only the attendee data you need, and provide required privacy notices</li>
|
||
<li>Configure roles and permissions appropriately for your team and onsite staff</li>
|
||
<li>Use shared devices carefully (sign out after check-in desks or kiosks)</li>
|
||
<li>Report suspected unauthorised access or misuse promptly</li>
|
||
</ul>
|
||
</section>
|
||
<section>
|
||
<h2>8. Incident response</h2>
|
||
<p>If we become aware of a security incident affecting EventBuzz customer data, we investigate, contain, and remediate according to our internal process. Where legally required or contractually agreed, we will notify affected customers without undue delay and share information reasonably needed for their own response.</p>
|
||
</section>
|
||
<section>
|
||
<h2>9. Compliance mindset</h2>
|
||
<p>EventBuzz is designed with privacy and security expectations common to professional events and enterprise buyers — including controlled access, encryption in transit and at rest, and clear data handling practices described in our <a href="/privacy">Privacy Policy</a> and <a href="/terms">Terms of Service</a>.</p>
|
||
<p>Formal certification status (for example SOC or ISO) can vary by product and over time. Contact us if your organisation needs a security questionnaire, DPA, or vendor review package.</p>
|
||
</section>
|
||
<section>
|
||
<h2>10. Responsible disclosure</h2>
|
||
<p>If you believe you have found a vulnerability in EventBuzz or related Stratawiz services, please tell us privately so we can investigate before public disclosure.</p>
|
||
<p>Email <a href="mailto:support1@stratawiz.com">support1@stratawiz.com</a> with a clear description, steps to reproduce where possible, and your contact details. Please avoid accessing or modifying data that is not yours, and do not disrupt live customer events while testing.</p>
|
||
</section>
|
||
<section>
|
||
<h2>11. Contact</h2>
|
||
<p>Security or trust questions:</p>
|
||
<p>Stratawiz Technologies Pvt. Ltd.<br/>Email: <a href="mailto:support1@stratawiz.com">support1@stratawiz.com</a>
|
||
<br/>Phone: <a href="tel:+919175891016">+91 91758 91016</a>
|
||
</p>
|
||
</section>
|
||
</div>
|
||
</div></main>
|
||
<footer>
|
||
<div class="wrap">
|
||
<div class="fbottom" style="margin-top:0;border-top:none;padding-top:0"><span>© 2026 EventBuzz Live. Part of the <a href="https://stratawiz.com/" target="_blank" rel="noopener noreferrer">Stratawiz</a> family.</span><span>
|
||
<a href="/privacy">Privacy</a> · <a href="/terms">Terms</a> · <a href="/security">Security</a>
|
||
</span></div>
|
||
</div></footer>
|
||
|
||
<script src="https://cdn.jsdelivr.net/npm/gsap@3.12.5/dist/gsap.min.js"></script>
|
||
<script src="https://cdn.jsdelivr.net/npm/gsap@3.12.5/dist/ScrollTrigger.min.js"></script>
|
||
|
||
<script src="/js/site.js" defer></script>
|
||
</body>
|
||
</html>
|