ciphera-net/pulse
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 15 Wiki Activity

refactor: update branding from Ciphera Pulse to Pulse across the application for consistency and clarity

Browse Source
This commit is contained in:
Usman Baig
2026-01-19 16:58:09 +01:00
parent 15ac469e39
commit 035d78175f
16 changed files with 26 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
app/faq/page.tsx
View File

@@ -1,19 +1,19 @@
export default function FAQPage() {
const faqs = [
{
question: "Is Ciphera Pulse GDPR compliant?",
answer: "Yes, Ciphera Pulse is GDPR compliant by design. We don't use cookies, don't collect personal data, and process all data anonymously."
question: "Is Pulse GDPR compliant?",
answer: "Yes, Pulse is GDPR compliant by design. We don't use cookies, don't collect personal data, and process all data anonymously."
},
{
question: "Do I need a cookie consent banner?",
answer: "No, you don't need a cookie consent banner. Ciphera Pulse doesn't use cookies, so it's exempt from cookie consent requirements under GDPR."
answer: "No, you don't need a cookie consent banner. Pulse doesn't use cookies, so it's exempt from cookie consent requirements under GDPR."
},
{
question: "How does Ciphera Pulse track visitors?",
question: "How does Pulse track visitors?",
answer: "We use a lightweight JavaScript snippet that sends anonymous pageview events. No cookies, no cross-session identifiers (we use sessionStorage only to group events within a single visit), and no cross-site tracking."
},
{
question: "What data does Ciphera Pulse collect?",
question: "What data does Pulse collect?",
answer: "We collect anonymous pageview data including page path, referrer, device type, browser, and country (derived from IP at request time; the IP itself is not stored). No personal information is collected. If you enable optional session replay, see 'What about session replay?' below."
},
{