SaySum

Privacy Policy

Effective September 10, 2026. SaySum is operated by the SaySum team (founder Doug Akas). Questions, privacy requests or deletion requests: hr@akazkickz.net.

Who this covers

This policy explains what SaySum collects when you use the SaySum website or mobile app, what we do with it, who processes it on our behalf, and how you delete it.

You must be at least 13 years old to create a SaySum account. We do not knowingly collect data from children under 13. We do not operate a parental-consent process; if we learn an account belongs to someone under 13, we remove it.

Account data

When you sign up we collect your email address and a password. Passwords are handled securely by our authentication provider; SaySum's own code and staff never receive or see your password in readable form. We also store your account ID, sign-up and sign-in timestamps, and email-confirmation state.

Profile data

Your profile (your SaySpace) holds your handle, display name, optional bio and optional profile photo. It also holds product state such as account status, access approval, and achievement flags. Your profile is visible to other signed-in SaySum accounts.

Content you create

Drops, Says, Say Backs, polls, and any photos or short video clips you attach are stored so the service can display them. This content is visible to other signed-in SaySum accounts. Do not post anything you want to keep private.

Photos: your device re-encodes each photo before upload, which removes embedded metadata such as EXIF tags and GPS coordinates. If that step cannot complete on your device, the upload is refused rather than sending the original file. Videos: uploaded clips may still contain technical metadata written by the recording device; we do not currently strip video metadata.

Interactions and safety data

We store your interactions so the product works: likes, poll votes, Run It Backs, saves, follows, blocks, notifications, and engagement-integrity signals used to decide which likes count as Verified Likes and to detect manipulation. We also store reports you file, moderation decisions, suspension state, and beta feedback you send us.

For safety and accountability we keep moderation and admin audit records (what action was taken, by which staff account, and when) even after an account is deleted.

Technical and platform logs

Our hosting and database providers generate operational logs (for example IP address, timestamps, user agent and error traces) as part of serving requests and keeping the service secure. These are infrastructure logs held by those providers on our behalf and retained for a limited period. We also record non-sensitive application error diagnostics to fix bugs.

We do not use advertising SDKs, analytics SDKs, advertising identifiers, or cross-app tracking. We do not collect location data, contacts, microphone audio or health data. Outside the reward payout process described in "Reward payouts and identity verification" below, we do not collect financial account data or payment details; SaySum never receives your full bank-account details or your government-ID documents. We do not sell your data, and we do not share it with third parties for advertising.

Cookies and local storage

SaySum stores your session token and a small amount of interface state in your browser or app storage so you stay signed in. We do not use advertising or tracking cookies.

Service providers

These providers process data on our behalf, only to run SaySum:

  • Supabase — database, authentication and file storage (hosted in the EU, AWS eu-west-1).
  • Lovable — application hosting and runtime.
  • Resend — transactional email such as access and account notices.
  • Stripe — hosted payout onboarding, identity and bank verification, and processing of approved reward payouts.
  • Google Fonts — web font delivery for the interface.

Why we use your data

To operate the service and show your content; to manage your account and sign you in; to deliver notifications and service email; to keep SaySum safe (abuse prevention, engagement-integrity, moderation); and to fix problems.

Security

Traffic to SaySum and to our providers is encrypted in transit (HTTPS/TLS). Data access is restricted by row-level database policies so accounts can only read and write what they are permitted to. Uploaded media lives in a private bucket and is served through short-lived signed links. No system is perfectly secure, and we do not claim otherwise.

Retention

We keep your account data while your account exists. Content you delete is removed from the service. When you delete your account, your profile, content and interactions are removed as described below; provider infrastructure logs and backups age out on their own schedules, and moderation/audit records are retained for safety.

Deleting your account and data

In the app: open Settings → Delete my account, confirm the warning, and your account is permanently deleted. This removes your login, your profile, your Drops, Says and Say Backs, your likes, poll votes, Run It Backs, saves, follows, blocks, notifications, feedback and any media you uploaded. It cannot be undone.

By email: if you can't sign in, email hr@akazkickz.net from the address on the account with the subject "Delete my account". We will verify the request and delete the account.

Payout data: a successful account deletion also removes your SaySum payout profile and the reward-payout ledger rows linked to your account. Records of provider payment events we received are kept, holding the provider's event identifier, the event type and status, and the time we received it; their link to the deleted payout is removed. Admin and audit records may still contain account or payment references, kept for fraud prevention and accountability.

Deleting your SaySum account does not automatically delete records held by Stripe. Stripe keeps the information it collected for payout verification and payment processing under its own privacy and retention policies. If you have a request about payout data, email hr@akazkickz.net.

What is retained after deletion: moderation records (including reports other people filed about the account, which may contain the account's identifier) and admin audit records of staff actions, kept for safety and accountability; and provider infrastructure logs and backups that expire on their own schedule. SaySum attempts to remove your uploaded media as part of the deletion. If that storage cleanup fails, residual copies may remain in our private storage until they are cleaned up manually or removed under our provider's retention and backup schedule — email hr@akazkickz.net if you want that confirmed. Retained records are not used to rebuild your profile or your content.

Reward payouts and identity verification

Payout setup only opens after a Said Sum reward has been approved for your account. When you start setup, SaySum sends Stripe the email address on your account, your display name, your payout country and a SaySum account reference. Stripe then collects the identity and bank information it requires in its own hosted flow. SaySum does not store the government-ID documents or the full bank-account details you submit to Stripe.

What SaySum stores for payouts:

  • your payout country and whether that country is supported;
  • references issued by Stripe: recipient, payout-method and onboarding references;
  • verification and readiness status, plus status messages;
  • approved reward amounts and currency, the payment reference and status, and processing timestamps.

We use these records to check eligibility, to send and track approved payouts, to prevent duplicate payments, and for support and fraud prevention. They are restricted to the account owner and authorized staff, and writes to them are protected server-side.

SaySum does not collect payment-card data, and it does not collect banking or identity documents through the app itself. If reward processing later requires new personal data, we will update this policy and tell you before we collect it.

Platform testing

SaySum may use internal testing tools and test activity to validate product features, safety, and reward systems. Test activity is excluded from Verified Like counts and reward eligibility.

Changes to this policy

If we change how we handle data we will update this page and its effective date. Material changes will be highlighted in the app.