workadventu.re
Every change Venpo has recorded in workadventu.re's public terms, privacy policies and subprocessor lists – each one linked to the document version it came from.
Change activity
Recorded changes per month, last 24 months
What changed, and what it meant
Each entry is a diff between two stored versions of a document, marked by whether it weakened, improved or left the customer position unchanged.
workadventu.re Subprocessors
Parties workadventu.re declares in its own subprocessor list and DPA annexes. Nothing here is inferred from traffic or page scripts.
| Subprocessor | Stated purpose |
|---|---|
|
|
We use Pipedrive as our Customer Relationship Management. Pipedrive is GDPR compliant. |
|
|
We use Mailjet as our email processing service. Mailjet is GDPR compliant. |
|
|
We use Google Tag Manager in our website. This service allows website tags to be managed via an interface. The Google Tag Manager only implements tags. No cookies are installed and no personal information is collected. The Google Tag Manager triggers other tags that may collect data. The Google Tag Manager does not access this data. If a deactivation has been made at the domain or cookie level, it remains valid for all tracking tags if they are implemented with Google Tag Manager. |
|
|
We use Sirdata as our Consent Management Platform. Sirdata is GDPR compliant. It allows users to opt-in or out of data collection via cookie consent. |
|
|
We use Google Ads as a marketing tool to promote our products and services. |
|
|
We use Facebook Ads as a marketing tool to promote our products and services. |
|
|
We use LinkedIn Ads as a marketing tool to promote our products and services. |
|
|
We redirect users to our YouTube channel for tutorials and product promotions’ purposes. |
|
|
We use Stripe to process one-time and recurring payments. |
|
|
The OVH data center hosts the WorkAdventure Platform, Website (this website), the meeting rooms (Jitsi) and all the data we gather for regular business operation (user accounts, list of members, analytics, etc…) |
|
|
The Amazon Web Services data center hosts the TURN servers. No data is stored in the AWS data center. Data is only processed “in-transit” |
|
|
We use Sentry for error tracking, crash reporting, and application monitoring. Sentry acts as a data processor, with a GDPR-compliant Data Processing Addendum (DPA) and the option to host data within the European Union. In addition, Sentry is self-certified under the EU-US Data Privacy Framework, ensuring compliant international data transfers. |
Explore the next levels
See how workadventu.re's declared subprocessors connect, level by level.
The documents behind the timeline
Venpo re-reads each of these on a schedule and keeps every version. When one moves, it becomes an entry in the timeline above.
FAQs
Where does this come from?
workadventu.re's own published pages: privacy policies, terms, DPA annexes and the subprocessor list. Nothing on this page is inferred from network traffic or page scripts, and nothing is supplied by workadventu.re directly.
How often are the documents read?
Every monitored document is re-read on a schedule, and each fetch is stored as a dated version. The page as it existed on any given date is retained, so a change can always be traced back to the two versions it sits between.
What counts as a change?
A difference between two stored versions that alters meaning. Reformatting, reordering and typographic fixes are recorded but not surfaced as entries in the timeline.
What do the three counts on each row mean?
They are the clauses that weakened the customer position, the clauses that improved it, and the ones that changed without shifting it either way – read off the redline for that version.
Can I be told when something changes?
Yes. Tracking a vendor sends the redline the day a document moves, along with a plain-language summary of what it changed. The first vendor is free.
Is Venpo affiliated with workadventu.re?
No. Venpo reads publicly published documents and records what changed in them. workadventu.re is not involved in producing this page.