Portability Pledge – A first draft for TheStartupBus
The Startup Bus to SXSW Interactive 2010 is now rolling south by southeast. "12 strangers will board a bus in San Francisco. At 60 miles an hour and over 48 hours, they will conceive, build and launch 3 tech startups in time for a SXSW party in Austin." Can you bootstrap a company and squeeze in a decent portability policy? The Bus startups will try. The DataPortability Project wants to make your site's portability policy an impulse buy but your company lawyers and designers will want more time.
My proposal:
The Portability Pledge.
Four steps:
- Take the Portability Policy Pledge
- Draft your portability policy
- Set up a customer conversation channel
- Post your Portability Policy Pledge on your site
1. Write Your Portability Policy Pledge
This is your promise to have a signed-off portability policy posted by a deadline. Model language:
- On behalf of THIS ORGANIZATION operating THIS SITE we promise to post a complete Portability Policy on this page by 1 July 2010. We will be terribly embarrassed if we don't.
- Like a Privacy Policy, our Portability Policy will explain your rights, in this case your rights to access, share, synchronize, delete and backup your data with our services.
- We'll also explain our responsibilities and how to work with us to improve your portability experience.
- We're working with DataPortability.org to create a useful policy. Learn more HERE.
- We believe we can do more for you by responsibly sharing your data with services you trust.
- We support these Portability Principles:
- It should be easy to bring your identity, friends, files and history with you to our site.
- It should be just as easy to share them from our site with other sites.
- We should make it easy to keep your information fresh with updates.
- We will be considerate with your data when our relationship ends.
- We will be explicit and transparent about our portability practices.
- If you'd like to discuss your portability rights with us, join us in this forum HERE.
2. Draft your portability policy.
Your policy will/should go through lawyers. It's part of you site's Terms of Service, End User License Agreement, or whatever contract connects you with your site's users.
This draft is what you'll give your lawyer.
The parts:
- 2.A. Welcome to our portability policy.
- 2.B. Our disclosures
- 2.C. How to talk with us about this
- 2.D. Cautions and other limits
2.A. Welcome to our portability policy.
This document is...
You'll explain what this document is, what it is called.
We're writing it so...
Say the purpose, what's inside, what's not inside.
We hope you get out of it...
Takeaways and benefits for users who read this and when to come back and read it in more depth.
2.B. Our disclosures
This is the body of your portability policy. You'll answer questions, grouped into five categories (Start, Sync, Access, Share, End). While the questions can be answered briefly with yes/no and multiple choice answers, it may take more time to provide the optional descriptions that explain your answers.
See the the full questionnaire and guide below.
2.C. How to talk with us about this
Learn more about data portability here...
Contact our ombudsman here...
Contact our portability alliance manager here...
Discuss with our other customers here...
2.D. Cautions and other limits
Subject to change...
Not my fault...
We only control ourselves...
We're not perfect...
3. Start Your Customer Conversation
You'll want a place to let customers ask data portability policy questions, for you to make announcements, conduct surveys, etc. Something like GetSatisfaction or UserVoice. You'll link here from your portability policy page.
4. Post Your Pledge
- The default file name: portabilitypolicy.html
- Popular locations: Root. Acme.com/portabilitypolicy.html
- Link to your portability policy on every page where you link to your privacy policy. "Portability" or "Portability Policy".
- We'll have a form for you to list your policy on the dataportability.org site.
There you go: four simple steps to a Portability Pledge.
You'll deliver on your promise when you answer and post your the Portability Policy Questionnaire.
The Portability Policy Questionnaire:
Start.
How well do you welcome me, my history, my friends?
1. Are your import and export APIs and formats documented?
- Yes
- No
- Suggested: If Yes,where are they documented?
- New Identity - The person is expected to create a fresh identity that is used on this site. This site does not trust a third party to authenticate identity.
- Existing Identity - The person can register an account that is accessed using an identity authenticated by some third party. This product assumes that, by selecting a third party to authenticate their identity, the person accepts that third party as trustworthy.
- Suggested: If Existing Identity, what identity services will you support?
Sync.
How do you keep my data fresh?
3. Must people import things into this product, or can the product refer to things stored someplace else? Can this product work with objects and information whose "authoritative home" is another product, or can this product only work with things that it hosts directly?
- Must Host - In order for this product to work with a thing, it must be hosted directly.
- Can Refer - This product has the ability to access and work with things that are hosted by third parties, assuming that the third party allows this.
- Suggested: If Can Refer, what items can be stored elsewhere and under what conditions?
4. Can this site accept updates that users make on other sites? In cases where the product tracks or manages things that the person has stored on some third party product, can this product watch the third party for updates?
- One Time Import - This product only sees the remote thing at import time, and does not watch for changes.
- Watch For Updates - This product watches the third party for changes, and updates its own view of the remote thing to match.
- Suggested: If Yes, what types of items and under what conditions?

Access.
How well do you help me use and manage my information?
5. Can the person allow other sites to use the things they've created or updated here? Does this product provide a way for third parties to authenticate a person and read or write?
- No Access - The person must use this product to read or access whatever it manages.
- Third Parties Can Read - The person can provide the third party with authentication credentials, and can read data managed by this product.
- Third Parties Can Write - The person can provide the third party with authentication credentials, and can write data managed by this product.
- Suggested: If Yes, what technical protocols are supported and how can users manage the authority they give other sites?
6. Can the person download or remotely access a copy of everything they've provided to this service? As part of their standard use of most products, people import or create things. Does this product provide an open, DRM-free way for people to retrieve or access via third party all of the things they've created or provided?
- No Access - This product does not offer the person the ability to download the things they've provided.
- Remote Access - The product provides an open, DRM-free way for people to download all of the things they've provided to the product, or remotely access it using a third party product.
- Suggested: If Yes, how and in what forms?
7. Do you disclose where my data is being kept in the real world?
- Yes
- No
- Suggested: If Yes, where can I learn where my data is kept?
8. Can I control where my data is kept in the real world?
- Yes
- No
- Suggested: If Yes, how can I exercise those controls?
Share.
How well do you help me share well with others?
9. If a person updates something here, is that change stored only by this product or can the person ask this product to store it elsewhere? Can this product accept some other site as being the authoritative home of a thing it knows about?
- Must Be Authoritative - This product assumes that it is the authoritative home of all things it manages, and does not update third parties.
- Can Update Remote - This product can work with a third party that is assumed to be authoritative. All updates made by the person using this product are also forwarded to the third party.
- Suggested: If Yes, how does it work in practice?
10. Can the person download or remotely access information that others have provided to the product? In cases where the product allows download or remote access, can the person export or access all of the data to which they have access, or only data which they have directly created?
- Provider Only - This person may only export or access data which they have directly provided.
- Full Access - The person may export or download any data to which they have access on this product, subject to reasonable usage and abuse rules.
- Suggested: If Yes, how and in what forms and with what other services or protocols?
End.
How well do you support a graceful exit from our relationship?
11. Will this site delete an account and all associated data upon a user's request? If the user creates a password or account for use with this product, does the product provide a way to cancel the account and erase all data associated with it?
- Immortal Accounts - Accounts or passwords, once created, are assumed to live for as long as the product is available. Desktop applications and other stand-alone products that do not have host services may have no way to remotely revoke accounts or passwords.
- Data Expires - If this product acts as a hub, the data it copies from other sites will expire in a set amount of time. This product must be linked to a place where it can refresh or synchronize data in order to stay current.
- Accounts Deleted Upon Request - This product has the ability to remove a person's account and all relevant data, and will do so when requested by the person or third party with appropriate legal standing.
- Suggested: If Yes, where can I find the procedure to request deletion.
12. Do you give notice before terminating the account?
- Yes
- No
- Suggested: If Yes, how much notice do you give and in what forms?
13. Can you recover a terminated account?
- Yes
- No
- Suggested: If Yes, how thoroughly, under what conditions, how quickly, and how is recovery triggered?
14. Do you have a posted appeals process or dispute resolution procedure?
- Yes
- No
- Suggested: If Yes, where are the procedures posted?
###
As you fill this out:
- Would you have designed your service differently if you read the Portability Pledge beforehand?
- Do you really need the pledge or are you ready to write a full portability policy before Austin?
tags: dataportabilityproject, dpp, portabilitypolicy, portabilitypledge, pledge, policy, sxsw, sxswi, roadtrip, promise
Call me at +1-510-316-9773, Skype me, follow @skypejournal and @Phil Wolff.
Visit our Skype Journal private technologist roundtable, one of the longest running public Skype chats.
Labels: dataportability, events, usa


























Join the Skype 5.X Text Chat Room