Riser Draft legal

Riser Draft Privacy Policy

Effective October 16, 2026Last updated November 15, 2026See also the Terms of Service

Contents

1. Who we are and what this policy covers

1.1 Riser Draft is run by Standing Rock Media LLC, doing business as Riser Draft ("we", "us"). Contact: support@riserdraft.com. Based in Kent, Ohio. Mailing address: PO Box 24, Kent, OH 44240.

1.2 This policy covers the Riser Draft web app at app.riserdraft.com, the website riserdraft.com, and email with us. The app's old address now only redirects to app.riserdraft.com.

1.3 Two kinds of information. Riser Draft is a business tool used by teams.

  • Account, billing and website information, such as your name, your email address and how you sign in. We decide how this is used, as described here.
  • Your team's work, such as designs, quotes, price lists, documents, Design Queue and Services records. We hold this on behalf of your team, and use it only to provide the Service to that team, as our Terms of Service say. Your team's admins decide who on the team can see it. If you have a question about your team's work, start with your team's admin.

2. What we collect

2.1 From your sign-in

You sign in with Google, with Microsoft, or with a sign-in link we email to you.

When you sign in with Google, Google tells us:

  • your name and email address, and that Google has verified the email address,
  • the link to your Google profile picture. The picture stays on Google's servers, and your browser loads it from there,
  • a Google account ID, so we know it is you next time,
  • whether your email address is one Google itself hosts or manages for your company.

When you sign in with Microsoft, with a work, school or personal Microsoft account, Microsoft tells us:

  • your name, your email address and your Microsoft username,
  • whether the organization that runs the account has verified that the email address is one of its own, and whether you sign in to it as a guest from elsewhere,
  • a Microsoft account ID and the ID of that organization (for a personal account, Microsoft's own), so we know it is you next time.

We ask Microsoft only to sign you in. We do not ask for access to your mail, files, calendar, contacts or any other Microsoft data, and we receive no picture. The first time you sign in with Microsoft, if Microsoft does not confirm your email address, we email that address a sign-in link and code, as below, and that first sign-in finishes only when you use one in the same browser. Until then we hold your Microsoft account ID, email address and name on our server for up to 30 minutes, then forget them. If your email address changes at Microsoft later, we use the new one only once Microsoft confirms it.

Your Microsoft account becomes another way into a Riser Draft account that already signs in with the same email address only when both sign-ins vouch for that address: Microsoft for yours (an address of the organization that runs your work or school account, or a Microsoft address such as outlook.com for a personal account), and that account's own sign-in, used in the last 30 days. If we confirmed your address by email instead, only an account that signs in with emailed links to that address, used in the last 30 days, qualifies. Otherwise your Microsoft account is a separate Riser Draft account.

When you sign in with an emailed link, you type your email address and we email it a link and a code. You can use either one, once, within 15 minutes, and using it shows us you can read that mailbox. We receive nothing else about you from the email itself. The first time you sign in this way, we ask your name, and we keep the name you give with your account, where your teammates see it. For each sign-in email we keep the address it went to, when it was asked for, whether and how it was used, and how many wrong codes were tried, so we can limit how many go to one address and stop abuse. We keep this for 48 hours, then delete it, whether or not the address has an account. We keep the link and the code, and the browser cookie and any invitation link they came with, only in a scrambled form that cannot be used to sign in. When a wrong code is typed, we also keep when it was typed, with the address only in a scrambled form, for 7 days, so we can stop codes for an address that gets too many wrong ones.

We also record when your account was made, when you last signed in, and when you last used the app. We never receive or store a password. If we add another way to sign in, we will update this policy before it starts.

2.2 About your team

  • The team's name and the kind of business it says it is, such as an integrator or a rep firm.
  • Who is on the team, their role (admin or member), their seat, when and by whom they were added or removed, and when each person started or stopped holding a Designer seat and who made the change.
  • Invitations: the email address invited, the role and seat offered, who sent it and when. We keep only a scrambled (hashed) copy of the secret code in the invitation link.
  • The team's letterhead lines, logo, proposal terms, estimate settings, price columns, design number prefix, hidden manufacturers, and the answers it gave about manufacturer names when it imported a price list.
  • Billing details for the team (section 2.6).

2.3 Your team's work

  • Designs: Signal Flow drawings, rack elevations, quotes, their names, Design #s and Opp #s, who made each design and who it is shared with.
  • Documents: PDFs and pictures attached to a design, such as site photos or plots. A PDF is kept as uploaded. A picture is rebuilt from its image data, which removes a photo's GPS position and camera details.
  • Quote revisions: each version of a quote that was exported, with its lines, the prices shown at the time, a list of what was in the drawing, which documents and sheets went with it, the name of the person who made it, and any revision name or note.
  • Price lists and items: the prices your team loads, such as list, dealer and distribution prices, with their dates, and the items, symbols, rack kit links and spec sheet links your team adds. When you import a price list file, the server reads it and holds a preview in memory for up to 30 minutes so you can review it. It then saves only the resulting prices. The file itself is not kept.
  • Export log: each export's quote name, file type, number of items, total and lines with the prices shown, whether it was MSRP only, who exported it and when. Your team's Reporting uses this.
  • Model requests: the manufacturer, model, link and note you send when you ask us to add a model, and your name.
  • Design Queue, for teams that use it: job and customer names, salesperson and designer names (some of whom may not have Riser Draft accounts), notes, questions and answers, links to files and messages, the names of people a request is waiting on, deadlines, time entries, the history of each request, and the email addresses the team chooses for its notices and morning summary.
  • Services, for teams that use it: jobs, customers, scope lines, quoted and actual hours and amounts, purchase order and accounting references, and the names and email addresses of technicians the team adds, who may not have Riser Draft accounts.
  • Your choices in the app, such as models you asked the rack kit prompt never to offer again.

Your designs and notes may include information about your own customers, such as a client or site name. You choose what to type in, and you are responsible for having the right to share it with us.

2.4 Feedback and support

  • When you send feedback from the app's Help menu, the app saves it and emails a copy to us at support@riserdraft.com. With your message it keeps your name and email address, your team's name, your browser name and version and its full description of itself, your screen and window size, which tab you were on and the app's version. It includes the name of the design you had open only if you tick the box to include it. We may email you back about it.
  • When you email us, we keep the conversation.
  • If your team lets Riser Draft support in, we keep a log of what support did in your team: when, what kind of action, and on which item. It is kept for 180 days, and your team's admins can read it.

2.5 Error reports

When something goes wrong in the app, it sends us an error report so we can fix it. Before a report is saved, the app and the server both clean it. They remove email addresses, ID numbers, long numbers, phone numbers, codes that look like keys or tokens, the query part of web addresses, and any text in quotation marks, which is where the app puts names of designs and searches. What is left is a short error message, a list of the code locations involved, the tab you were on and the app version. The server adds your account ID and team ID so we can count how many people an error affects. For each kind of error we keep the latest report and a count. At most once a day, a short summary of new errors is emailed to our support mailbox. A message could still contain a word you typed, which is why only our staff see these reports.

2.6 Billing

Subscriptions are sold through Link, a Stripe service that is the merchant of record for each payment, and Stripe processes the payments. Link works out and collects sales tax. Link and Stripe hold the team's billing email, name and billing address. We store the team's Stripe customer and subscription IDs, its plan (founding or standard), its number of paid seats, its subscription status, the date its current period ends, when a cancellation takes effect, when it first paid and when its founding price ends, and a log of the IDs in the billing events Stripe sends us. We also record which version of the Terms of Service each person agreed to and when, and which version an admin agreed to when paying. Link and Stripe collect and store card details and the billing address needed for tax, and use the payment information they collect under their own privacy policies. We never receive your full card number.

2.7 Server logs

  • Our app server writes one line for each request to the app: the time, the type of request, the address within the app (never the search text or other query details), the result, how long it took, your account ID and the team ID. It never logs cookies, sign-in tokens or the content you send. It also logs problems, for example an email that could not be sent, with that email's address and subject.
  • Our web server keeps a standard access log for the app and the website: your IP address, the time, the full address requested, which can include words typed into a search box, the page that linked to it and your browser's description of itself.
  • To stop abuse, the app counts recent requests by IP address and by account. Those counts are kept in memory only, for a short time, and are not saved.
  • Sign-in sessions do not record your IP address or browser.

2.8 Cookies and browser storage

  • Four cookies. The app sets one sign-in cookie, __Host-sid, that keeps you signed in for up to 30 days. When you ask for a sign-in email, it also sets __Host-rd-signin, so the email's code works only in the browser that asked for it. That one lasts 48 hours from your last sign-in email, or until you sign in with an emailed link or code in that browser. When you sign in with Microsoft, it sets __Host-rd-microsoft, so Microsoft's answer counts only in the browser that asked for it. That one lasts 10 minutes, or up to 30 while we wait for you to use an emailed code, and is removed once you are signed in. Each holds a random code, not your details. Scripts on the page cannot read them, and they are only sent over a secure connection. The app needs them to sign you in, so there is no option to turn them off. Google's sign-in code, which runs on the sign-in page, sets a fourth cookie on app.riserdraft.com, g_state, as soon as the Sign in with Google button loads. It remembers the state of Google's sign-in prompt for up to about 6 months and holds no account details.
  • No trackers. The app has no advertising cookies, analytics tools, tracking pixels or social media plug-ins.
  • Google sign-in. On the sign-in page, Google's sign-in code runs. Besides the g_state cookie above, Google may set its own cookies on Google's own sites. Google's privacy policy covers that.
  • Microsoft sign-in. Sign in with Microsoft takes you to Microsoft's own sign-in page and back. No Microsoft code runs in the app. Microsoft may set its own cookies on its own sites. Microsoft's privacy statement covers that.
  • Browser storage. The app stores some things only in your own web browser:
    • your layout, display and export preferences, such as the MSRP only tick,
    • where you were in the app, in that tab only,
    • an invitation link you opened, in that tab only, until you use it,
    • the address you asked a sign-in email for, in that tab only, while you wait for the email. It is removed when you sign in, and not used after 15 minutes,
    • symbols you placed recently, and when you last used the app,
    • a working copy of the design you have open, removed when you sign out,
    • a copy of any changes that could not be saved, so you can get your work back. It is deleted when the changes save. The app removes copies older than 30 days the next time it is opened in that browser. When you sign out, you choose whether to keep your unsaved changes for next time. Changes you chose to keep stay until you next sign in there, or until you clear your browser's storage.

    These copies can include your team's prices. We cannot see what is in your browser's storage.

  • Do Not Track. We do not track you across other websites, so the app works the same way whether or not your browser sends a Do Not Track or Global Privacy Control signal. Apart from Google's sign-in code, no outside company's code runs in the app, and we do not let advertising or analytics companies collect information about you through it.

2.9 The riserdraft.com website

  • The website has no sign-in of its own (its Sign in link opens the app). It sets no cookies unless you accept analytics cookies.
  • It loads its fonts from Google Fonts, so Google receives your IP address and browser details when you visit.
  • Google Analytics (optional). If you accept analytics cookies, the website runs Google Analytics so we can count visits and see which pages help people. Google then receives the pages you view, the page you came from, your browser, device type, screen size, language and approximate location (worked out from your IP address, which Google Analytics does not keep), and sets two cookies, _ga and _ga_<ID>, which tell a return visit from a new one and last up to 13 months. We have turned off Google's advertising features, Google signals and sharing this data with Google for its own products, and we never send Google your name, email address or anything from the app. A notice at the top of the page asks first (Accept or Decline); if you decline, or your browser sends Global Privacy Control or Do Not Track, Google Analytics does not load.
  • How your choice is kept. Your browser keeps your choice on your own device, in its local storage under the name rd-consent: which kinds you allowed (analytics, marketing) and when you chose. It holds no name or ID and is never sent to us. After 12 months you are asked again. Apart from Google Analytics' cookies when you accept them, this is the only thing the website stores in your browser. If your browser blocks site storage, nothing is stored and nothing optional runs.
  • Changing your mind. Use Cookie settings at the bottom of any page to accept or decline at any time, for analytics and marketing separately. If you decline after accepting, the website removes what the optional tools stored for riserdraft.com in your browser, where your browser allows it, and, if they were running, reloads the page without them. You can also clear your choice in your browser's settings.
  • Global Privacy Control and Do Not Track. If your browser sends a Global Privacy Control or Do Not Track signal, the website treats it as Decline for everything optional, whatever was chosen before, so the notice does not ask, and Cookie settings says so. While the signal is on, nothing optional can be turned on in Cookie settings.
  • Our web server keeps an access log, as in section 2.7.
  • Until the public beta opened on November 15, 2026, you could join the waitlist by giving your email address in the form at the bottom of the home page. That address was all the form collected. Our app server passed it to EmailOctopus, the email service that keeps our waitlist (section 4.3), and keeps no copy of it, not even in its logs. We use it only for the emails the form promised: if you joined before November 15, a heads-up before the beta opened and the opening itself with your founder link; and one before the founder price closes on December 31. Each has an unsubscribe link. When you open one of these emails or click a link in it, EmailOctopus records that and when, and receives your IP address and device details. If you emailed us to join instead, we added you the same way, and your email also stays in our support mailbox, like any other support email (section 6).

2.10 Our email lists

We keep two email lists with EmailOctopus, the email service in section 4.3:

  • Notices: everyone with an account. We use it only for notices about the Service: release notes, updates and changes, downtime and scheduled maintenance.
  • Newsletter: everyone who had an account when this section took effect, on November 13, 2026, except those who asked us not to add them. After that, we add only people who ask for it, when they sign up or later on the Account page. We keep your choice with your account, and when and how it was made.

We send EmailOctopus your email address and first name, and whether you are a team admin, which seat you hold, and whether your team is complimentary. We send nothing else: not your team's name, its designs or its prices. We keep these details up to date, and take you off both lists when your account is deleted. When you open one of these emails or click a link in it, EmailOctopus records that and when, and receives your IP address and device details. Each email has an unsubscribe link, and you can leave either list at any time (section 8.6).

3. How we use information

We use the information above to:

  • Provide the Service: sign you in, save and show your team's work, make exports and downloads, and run Reporting, the Design Queue and Services.
  • Run teams: send invitations and team notices, such as when support is let in, send the notices and summaries your team sets up, and show teammates who made or exported what.
  • Bill: set up and charge subscriptions, and send receipts and billing notices.
  • Support you: answer questions and feedback, add models you request, and, when your team lets us in, look at the problem you asked about.
  • Keep it safe and working: prevent abuse, find and fix errors, make backups and plan capacity.
  • Improve the Service: understand which features are used and what goes wrong. We do this from usage records, counts and error reports, not by reading your designs or prices.
  • Talk to you: send service, security, billing and policy notices. We send marketing email, such as waitlist updates, only to people who asked for it, and our newsletter as section 2.10 says. You can unsubscribe at any time.
  • Meet legal duties: keep business and tax records, carry out deletion requests, and respond to lawful requests.

We do not sell personal information, use it for targeted advertising, or share it with anyone for their own marketing. We do not use your team's designs, prices or other work to train AI models, and our AI provider's account is set so that it does not either (section 4.3).

4. Who can see your information

4.1 Your team

  • Teammates can see your name and email address.
  • Your team's admins can see who is on the team, each person's role and seat, pending invitations, and the support log.
  • Reporting shows who exported each quote and when. Quote revisions show who made them. Designs show who owns them and who they are shared with.
  • In the Design Queue and Services, the people your team sets up can see the requests, jobs, notes and time entries the module's rules allow. A salesperson sees only their own requests.

4.2 Riser Draft staff

  • To run the platform, our staff can see each team's name, status, seats, number of members, its admins' names and email addresses, who set the team up, when the team was last active, and the dates of its Designer seat changes in the last 30 days, with people shown by number, not name.
  • We see feedback, support email, model requests, error reports, deletion requests and our email lists (section 2.10). When a new team is set up, we get an email with the team's name and the name and email address of the person who set it up.
  • We see how often each library symbol is placed, as numbers only, never which team or design.
  • We do not see your team's designs, quotes, prices, letterhead, documents, Design Queue or Services jobs through the app unless your team lets Riser Draft support in (section 2.4, and the Terms of Service on support access).
  • The people who run our servers can technically reach the database. They do so only to keep the Service running, fix faults, make and restore backups, carry out something your team asked us to do, or when the law requires it.
  • We use an AI assistant, Claude, made by Anthropic, to help us build, run and support the Service. While it does that work under our direction, it may see anything described in this policy, including your team's work, support email and feedback. Our Anthropic account is set so that Anthropic does not use this data to train its AI models.

4.3 Our service providers

We share information with these companies only so they can provide their service to us, under their terms and data protection commitments:

ProviderWhat they do for usWhat they receive
DigitalOceanHosts the app, the website, the database and its backups, in data centers in the United States. The server we used before October 20, 2026 now only redirects the app's old address to app.riserdraft.com. The data still on it, and in its backups, will be deleted by January 18, 2027Everything stored in the Service
GoogleSign in with Google. Fonts on riserdraft.com. Google Analytics on riserdraft.com, only if you accept analytics cookiesSign-in details; website visitors' IP addresses; if you accept, the visit details in section 2.9
MicrosoftSign in with Microsoft. Microsoft 365 sends the app's email from no-reply@riserdraft.com and hosts our support mailbox, support@riserdraft.comSign-in details; the address and content of each email the app sends; feedback, support email, model-request and error summaries, and deletion receipts
EmailOctopusKeeps our waitlist and our notices and newsletter lists, and sends their emails, from data centers in the European Union (mainly Ireland)The email address you give to join the waitlist; for the notices and newsletter lists, the details in section 2.10; and, when you open or click one of these emails, when you did, your IP address and device details
StripeSells our subscriptions through Link, its service that is the merchant of record; takes payments, manages subscriptions, and works out and collects sales taxBilling contact, team name, seats, billing address, payment details, our account and team IDs, and the Terms version agreed to
AnthropicClaude, the AI assistant we use to help build, run and support the Service. Our account is set so that Anthropic does not train its models on what Claude seesWhatever Claude sees while working for us, which may include anything stored in the Service, support email and feedback
NotionOur planning notesIdeas from feedback and model requests, which may name the person who suggested them

Let's Encrypt issues the security certificates for our websites. It does not receive your personal information.

4.4 Other cases

  • The law. We may disclose information if we believe in good faith that the law requires it, for example to answer a valid subpoena or court order, or to protect someone's safety. If we are asked for your team's work, we will tell your team first unless the law forbids it.
  • A change of ownership. If Standing Rock Media LLC or the Service is sold, merged or reorganized, information may pass to the new owner, who must keep honoring this policy for the information it receives. We will tell you before that happens.
  • With your permission. For example, when you share a design with a teammate, or ask us to send something to someone.

5. Google user data

5.1 Riser Draft uses Sign in with Google only to sign you in. From Google we receive the information in section 2.1: your name, email address, profile picture link and Google account ID. We do not ask for access to your Gmail, Google Drive, Calendar, contacts or any other Google data.

5.2 We use this information only to sign you in, to show your name and picture to your teammates, to send you email about Riser Draft, and to keep your account secure. We do not sell it, use it for advertising, or use it to train AI models. We share it only as section 4 describes.

5.3 Riser Draft's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

5.4 You can remove Riser Draft's access from your Google account settings at any time. To delete the information we hold, see section 8.4.

6. How long we keep information

We keep information only as long as we need it for the reasons in section 3. These are our retention periods:

InformationHow long we keep it
Your account: name, email address, sign-in IDs, profile picture link, newsletter choiceWhile you have an account. Deleted within 45 days of a deletion request, except as section 8.4 says
Sign-in sessionsUp to 30 days. Expired sessions are removed automatically
A Microsoft sign-in waiting on an email code: its Microsoft account ID, email address and nameUp to 30 minutes, in our server's memory only, then forgotten
Sign-in emails: the address each went to, when it was asked for, and whether it was used48 hours, whether or not the address has an account. Deleted at once with an account that is deleted
Wrong sign-in codes: when each was typed, with the address in a scrambled form7 days, whether or not the address has an account. Deleted at once with an account that is deleted
Your team's work and settings: designs, quote revisions, documents, price lists, items, symbols, spec sheet links, letterhead, export log, model requests, Design Queue and Services recordsWhile the team is active. Then at least 90 days after the team's tools lock or it closes. After that we may delete it, after emailing the team's admins at least 14 days ahead. A team that was never switched on and holds no designs may be deleted 7 days after it was made
A team's data that an admin asks us to deleteDeleted 7 days after we email every admin, unless an admin stops it
A design someone deletes, with its quote revisions and documentsKept in the team's Trash for 30 days, where it can be restored, then deleted
Pending invitationsExpire after 14 days. The record of each invitation stays with the team. The log of invitation emails sent is deleted after 30 days
Record of each Designer seat starting or ending: the account ID, the seats before and after, how and when, and who made the changeKept while the team's data is kept, and deleted with it. After an account is deleted, its rows stay with the account ID only
Count of emails sent, with no recipients7 days
Support access log180 days
Feedback sent from the appWhile it is open. Deleted 2 years after it is closed
Support email2 years after the conversation ends
Error reportsFixed errors are deleted after 90 days without happening again. Open errors are kept until fixed, for at most 1 year
Record that an account or team was deleted, with no name or email addressKept. The account or team ID in it is removed 120 days after the deletion
App server request logAbout 30 days
Web server access logAbout 14 days
Billing records7 years, for tax and accounting, including after a team's data is deleted: the team's ID, its Stripe IDs, plan, first payment and founding-price dates, and the Terms version agreed to when paying. Stripe keeps its own records under its own policy
Record of agreeing to the TermsWhile the account exists, deleted with it. The agreement made when paying is kept with billing records
Log of billing events from Stripe (IDs only)90 days
Database backupsUp to 90 days. These are DigitalOcean's server backups, and copies we make before an update, kept on the server and on the computer of the person who runs Riser Draft
Unsaved-change copies in your browserOn your own computer. The app removes copies older than 30 days the next time it is opened in that browser. Changes you chose to keep when you signed out stay until you next sign in there, or until you clear your browser's storage
Your cookie choice on riserdraft.comOn your own computer, never sent to us. Up to 12 months, then the website asks again. You can change or clear it at any time
Google Analytics visit data (website, only if you accept)Kept 14 months in Google Analytics, then deleted by Google
Waitlist email addressesIn EmailOctopus, until we delete the list, and no later than 12 months after the launch if you never sign up. If you unsubscribe before then, EmailOctopus keeps your address, marked unsubscribed, only so you are sent nothing more. If you emailed us to join, that email stays in our support mailbox, like other support email
Your details on our notices and newsletter lists (section 2.10)In EmailOctopus, while you have an account, and taken off both lists when it is deleted. If you unsubscribe from a list before then, EmailOctopus keeps your address on it, marked unsubscribed, only so you are sent nothing more from it

7. How we protect information

  • All traffic to the app and website is encrypted (HTTPS).
  • We never store passwords. You sign in through Google or Microsoft, or with a link or code we email you, which works once, for 15 minutes, and which we keep only in a scrambled form.
  • Our sign-in cookies cannot be read by scripts on the page, and are only sent over a secure connection. Sessions are kept on our server and end after 30 days or when you sign out.
  • Every request for team data is checked against the team you belong to, so one team cannot reach another team's work.
  • The app's pages run only our own code and Google's sign-in code. Uploaded logos and pictures are rebuilt from their image data, so nothing else in the file reaches the people who open them.
  • When we delete an account or a team's data, the database overwrites the space it used.
  • Our servers accept only the connections they need. Administrators sign in to them with SSH keys, not passwords. Security updates are installed automatically.
  • Logs and error reports are kept free of sign-in tokens and the content you send, as far as we can (sections 2.5 and 2.7).
  • Only the people who run Riser Draft can reach the servers and the backup copies.

No system is perfectly secure. If a breach affects your personal information, we will tell you, and the authorities where the law requires it, without undue delay.

8. Your choices and rights

Wherever you live, you can ask us to do the following. Email support@riserdraft.com from the address on your account. We will answer within 45 days. We may need to confirm it is you before we act, and we will not treat you differently for asking.

8.1 See your information. Ask for a copy of the personal information we hold about you.

8.2 Correct it. If you sign in with Google or Microsoft, your name and email address come from that account, and with Google your picture too. Change them there and sign in to Riser Draft again, and we will update them, a new email address from Microsoft once Microsoft confirms it. If you sign in with an emailed link, your account is the email address you sign in with, and your name is the one you gave when we asked for it, which you can change on the Account page. For anything else, ask us.

8.3 Get a copy of your team's work. A team admin can download the team's data as one ZIP file from Admin, Your data, at any time, including while the team's tools are locked. Services jobs are not in this download yet. Email support@riserdraft.com and we will send them at no charge. People with a Designer seat can export quotes, drawings and bills of materials from the app at any time.

8.4 Delete your account. Use Request account deletion on the Account page, or email us. We will delete your account within 45 days. We delete your name, email address, picture, sign-ins and sessions, sign-in emails asked for to your address, invitations to your address and the feedback you sent, and take you off our notices and newsletter lists. Some things stay, because they belong to your team or we must keep them:

  • designs and symbols you made for a team stay with that team, shown as made by a Former member;
  • your team's business records, such as quote revisions, the export log and Design Queue history, keep the name you had when you made them, without your email address;
  • the record of when you started or stopped holding a Designer seat on a team, with your account ID only;
  • billing records we must keep for tax purposes;
  • the billing email Stripe holds for your team, until your team's admins change it (we ask them to when you leave);
  • copies in our backups, until those backups are deleted, as section 6 says.

If you are the only person on your team, the team's data is deleted with your account, so download it first. If you are your team's only admin and others are on the team, make someone else an admin first, or tell us what should happen to the team.

8.5 Your team's work. We hold your team's work on behalf of the team. If you ask us about something that belongs to your team, such as deleting a design, we may send you to your team's admin, or check with the admin before we act. An admin can ask us to delete all of the team's data, as section 6 says.

8.6 Email. Every email we send through EmailOctopus has an unsubscribe link. You can also turn the newsletter on or off on the Account page, and unsubscribing from it turns it off there too. While you have an account, we still email you about signing in, security, billing, your team and changes to our Terms or this policy.

8.7 Cookies. The app uses only the sign-in cookies it needs to work, plus the g_state cookie Google's sign-in code sets (section 2.8). The website keeps only your cookie choice and, if you accept analytics cookies, Google Analytics' cookies. You can change your choice with Cookie settings at the bottom of any page (section 2.9). You can clear all of these, and your browser's stored preferences and copies, in your browser's settings. You will then need to sign in again, and any unsaved copy on that computer is lost.

9. California residents

9.1 This section is for California residents, under the California Online Privacy Protection Act and related laws.

  • What we collect and who we share it with: sections 2 and 4.
  • How to review and change your information: section 8.
  • How we tell you about changes: section 12.
  • Do Not Track: we do not track you across other websites over time, and we do not allow third parties to do so through our app or our website. Section 2.8 says how the app treats Do Not Track and Global Privacy Control signals, and section 2.9 how the website does.
  • Shine the Light: we do not share personal information with third parties for their own direct marketing.

9.2 We do not sell or "share" personal information as California law defines those words (sharing for cross-context behavioral advertising). We do not use or disclose sensitive personal information for any purpose that would give a right to limit it.

9.3 If the California Consumer Privacy Act applies to us, California residents also have the rights it gives: to know what we collect and why, to get a copy, to correct, to delete, and not to be treated differently for using these rights. You can use them as section 8 says, and you can name an authorized agent to ask for you.

10. Children

Riser Draft is a business tool for adults. It is not meant for anyone under 18, and we do not knowingly collect information from children under 13. If you think a child has given us information, email support@riserdraft.com and we will delete it.

11. Where we keep information, and visitors outside the US

11.1 We store and process information in the United States, except our email lists, which EmailOctopus keeps in the European Union (section 4.3).

11.2 Riser Draft is offered to businesses in the United States only. If you use it from another country, your information will be moved to and kept in the United States, where privacy laws may differ from yours.

11.3 Visitors from the European Economic Area, the UK and Switzerland. We do not offer the Service to customers there. If you contact us or visit our website from there, we use your information as this policy describes: to provide what you ask for, for our legitimate interest in running and securing the Service, to meet legal duties, or with your consent, for example for the waitlist. You can ask us to see, correct, delete, restrict or move your information, or object to how we use it, at support@riserdraft.com. You can also complain to your local data protection authority.

12. Changes to this policy

We may update this policy as the Service changes. We will post the new version at riserdraft.com/privacy with a new "Last updated" date. If a change is material, we will email your team's admins, and you if it affects your own account, before it takes effect.

13. Contact

Standing Rock Media LLC, doing business as Riser Draft
PO Box 24, Kent, OH 44240
support@riserdraft.com

Also read our Terms of Service. Back to riserdraft.com.