PageSourceSearch

https://www.stepdaddy.me/privacy-policy

html stepdaddy.me collected 2026-10-02 16:06:34 UTC 19,476 bytes, 351 lines download raw bytes

1<!doctype html>
2<html lang="en">
3  <head>
4    <meta charset="UTF-8" />
5    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
6    <title>Step Daddy - Privacy Policy</title>
7    <style>
8      body {
9        font-family:
10          -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial, sans-serif;
11        margin: 0;
12        padding: 0;
13        background-color: #039b9e;
14        color: #ffffff;
15      }
16      .container {
17        display: flex;
18        flex-direction: column;
19        align-items: center;
20        justify-content: flex-start;
21        min-height: 100vh;
22        padding: 20px;
23        text-align: center;
24      }
25      .logo {
26        width: 80px;
27        height: 80px;
28        margin-bottom: 8px;
29      }
30      .title {
31        color: #ffffff;
32        font-size: 32px;
33        font-weight: bold;
34        margin-bottom: 4px;
35      }
36      .subtitle {
37        color: #ffffff;
38        font-size: 18px;
39        margin-bottom: 24px;
40      }
41      .policy-card {
42        background-color: #ffffff;
43        border-radius: 8px;
44        padding: 32px;
45        max-width: 800px;
46        width: 90%;
47        color: #333333;
48        text-align: left;
49        margin-bottom: 40px;
50      }
51      .section-title {
52        color: #039b9e;
53        font-size: 22px;
54        margin-top: 24px;
55        margin-bottom: 12px;
56      }
57      .policy-text {
58        line-height: 1.6;
59        margin-bottom: 16px;
60      }
61      .footer {
62        margin-top: 20px;
63        font-size: 14px;
64        color: rgba(255, 255, 255, 0.8);
65      }
66      a {
67        color: #039b9e;
68        text-decoration: none;
69        font-weight: bold;
70      }
71      a:hover {
72        text-decoration: underline;
73      }
74      .home-link {
75        color: white;
76        margin-top: 20px;
77        font-weight: bold;
78      }
79    </style>
80  </head>
81  <body>
82    <div class="container">
83      <img src="images/icon300.png" alt="Step Daddy Logo" class="logo" />
84      <h1 class="title">Step Daddy</h1>
85      <h2 class="subtitle">Privacy Policy</h2>
86
87      <div class="policy-card">
88        <h3 class="section-title">Introduction</h3>
89        <p class="policy-text">
90          Welcome to Step Daddy. We respect your privacy and are committed to protecting your
91          personal data. This privacy policy will inform you about how we look after your personal
92          data when you use our mobile application and website, and tell you about your privacy
93          rights and how the law protects you.
94        </p>
95        <p class="policy-text">This policy was last updated on September 21, 2026.</p>
96
97        <h3 class="section-title">Data We Collect</h3>
98        <p class="policy-text">We collect the following types of information:</p>
99        <ul>
100          <li>
101            <strong>Profile Information:</strong> Name, email address, profile picture, and optional
102            biography that you provide.
103          </li>
104          <li>
105            <strong>Health Data:</strong> Step count, distance walked, and other fitness metrics
106            from your connected health services. If you use the Apple Watch match-tracking beta,
107            this also includes the workout's active energy and heart-rate measurements where
108            available.
109          </li>
110          <li>
111            <strong>Location Data:</strong> Precise location data when you choose to plan or
112            navigate a route, start a walk or run session, or record an outdoor football match with
113            the Apple Watch match-tracking beta. During an active navigation, walk/run or Watch
114            match session that you start, we may access location data in the background so that
115            guidance and activity tracking can continue while the app is not open or the Watch
116            screen is lowered.
117          </li>
118          <li>
119            <strong>Account Information:</strong> Authentication details necessary to manage your
120            account.
121          </li>
122          <li>
123            <strong>Usage Data:</strong> Information about how you use our app, including
124            competitions you join or create.
125          </li>
126          <li>
127            <strong>Device Information:</strong> Basic information about your mobile device,
128            including device type and operating system.
129          </li>
130        </ul>
131
132        <h3 class="section-title">How We Use Location Data</h3>
133        <p class="policy-text">
134          We use location data to generate routes from your current position, provide turn-by-turn
135          guidance, calculate distance, pace and session statistics, detect when you are off route,
136          and record the route trace for activities that you choose to save. During the Apple Watch
137          match-tracking beta, the Watch records an outdoor workout and GPS trace after you
138          explicitly start a match. We use that trace on your paired 
138iPhone to calculate
139          football-focused movement statistics, a movement heat map, GPS quality and clearly
140          labelled estimated observations. Watch location capture runs only while that match is
141          recording and stops when you finish or discard it. The iPhone may continue using
142          background location only for a navigation or walk/run session that you separately start.
143        </p>
144        <p class="policy-text">
145          Apple Watch match traces, workout statistics and summaries are transferred locally to the
146          paired iPhone. They are uploaded to Step Daddy servers only if you choose to save matches
147          to your account: the app asks for your explicit consent before the first upload and you
148          can decline, in which case matches stay on the phone only. A saved match sends the GPS
149          trace, heart-rate readings from the Watch, the pitch position and match timings you set,
150          and the summary numbers; it is stored against your account, shown only to you, and kept
151          until you delete it. Deleting a saved match removes the server copy and the copy on the
152          phone. If you keep AI match summaries switched on (Settings), the summary numbers of a
153          saved match, and never its location trace or heart-rate readings, are sent to an AI
154          service (Anthropic's Claude API) to write a short plain-language summary, which is stored
155          with the match and deleted with it. The Watch retains managed app checkpoints until the
156          iPhone confirms receipt, so a match can continue safely while the phone is off the pitch
157          or temporarily disconnected. After confirmation, the Watch removes its transferred
158          checkpoint. The iPhone app keeps up to five completed local matches for each account used
159          on the device, and shows them only to their owning account. You can delete an individual
160          match in its summary. Explicit logout and in-app account deletion disconnect the
161          signed-out account and attempt to stop its recorder and remove its match data from managed
162          local storage. If device storage reports a cleanup failure, clearing the app's data or
163          uninstalling the app removes any remaining iPhone copy.
164        </p>
165        <p class="policy-text">
166          When you finish a Watch match, Step Daddy saves the workout to Apple Health so it remains
167          in your personal health history. Apple Health data is controlled through your device's
168          Health permissions and retention settings; deleting a Step Daddy match summary does not
169          delete the corresponding workout from Apple Health.
170        </p>
171        <p class="policy-text">
172          We do not use location data for advertising, do not sell it, and do not share precise
173          location with analytics providers. Match traces are not shared with our hosting provider.
174          Other location features may share the minimum location data needed with mapping and
175          navigation providers to operate those features.
176        </p>
177
178        <h3 class="section-title">How We Use Your Data</h3>
179        <p class="policy-text">We use the information we collect for the following purposes:</p>
180        <ul>
181          <li>To provide and maintain our service</li>
182          <li>To track and display your fitness activity</li>
183          <li>To manage competitions and challenges</li>
184          <li>To communicate with you about the service</li>
185          <li>To improve our application based on your feedback and usage patterns</li>
186          <li>To respond to your requests and support needs</li>
187        </ul>
188
189        <h3 class="section-title">Third-Party Health Services</h3>
190        <p class="policy-text">
191          Our app can connect to one third-party health service of your choice: Apple Health
192          (iPhone), Health Connect (Android), Google Health (which also covers Fitbit accounts) or
193          Garmin. From every service we read your daily step count and distance. From Apple Health
194          we may additionally read flights climbed, active energy, weight and body fat, and the
195          workouts you record (type, start and end time, duration, source, energy, distance and
196          steps), which are sent to our servers so that your walks and matches appear in your
197          activity history and count towards competitions; from Health Connect we may additionally
198          read weight. We access this data only with your explicit permission, and only read it; we
199          never write to these services except to save workouts you finish to Apple Health as
200          described above. You can disconnect a service at any time through the app's settings,
201          which also revokes our access.
202        </p>
203        <p class="policy-text">
204          When you connect a health service, we store authentication tokens securely to maintain the
205          connection. We do not sell or share your health data with third parties except as
206          necessary to provide our services.
207        </p>
208        <h3 class="section-title">Google Health Data</h3>
209        <p class="policy-text">
210          If you connect Google Health, Step Daddy requests read-only access to your Google Health
211          activity and fitness data (the
212          <code>googlehealth.activity_and_fitness.readonly</code> scope). That scope permits access
213          to activity and fitness records beyond steps and distance (for example active energy,
214          exercise sessions and floors climbed); Step Daddy currently retrieves only your daily step
215          count and walking distance, and uses them solely to show your progress towards your daily
216          goal and to score the competitions you have joined. Your step totals are shown to you and,
217          where you have joined a competition, to its other members as part of that competition's
218          standings; nothing else obtained from Google Health is shared with anyone.
219        </p>
220        <p class="policy-text">
221          The use of information received from Google Health API and/or Developer Tools will adhere
222          to the
223          <a
224            href="https://developers.google.com/health/policies/health-api-developer-user-data-policy"
225            >Google Health API Developer and User Data Policy</a
226          >, including the Limited Use requirements, and Step Daddy's use of information from other
227          Google APIs adheres to the
228          <a href="https://developers.google.com/terms/api-services-user-data-policy"
229            >
229Google API Services User Data Policy</a
230          >. We do not use Google Health data for advertising, do not sell it, and do not transfer
231          it to third parties except (a) to the service providers that host our infrastructure, only
232          as needed to operate the service, and (b) the step totals shown in the standings of
233          competitions you have chosen to join, a feature that is clear in the app and that you
234          consent to by joining. We do not allow humans to read your Google Health data except with
235          your consent, for security purposes, to comply with the law or for internal operations
236          where the data has been aggregated or anonymised. You can revoke Step Daddy's access at
237          any time from the app's settings or from your Google Account permissions page, and
238          deleting your Step Daddy account deletes the data we hold.
239        </p>
240
241        <h3 class="section-title">Data Sharing and Disclosure</h3>
242        <p class="policy-text">We share your information in the following limited circumstances:</p>
243        <ul>
244          <li>
245            <strong>With other users:</strong> Your name, profile picture, and activity data may be
246            visible to other users you connect with or join competitions with.
247          </li>
248          <li>
249            <strong>Service providers:</strong> We use third-party service providers to help us
250            operate our application (hosting, database management, mapping and navigation).
251            Analytics providers may receive usage and device diagnostics, but not precise location
252            data.
253          </li>
254          <li>
255            <strong>Legal requirements:</strong> We may disclose your information if required by law
256            or in response to valid legal requests.
257          </li>
258        </ul>
259
260        <h3 class="section-title">Data Security</h3>
261        <p class="policy-text">
262          We implement appropriate security measures to protect your personal data against
263          unauthorized access, alteration, disclosure, or destruction. All data is transmitted using
264          secure HTTPS connections, and sensitive information like authentication tokens is
265          encrypted.
266        </p>
267
268        <h3 class="section-title">Data Retention and Deletion</h3>
269        <p class="policy-text">
270          We retain your account information and the profile, health, activity, route and
271          location-derived data associated with your account while your account remains active, so
272          that we can provide the service and your saved history. You can request deletion of your
273          account and associated personal data through the app or by contacting us at
274          <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="7f0c0b1a0f1b1e1b1b063f111a0b0c1a110c161e511c1012">[email&#160;protected]</a>.
275        </p>
276        <p class="policy-text">
277          Apple Watch match-tracking beta data is retained in the Watch app while recording and
278          until the paired iPhone acknowledges its checkpoint. It is then retained locally in the
279          iPhone app, and additionally in your Step Daddy account only if you have chosen to save
280          matches to your account. No more than five completed matches per account are retained on
281          the phone, and another account on the same device cannot view them. Matches saved to your
282          account are retained until you delete them; deleting a match in the app removes both
283          copies. Those iPhone recordings remain until you delete them, successfully complete
284          explicit logout or in-app account deletion, clear the app's local data, or uninstall the
285          app. A completed workout saved to Apple Health follows the retention and deletion controls
286          in Apple Health.
287        </p>
288        <p class="policy-text">
289          When the server confirms in-app account deletion, the app signs you out and attempts to
290          clear its account-related managed AsyncStorage data, including app settings, cached data
291          and persisted queued diagnostic logs. If device storage prevents local cleanup from
292          completing, your server account may still be deleted; the app warns you to clear its local
293          data or uninstall it to remove the remaining local copy. Pending diagnostic logs are
294          separated by account and removed from the app's active memory queue at logout or account
295          change;
295 in-app account deletion also attempts to remove their managed local storage. If
296          you request deletion by email, we cannot automatically clear data on your device; you must
297          manually clear the app's local data or uninstall the app. Other device-local data outside
298          managed app storage may remain until manually cleared, the app exits, or the app is
299          uninstalled. We process account-deletion requests by removing or anonymising the personal
300          data held in our service where applicable. Diagnostic logs and provider-held data may be
301          retained for the periods required for security, support, legal compliance, or under the
302          relevant provider's own retention policy. We may retain anonymous, aggregated information
303          that does not identify you for analytical purposes.
304        </p>
305
306        <h3 class="section-title">Your Data Rights</h3>
307        <p class="policy-text">
308          Depending on your location, you may have the following rights regarding your data:
309        </p>
310        <ul>
311          <li>Access and receive a copy of your data</li>
312          <li>Correct inaccurate data</li>
313          <li>Request deletion of your data</li>
314          <li>Object to our processing of your data</li>
315          <li>Request restriction of processing your data</li>
316          <li>Data portability (receive your data in a structured format)</li>
317        </ul>
318        <p class="policy-text">
319          You can exercise most of these rights directly through the app by managing your account
320          settings or by contacting us at <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="2b585f4e5b4f4a4f4f526b454e5f584e4558424a05484446">[email&#160;protected]</a>.
321        </p>
322
323        <h3 class="section-title">Children's Privacy</h3>
324        <p class="policy-text">
325          Our service is not directed to children under the age of 13, and we do not knowingly
326          collect personal information from children under 13. If we learn we have collected
327          personal information from a child under 13, we will delete that information promptly.
328        </p>
329
330        <h3 class="section-title">Changes to This Privacy Policy</h3>
331        <p class="policy-text">
332          We may update our privacy policy from time to time. We will notify you of any changes by
333          posting the new privacy policy on this page and updating the "last updated" date. You are
334          advised to review this privacy policy periodically for any changes.
335        </p>
336
337        <h3 class="section-title">Contact Us</h3>
338        <p class="policy-text">
339          If you have any questions about this privacy policy or our data practices, please contact
340          us at:
341        </p>
342        <p class="policy-text">Email: <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="5c2f28392c383d3838251c3239282f39322f353d723f3331">[email&#160;protected]</a></p>
343      </div>
344
345      <a href="/" class="home-link">Return to Home</a>
346
347      <div class="footer">&copy; 2025 Step Daddy. All rights reserved.</div>
348    </div>
vendor: 111 bytes, lines 348-349
348
349  <script data-cfasync="false" src="/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js"></script>
349<script type="module" src="https://static.cloudflareinsights.com/beacon.min.js/v31edd6df95cf4e85bb4c19e7a9bdbcba1788362987495" integrity="sha512-iIg7k2xntmwu6/uSb5tpc/hySgZc4eoL31yB29W6tJFo2akwjPWcEqnCEdJvGexCL0KEQwVYv5BlowfhVz26hg==" data-cf-beacon='{"version":"2024.11.0","token":"c6984e9a58fc4b9c91823cdef5477978","r":1,"spa":2}' crossorigin="anonymous"></script>
349
350</body>
351</html>

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.