zeplin.io
Every change Venpo has recorded in zeplin.io'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.
zeplin.io Subprocessors
Parties zeplin.io declares in its own subprocessor list and DPA annexes. Nothing here is inferred from traffic or page scripts.
| Subprocessor | Stated purpose |
|---|---|
|
|
Zeplin uses LogDNA for logging and operational activity message aggregation. Log records may contain user information. |
|
|
Zeplin uses Twitter cookies to collect user information to engage in marketing efforts. |
|
|
Zeplin uses TikTok cookies to collect user information to engage in marketing efforts. |
|
|
Zeplin uses Stripe to collect and process credit card transactions and process purchase orders. |
|
|
Snowflake, Inc. is a Cloud data warehouse. Zeplin may store user data in Snowflake. |
|
|
Zeplin uses Sentry for logging and operational activity message aggregation. Log records may contain user information. |
|
|
Zeplin uses Salesforce.com for CRM and may store and process user contact information. |
|
|
Zeplin uses Reddit cookies to collect user information to engage in marketing efforts. |
|
|
Zeplin uses Pusher to enable real-time communications between the Zeplin servers and the client App or webapp. User information may pass through Pusher services.Pusher process Zeplin data through US-based datacenters only. |
|
|
Zeplin uses Profitwell for billing, sales and marketing data visualization. Zeplin may provide user financial transactional information. |
|
|
Zeplin uses Postmark to provide email services, for transactional emails and for service notifications. Postmark infrastructure processes some Zeplin email traffic and provides some email security services. |
|
|
Zeplin uses NewRelic for logging and operational activity message aggregation. Log records may contain user information. |
Explore the next levels
See how zeplin.io'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?
zeplin.io'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 zeplin.io 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 zeplin.io?
No. Venpo reads publicly published documents and records what changed in them. zeplin.io is not involved in producing this page.