Privacy Policy

Powe ("we", "us") is operated by TODO_BEFORE_LAUNCH, which is the data controller for the personal data described in this policy. You can reach us at TODO_BEFORE_LAUNCH or by post at TODO_BEFORE_LAUNCH.

This policy explains what we collect, why, who can see it, how long we keep it and what you can ask us to do about it. It covers the Powe mobile apps and the Powe website.

We collect only what a feature needs. Notably, we do not ask for your real name, date of birth or gender, because nothing in the app uses them.

Account and identity. When you sign in with Google we receive an account identifier, your name, your profile picture and your email address. We request only the OpenID Connect scopes "openid", "email" and "profile" and nothing further. We use the account identifier to recognise you across sign-ins, and your name and picture so your friends can identify you. We use your email address to contact you about your account. If you sign in with Apple and choose Hide My Email, we receive a relay address and store it as such.

Profile you give us. A display name, an optional unique username so friends can find you by searching, an optional photo, whether you ski or snowboard, your self-described ability, an optional home resort, your unit preference, your sharing preferences, which powmates and which groups you have starred as favorites, and an optional emergency contact name and phone number. Ability is used so group features do not suggest terrain beyond it. Your favorite powmates and favorite groups are stored so the lists order them first for you, are never shown to anyone else, and are cleared when you delete your account. The emergency contact is stored only if you enter one, is never shown to your groups, and is not shared with anyone automatically.

Location and motion, while you are recording. Latitude and longitude, GPS altitude and its reported accuracy, speed, and barometric pressure from your device's sensor. Pressure is what makes vertical descent accurate, because GPS altitude alone carries ten to twenty metres of error. We use these to detect your runs and lift rides and to calculate your statistics. Recording only happens while a session is active, which you start and stop.

Presence, only while you are sharing. When you turn sharing on we send your position and altitude, what you appear to be doing (descending, riding a lift, climbing, resting), the resort and the name of the piste or lift you are nearest to, your run count and total vertical for the day, whether the position is exact or approximate, and your battery level. Battery level is included because a friend seeing that your phone is nearly flat is useful information on a mountain.

Completed days, if you share them. When you turn on “Share completed days” we upload a summary of each recorded day to your account: the date, whether it was on skis or a snowboard, whether it was a resort or a backcountry day, when it started and ended, the run count, the total vertical and the distance skied. Not the recorded points, not the route, not the resort. This is off unless you enable it, and only the summaries recorded while it is on are counted.

Community totals. A group you belong to can choose to be listed in the community, on the Powe tab. Everyone with an account then sees that group’s name, picture and member count, and its totals for the season: days on snow, split into ski and snowboard days, runs and vertical. These totals are sums over the members who share their completed days; no member’s name, position or individual days are ever shown, and the database only returns the sums. Any member can remove the group from the listing, and switching off “Share completed days” removes your contribution immediately.

What we do not collect. There is no advertising identifier, no third-party analytics software development kit, no cross-app or cross-site tracking, and no contact list access in the app.

Your recorded sessions are written to a database on your phone and stay there. That is deliberate: recording has to keep working with no mobile signal, which on a mountain is normal rather than exceptional.

Nothing leaves your device unless you turn on location sharing, or choose to share your completed days. Your sign-in session is held in the operating system keychain, encrypted by the device.

Only people in the groups you choose, and only while sharing is on. The controls are:

We never show your email address, your preferences or your emergency contact to your groups. What other members see is your display name, username, photo, discipline and ability, plus your presence while you are sharing.

Where the UK GDPR or EU GDPR applies, we rely on the following bases.

We keep this list short on purpose. The providers we use to run the service are:

We do not sell personal data, and we do not share it with advertisers or data brokers.

Our database is hosted in the TODO_BEFORE_LAUNCH region. Where personal data is transferred outside the UK or European Economic Area, we rely on the transfer mechanisms offered by the provider concerned, such as the European Commission's standard contractual clauses.

Depending on where you live you may have the right to access a copy of your personal data, to have inaccurate data corrected, to have your data deleted, to receive it in a portable format, to object to or restrict processing, and to withdraw consent.

To exercise any of these, email TODO_BEFORE_LAUNCH. You can delete your account from inside the app at any time, which scrubs your profile and removes your presence and your shared completed days. You also have the right to complain to your data protection authority.

Powe is not directed at children under 13, and we do not knowingly collect their personal data. Where local law sets a higher age of consent for data processing, that age applies instead. If you believe a child has given us personal data, contact us and we will delete it.

Your sign-in credentials are stored in the operating system keychain. Traffic between the app and our servers uses encrypted connections. Access to your rows in our database is restricted by row-level security rules evaluated by the database itself, so authorisation does not depend on the app behaving correctly.

No system is perfectly secure, and we do not claim otherwise.

If we change this policy we will update the effective date at the top. If a change materially affects what we collect or who can see it, we will tell you in the app before it takes effect.

Questions about this policy: TODO_BEFORE_LAUNCH. General enquiries: TODO_BEFORE_LAUNCH. Post: TODO_BEFORE_LAUNCH.