What this site stores
The example workspace can save brand profiles, keywords, competitors, questions, response drafts, opportunity states, profile preferences, and workflow events in your browser. Browser-only workspace details are not sent to a rouse application data store or email list.
When connected workspace storage is enabled, those details are saved to the configured rouse data store and can be opened by other tabs or browsers using the same service. Unsaved edits remain in the current tab as a recovery copy when browser storage is available.
What happens when you visit
The site’s hosting provider may process ordinary request information, such as IP addresses, browser details, and access logs, to deliver the website. Fonts and brand images are served with the website.
The homepage mascot is a static image on its purple backdrop. Selecting it opens the shared assistant described below; the character does not track your pointer, animate a greeting, or store greeting state. Separate discovery diagrams retain their reduced-motion and static fallbacks.
Advertising measurement
rouse measures whether its advertising leads to reports, contact requests and booked calls. When measurement is live, the public marketing, research, careers, contact, privacy and report pages load the Meta Pixel and record the events described below. Meta and rouse may use cookies, the Pixel and similar browser storage on those pages to collect this information, and Meta may use it to measure and deliver advertising. rouse does not show a banner or offer an on-site switch. To limit how Meta uses this information for advertising, use Meta’s ad settings or the Digital Advertising Alliance opt-out; you can also block or clear cookies in your browser. With each page view rouse also records the name of the website that linked you here, such as google.com, but never the linking page’s address or what you searched for, and never sends it to Meta. Measurement is separate from permission to deliver a report, answer a question or contact you. Signed-in, account, client, operations, checkout and onboarding pages never load the Pixel.
When you arrive through a tagged campaign or from another website, the browser stores a bounded attribution record for up to 30 days. In live mode, Meta Pixel may also set its browser identifier. rouse may retain only a bounded landing path, the referring website’s name and approved campaign fields—UTM source, medium, campaign, content and term; Meta campaign, ad-set and ad identifiers; placement; and Meta click/browser identifiers. With each saved event it also keeps your browser’s user agent—the browser and device description your browser sends with every request—and sends it to Meta with that event as a match key. It never saves an arbitrary landing URL, page query, private report or service token, chat, question, research content or form text as campaign attribution.
In live mode, Meta may receive page views, report starts, scheduler opens, successfully saved report-email leads, successfully saved question or fallback meeting requests and, when booked-call measurement is enabled, booked calls through its Pixel and Conversions API. A scheduler open is not reported as a booked appointment. For lead and contact events, rouse normalizes and hashes the submitted email on the server before delivery; it does not send the plain email or a raw IP address to Meta in this version. Browser and server copies share a random event identifier so Meta can deduplicate them.
Only rouse’s own booking calendar confirms a booked call. When booked-call measurement is enabled, rouse’s server reads that calendar with read-only access and counts a call only when an appointment made through our booking page is confirmed there with exactly one guest from outside rouse. Opening, loading or clicking the scheduler never counts, and neither does a fallback meeting request. Bookings by rouse staff, rouse.io addresses and existing customers are excluded. For each counted booking, rouse sends Meta only a hash of the guest’s normalized email address and the time the call was booked. If the same hashed address has a rouse measurement event from the previous 30 days, the booking also carries that event’s Meta browser identifiers, browser user agent and page address; otherwise it names the contact page. rouse does not read or send the meeting’s title, description, time or link, or anyone’s name; other guests’ addresses are used only to apply these rules and are never stored or sent. A booking already sent to Meta cannot be withdrawn if you later cancel; a booking cancelled before it is sent is not reported. A rebooking within seven days of a counted booking is not reported again.
rouse keeps measurement events and delivery receipts for 180 days by default, then deletes them through the attribution retention process. The retention setting is bounded between 30 and 730 days. So that a booking is never reported twice, rouse separately keeps a one-way record of each booking it has evaluated for 800 days: a hash of the calendar and event identifiers, the booking time, the outcome (such as counted, repeat or excluded) and whether it was cancelled—never an email address, name or meeting details. Admins see only aggregate campaign counts and delivery states, which include booked calls—not Meta/browser identifiers, email hashes, booking records, request payloads, credentials or raw provider errors. In preview mode, events remain inside rouse and no Meta code is loaded or event sent to Meta. When measurement is off, no events are accepted.
When you chat with the mascot
The chat keeps the conversation in the page’s memory until you clear it or reload. When the rouse service is connected, submitted questions and a bounded recent conversation are sent to that service. Reviewed rouse answers use a saved knowledge base. When broader research is configured, the service sends those explicit messages to OpenAI and may search public sources. It does not automatically attach your workspace, current page address, private report link, or meeting-request details. Common contact details and tokens are filtered, but avoid entering private information. rouse does not persist chat transcripts in its application data store; provider processing and retention are governed by the configured provider and account settings.
Contact questions and meeting requests are separate from your assistant conversation. With your consent, a connected rouse service saves your name, email, optional company and submitted question in a team review queue. A meeting request additionally saves your time zone, preferred times and topic. When hosted contact intake and its mail service are explicitly enabled, the same transaction also queues one plain-text alert to the configured info@rouse.io shared inbox. That alert contains only those submitted fields, the request identifier and submission time; it does not include your chat, current page, cookies, report or service links, or workspace data. The mail provider processes that copy for delivery. The saved receipt does not prove provider acceptance, inbox receipt, a reply time or a confirmed appointment. Active contact requests and their alert, attempt and reconciliation records are deleted after 90 days by the running retention sweep; an operator can delete an exact request sooner through the private service. An alert with a live sending lease is briefly deferred rather than erased mid-send; an expired lease is classified as uncertain and then removed. Clearing chat or resetting the example workspace does not delete a contact request, deletion cannot recall mail already accepted by the delivery provider, and a non-identifying daily request count remains.
If an approved query-free scheduler link is configured, either a Calendly event or a Google Calendar appointment schedule, the Contact page shows that calendar immediately on wider screens; on narrower screens, an explicit action opens it in a full-page dialog so page and provider scrolling do not compete. An explicit booking action also loads it inside the assistant. The inline frame carries only the provider’s fixed embed layout marker and, for Calendly, the current site host; it does not forward the current page path, page query, chat or existing contact details. The provider receives ordinary browser request information and the details you enter there under its own privacy practices, manages availability, and sends its configured confirmation and invitation. The page does not prefill those attendee details or read them from the frame. It treats a Calendly booking as made only after a completion message from the current configured iframe; Google Calendar shows its confirmation inside the frame and the page records nothing. Separately, when booked-call measurement is enabled, rouse reads confirmed bookings from its own booking calendar as described under Advertising measurement. Merely opening a calendar does not confirm a meeting. Profile-only links, short links, URL-prefilled contact details and other scheduler hosts are rejected.
When you apply for a role
The careers pages do not upload or store applications. Each role asks you to email the requested information and an attached résumé or CV to info@rouse.io using your chosen email provider. The role-specific button may prefill the role title and approved questions in your mail app, but you decide what to include and nothing is submitted merely by opening it.
Rouse uses application emails only to consider candidates for Rouse roles and does not add applicants to marketing lists or attach their messages to assistant conversations, reports or workspace data. Email providers process and retain the message and attachments under their own services. To ask about or request deletion of an application email, contact info@rouse.io.
When you request a report
Starting an audit saves your company or website and request time in the configured rouse data store. If you request email delivery, it also saves your email, delivery consent and optional follow-up preference. Report emails are kept in a private contact directory, with each report request and its consent record linked to the address. When available, the report form offers separate, optional choices for report reminders and Tuesday informational notes. Each choice records the wording agreed to and when it was given. Requesting the report alone does not subscribe you to either program. A worker reads the public website and its crawl instructions. When the research service is configured, company context and buyer questions are sent to the selected research provider to research public sources, record answers and find relevant Reddit discussions. Your email and private report token are not included in those prompts. The report stores the collected evidence, research activity, delivery timing and a PDF snapshot; the team can add separately labeled, dated observations.
So you can check a few websites in one sitting, the homepage keeps your three most recent report links in your own browser and shows the company each was for. That list stays on the device you used, is never sent to rouse or any other service, and is not linked to an account. Anyone using the same browser profile can open those reports from it, so avoid it on a shared computer and use Forget on a row, or clear your browser storage, to remove one. Removing a row does not delete the report itself; use the deletion control on the report for that.
A private report link gives access to that report, its PDF, call-request controls and deletion. Treat that link as private. An authorized team review workspace can access report requests and email drafts. A connected shared workspace is not a tenant-isolated customer account system.
Email is sent only when an operator explicitly configures the mail service; otherwise drafts remain in the team review outbox. Choosing a service saves that preference with your request, then opens a service inquiry. rouse does not collect bank or card details on this page. Report requests made from October 2, 2026 also receive three report reminders, scheduled at 24 and 96 hours and then day 7 after the report is ready and its delivery is accepted, followed by our Tuesday notes; no separate choice is shown, and every email has an unsubscribe link. From October 12, 2026 these reminders are short notes from our founder, sent from info@rouse.io. If no booking, reply, call request or service request has been recorded by about ten days after the report, one further note invites you to QuietKarma (quietkarma.ai), a separate self-serve platform led by our founder, and one check-in about four days later asks whether you had a chance to look. rouse sends both itself: your email address and report are not shared with QuietKarma, and the link carries no tracking. Reminders, the invitation and its check-in stop when you opt out, request a call, select a service, or a reply or booking is recorded. Opening the scheduler alone does not confirm a booking. A read-only connection to our booking calendar matches attendee email addresses to existing contacts; event titles and descriptions are not stored. Customer domains are excluded from reminders, the invitation, its check-in and Tuesday notes. Earlier requests keep the email choices made at the time, except that the QuietKarma invitation and check-in go to anyone still receiving report reminders, and older two-reminder permissions retain their original scope. Report links include an opt-out page. Opting out stops optional report reminders, the QuietKarma invitation and check-in, and future marketing to that address; it does not remove access to your report. Apart from that invitation and its check-in, reminder consent is never treated as consent to marketing campaigns.
Proposals, agreements, and test invoices
rouse stores the completed demo time, published proposal, and a reference to the agreement executed through your signing process. Staff record the signer, signing time, agreement link, billing email, and purchase order where supplied. Signed pricing is preserved as a fixed snapshot. The private customer page shows the agreement reference and its proposal version; staff have access to the agreement details.
In Stripe test mode, rouse sends the company name, billing email, agreement reference, purchase order, and invoice amounts to Stripe. Bank authorization and payment details are entered on Stripe’s hosted invoice. rouse stores the Stripe customer and invoice references, hosted invoice link, amounts, verified payment status, and payment references. Research and private access tokens are not sent to Stripe. Test payments use sandbox funds, and Stripe does not email test invoices. A confirmed test payment opens the onboarding form, which stores your approval contact, website, priorities, Slack setup preference, and any workspace address or additional teammate emails you provide. These details are available through your private customer page and the team review area so the team can coordinate channel access and kickoff. Saving onboarding does not send these details to Slack or create invitations.
When you request a demo or proposal
rouse stores your company, contact details, requested scope, budget preference, and permission to contact you about the proposal. Your brief is reviewed by the team; it does not start research or enroll you in marketing follow-ups. If you arrive from a private visibility report, that report can be linked after its access token is verified. Each service request uses its own private access link. Proposal drafts remain in the team review area until the team publishes pricing, deliverables, coverage, and terms to your private page.
An agreement request records the proposal version you reviewed. It is nonbinding. Signing takes place through the agreed external process; staff record the executed agreement before issuing an invoice. Team members can copy the private proposal link for a manual handoff; this workflow does not automatically send email. Before signing, delete the request from its private page to remove the brief, contact details, and proposal. Signed agreements, invoices, and onboarding records are retained for billing reconciliation and cannot be removed through this control. A linked report is stored and deleted separately. A non-identifying daily intake count remains.
Your controls
Use Settings to export the workspace or reset it to the fictional example. Clearing browser site data removes browser-saved changes and any tab recovery copy. It does not remove records from a connected workspace. Use the Settings reset action to replace connected workspace data with the fictional example, and wait for the saved confirmation before closing.
Use “Delete this request” on your private report to remove its contact details, report, and unsent email records. If another report uses the same email, its separate request and consent record remain. Deleting the final report for an address also removes its saved contact-directory entry. A hashed address may remain to honor an opt-out. Workspace reset does not delete report requests. Deletion cannot recall emails already accepted by a mail service. A non-identifying daily request count remains to enforce collection limits.
Contact and future services
For questions about this page or rouse’s handling of information, email info@rouse.io.
Source links open external websites, which have their own privacy practices. The example workspace does not connect to your Reddit account or accept payments. The independent audit can query its configured AI research provider; report delivery and explicitly enabled contact alerts use the configured mail service. rouse will not enable live commercial Reddit Data API use until Reddit approves the intended use and the required retention, removal, and downstream-processing controls are implemented.
This page describes the current rouse website and example workspace.