Accelera Privacy Policy
Draft pending legal review — last updated 30 Sep 2026
SSPP Development Inc. ("Accelera", "we") operates the Accelera app and the site at accelerahub.app. This policy explains what we collect, why, and what control you have. It is written to describe the system as it is actually built.
Contact: support@accelerahub.app SSPP Development Inc., 675 Manorwood Lane, Louisville, CO 80027-3244
1. The short version
- We collect what an athlete records, what they tell us about themselves, and the minimum needed to run the service.
- We do not sell personal information and we do not show ads.
- A child under 13 cannot hold an account. They exist only as a profile inside a parent's account, created with that parent's consent, holding no password of their own, and never publicly visible.
- An athlete's training record belongs to the athlete. A parent managing a young child's profile is a custodian, not an owner.
- Deleting an athlete is genuine deletion, not a hidden flag.
- Nothing is ever deleted automatically. A person reviews and signs off before any account data is removed.
2. What we collect
2.1 What you give us
| Data | When | Why |
|---|---|---|
| Name, email | Account creation | Identify the account, contact you |
| Date of birth | Account creation | Required. Our obligations differ by age, and we cannot apply the under-13 rules without it |
| Mobile number | Optional | Verification, and parental consent messages |
| Sport, position, level | Onboarding | Set up relevant sessions, comparisons and suggestions |
| Height, weight, wingspan, dominant hand | Optional | Stored as a time series so growth is visible |
| Training sessions and their measurements | Whenever you record | The core of the service |
| Workouts you write or save | On save | Show them back to you, and to people you share with |
| Connections to coaches | When you connect | Let a coach see work you chose to share |
2.2 What the service generates
Provenance. For every measurement we record how it was captured (by eye, by a device, attested by a third party) and who was present (self, supervised, at an event). This produces a confidence indication.
It is a description of circumstances, not a judgement about a person. A low confidence value means nobody independent could vouch for the number. It does not mean anyone lied.
A measurement a parent or guardian records for their own child is treated as self-reported, at the same level as the athlete entering it alone. This is deliberate: the provenance model asks whether someone independent of the result observed it, and a parent is not independent. It is not a comment on any parent's honesty. That level rises only when an unrelated coach or evaluator records a comparable measurement.
Corroboration. Where self-reported numbers can be compared against measurements taken by someone else, we record whether they line up. This is visible only to the athlete. It is not shown to coaches or recruiters.
Streaks and progress, derived from sessions you save.
2.3 Health and fitness data from other apps
If you connect a health source such as Health Connect, we import activity records only — type, start and end time, and summary metrics like duration and distance.
- The connection is opt-in and asked for in the app before any data moves.
- Imported activities are labelled as imported, so it is always clear which numbers came from another device.
- You can disconnect at any time, in the app and in your phone's own settings.
2.4 Technical information
Device type and OS version, app version, IP address, and error diagnostics, used to keep the service working and investigate faults.
2.5 Crash reports and diagnostics
When the app closes unexpectedly or hits an error, it sends us a crash report so we can find and fix the fault. Many of our users are children, so this is deliberately narrow.
A crash report contains: what went wrong and where in the code, the app version and build, the screen you were on, the device model and OS version, and the time.
A crash report does not contain: your name, your email address, a child's name, any measurement or session data, the contents of anything you typed, or the body of any request. We strip these before the report leaves your device, and we test that stripping so it cannot quietly stop working.
Reports are tied to an internal account identifier — a random string — so that we can tell twenty crashes from one person apart from twenty people hitting the same bug. That identifier is meaningless outside our own systems and is not linked to a name inside the crash-reporting tool.
If you report a problem yourself using the in-app reporting option, we attach the same technical context automatically, plus whatever you choose to write. What you write is up to you, and it reaches our support team.
We do not use analytics or tracking for advertising, profiling or measurement. There is no advertising SDK in the app, and crash reporting is not used to build a picture of how you use the service.
Processor. Crash reports are handled by Sentry (Functional Software, Inc.), on servers in the United States, on our instructions only. Reports are retained for a limited period and then deleted on the provider's normal cycle.
2.6 What we do not collect
- No precise device location. We store a zip or postal code where you give one, to place you in a regional comparison group.
- No advertising identifiers. We have no advertising partners.
- No payment card details. Payments are handled by a third-party processor; card numbers never reach our systems.
3. Children under 13
This is the part of the service designed most deliberately, so it is described in full.
3.1 No account, ever
A child under 13 cannot create or hold an Accelera account. If a date of birth under 13 is entered at sign-up, we refuse to create the account.
A child under 13 exists only as a profile inside a parent or guardian's account. That profile:
- holds no login credentials of any kind. This is enforced by a database constraint, not only by a rule in our code — a child profile with a password cannot exist in our system;
- is created only after the parent affirms they are the child's parent or legal guardian and consents to us holding the child's training records;
- is never publicly visible, and does not appear in public rankings or to recruiters;
- exists alongside a consent record written in the same database transaction as the profile itself, so a child profile without a consent record cannot exist.
3.2 What we collect about a child
Only what the parent enters: a name, a date of birth, and training measurements. We do not collect a child's email address, phone number, or any other contact detail, and there is no way for a child under 13 to contact anyone through the service, because they have no account.
Crash reports never carry a child. A child has no account and no device of their own on the service, so the only device sending us diagnostics is the parent's. Crash reports are stripped of names and of all session and measurement data before they leave that device (section 2.5), so a child's profile cannot appear in one.
3.3 What a parent can do
At any time, a parent or guardian may:
- See what we hold about their child — how many sessions, measurements, workouts and connections exist, and confirmation that the child is not publicly visible;
- Withdraw consent, which deletes the child's profile and its data. The record of why the data was removed is written before the removal, so the withdrawal itself stays auditable;
- Ask us anything at support@accelerahub.app.
3.4 Verifiable parental consent
Consent today is given by a parent affirming, inside their own authenticated account, that they are the child's parent or legal guardian, with the consent recorded against a specific version of our Terms. A second confirmation step is available.
4. Ages 13 to 17
A teenager may hold their own account. A parent can link that account to theirs for oversight; linking requires the teenager's account to already exist and does not give the parent their password.
Accounts belonging to minors are excluded from recruiter discovery below the age threshold, and first contact from a recruiter to a minor requires a guardian.
5. Whose record is it
An athlete's training record belongs to the athlete, including when a parent created it. A parent managing a young child's profile is a custodian, not an owner: they cannot sell, trade, or withhold the record from the athlete. At maturity the custodianship ends and control passes to the athlete. Nothing is transferred, because it was always theirs.
6. Who can see your data
| Who | What |
|---|---|
| You | Everything in your own account |
| A parent or guardian | For a child's profile they manage: what exists, and the ability to review and delete it |
| A coach you connected with | Sessions and measurements you shared. A connection requires your approval |
| Other athletes | Only what you chose to make public |
| Recruiters | Only profiles meeting the age threshold that have chosen to be discoverable |
| Anyone else | Nothing. We do not sell personal information or share it for others' marketing |
Service providers. Amazon Web Services for hosting, databases and transactional email, and Sentry for crash reporting (section 2.5). They process data on our instructions only.
Legal requests. We may disclose where law requires it. Where we can lawfully tell you first, we will.
7. Where your data is held
In the United States, in Amazon Web Services' us-east-1 region, encrypted in transit and at rest. Crash reports are held in the United States by our crash-reporting provider (section 2.5).
8. How long we keep it, and how deletion works
Your account and records: while your account is open.
If a subscription lapses: access to write new data is suspended after a 5-day grace period, reads stay open, and data is retained in full for 120 days.
Nothing is ever purged automatically. At the end of that window the account is flagged for manual review, and a person signs off before any deletion. This rule is absolute, and the reason matters: the data belongs to athletes, many of them minors, who did not fail a payment. A coach's expired card is not a child's consent to have a season of measurements deleted.
When an athlete is deleted: the athlete record is erased, not soft-deleted or tombstoned. A coach keeps that an evaluation happened, when, and the structured values — with athlete identity severed and unrecoverable. Any free-text notes are destroyed rather than de-identified, because coach notes routinely contain names, schools, parents and physical descriptions.
Consent records for a child are kept after the child's data is removed, because the record of what was consented to and when is what makes the deletion auditable. They contain no training data.
Backups: deleted data persists in encrypted backups until they age out on a normal cycle.
9. Your choices
- See your data — in the app, or email support@accelerahub.app
- Correct it — most fields are editable in the app
- Delete your account — email support@accelerahub.app. Deletion is genuine
- Control who sees what — visibility settings are per field
- Disconnect a health source — at any time
- Withdraw consent for a child — which deletes that profile
- Ask what a crash report held — email support@accelerahub.app with the approximate time; we can look up reports from your account identifier
10. Security
Access to production data is limited and authenticated. Signing keys and infrastructure credentials are held in managed secret storage, not in our code, and we use short-lived federated credentials rather than long-lived keys.
No system is perfectly secure. If a breach affects your personal information we will notify you and any regulator as required by law.
11. Changes
Material changes are notified in the app or by email before they take effect. Every version is dated, and consent records reference the version in force at the time.
12. Contact
support@accelerahub.app · SSPP Development Inc., 675 Manorwood Lane, Louisville, CO 80027-3244