Privacy Policy

Last updated: September 25, 2026

Scope

This Privacy Policy describes how POSTLOCK (“the app”, “we”) handles information when you use the POSTLOCK iOS app and this website. POSTLOCK is operated independently by Samuel Adeyemi.

Information you provide

When you set up POSTLOCK, you provide a public X (Twitter) username. You also choose posting days, a daily posting target, and a deadline. The username, posting schedule, and deadline settings are sent to our backend so it can check your public posting activity against your goal. POSTLOCK does not ask for and does not accept an X password, OAuth token, or any other X account credential.

Public profile and posting information

To check whether you've met your posting goal, POSTLOCK's backend looks up your public X profile (to confirm it is public) and your qualifying public posts for the day. This requires your X profile to be set to public. POSTLOCK does not sign in to X, does not post, like, repost, follow, or send messages on your behalf, and cannot access anything that isn't already publicly visible on X.

Public posts are fetched through FxTwitter, a third-party service that returns publicly visible X data; POSTLOCK does not use the X API. To score your posts and calculate XP, our backend stores details of your public posts: the post text (including thread and quoted-post text), when it was posted, media type, links and hashtags, and public engagement counts such as replies, reposts, likes, and views. It also records the IDs and times of replies you post on other people's public posts, which count toward your XP. Your public display name and profile photo URL are stored so they can be shown in the app.

Post scores, insights, and AI processing

POSTLOCK scores each post out of 100, generates insights, and can suggest rewritten versions of a post or post ideas for a niche you choose. To do this, our backend sends the text of your public posts (and, for post ideas, your chosen niche) to a third-party AI model provider, currently OpenAI, and stores the resulting scores and insights with your post history. We send only the post content and details needed for scoring, not your device information or Screen Time data. AI-generated scores, insights, and suggestions are estimates and may be inaccurate.

Leaderboard (optional)

The leaderboard is off until you choose to join it. When you join, your X display name, @username, profile photo, level, XP, and rank become visible to other POSTLOCK users. We also store your chosen niche and timezone to group and time the rankings. You can leave the leaderboard at any time in Settings, which removes you from the rankings shown to other users. To also delete the stored record, contact us as described in Privacy choices.

Challenges

You can challenge any public X account to a 24-hour or 7-day posting duel. When you start a challenge, our backend stores both usernames, public display names, and profile photo URLs, the challenge duration and status, and a count of each side's qualifying public posts during the challenge. Both participants can see each other's public name, photo, and score. If the other person uses POSTLOCK, they can accept or decline. Profile photos for active challenges are saved on your device so the challenge can appear in a Live Activity on your Lock Screen.

Install identifier

The app creates a random install ID and sends it to our backend when you join or leave the leaderboard or take part in a challenge. It is used only to confirm that requests to change your leaderboard entry or respond to a challenge come from the same install. It is not an advertising identifier and is not used to track you across other apps or websites.

Notifications and Live Activities

If you allow notifications, POSTLOCK schedules deadline reminders on your device. These are local notifications: we do not collect a push notification token. Challenge Live Activities are also created and updated on your device. You can turn either off at any time in iOS Settings or in POSTLOCK's Settings.

Posting goals, schedule, and verification state

Your posting days, daily target, deadline, timezone, and the result of each verification check (such as how many qualifying posts were found) are sent to our backend to perform the check and are stored there so your progress can be evaluated. Your current plan and progress are also kept on your device so the app can show your dashboard.

Screen Time authorization and app tokens

POSTLOCK uses Apple's Screen Time frameworks (Family Controls, Managed Settings, Device Activity) to let you choose which single app (X) stays available when you shield other apps after a missed deadline. Apple represents your app selection as an opaque, privacy-preserving token — POSTLOCK's code cannot determine which app you selected from that token alone. This selection is stored locally in an app group shared between POSTLOCK and its Screen Time extension, and is not sent to the POSTLOCK backend or any third party.

Analytics and diagnostics

The POSTLOCK iOS app does not include any third-party analytics, advertising, or crash-reporting SDKs. Our backend, like most web servers, generates standard server logs (such as request timestamps and IP address) as part of normal operation; these are used only to operate and secure the service.

Infrastructure

The POSTLOCK backend is hosted on Railway, and its database on MongoDB Atlas. We do not use third-party analytics, advertising, or tracking services in the app.

Payments

POSTLOCK offers optional paid subscriptions. All payments are processed by Apple through the App Store; we do not receive or store your payment card details. The app uses RevenueCat to check your subscription status. RevenueCat receives an anonymous app user ID, your App Store purchase and subscription history, and basic device details such as iOS version and region. It does not receive your X username. Apple's and RevenueCat's handling of this information is governed by their own privacy policies.

Purposes for processing

We process this information solely to operate POSTLOCK: to set up your posting plan, to check your public posting activity against your goal, to determine whether to shield other apps, to score your posts and calculate XP, to run the leaderboard and challenges you choose to take part in, to send the reminders you turn on, and to keep the service secure and reliable.

Data sharing

We do not sell your information and do not share it for advertising. We share information only:

  • With service providers that help us run POSTLOCK, strictly to operate the service: Railway (hosting), MongoDB Atlas (database), FxTwitter (fetching public X data), OpenAI (post scoring, insights, and suggestions), and RevenueCat (subscription status).
  • With other POSTLOCK users, when you join the leaderboard or take part in a challenge, as described above.
  • Where required by law.

Data retention

We retain your username, posting plan, verification history, scored posts, XP, leaderboard record, and challenge history on our backend for as long as your POSTLOCK setup is active, so the app can continue checking your progress and showing your history. You can request deletion at any time — see Privacy choices.

Security

We use reasonable technical and organizational measures to protect the information POSTLOCK processes. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

Your privacy rights

You can ask what data we hold for your username, request correction or deletion of that data, and control Screen Time access through iOS. See Privacy choices for how.

Children's privacy

POSTLOCK requires a public X profile, and X's own terms set a minimum age for holding an X account. Consistent with that, POSTLOCK is not intended for use by anyone who does not meet X's minimum age requirement, and we do not knowingly process information from children below that age.

International processing

Our backend infrastructure may process and store information in a different country than the one you are located in, depending on our hosting provider's infrastructure.

Changes to this policy

We may update this Privacy Policy from time to time. We will update the “Last updated” date above when we do.

Contact

Questions about this policy can be sent to adeyemis710@gmail.com.

Independence

POSTLOCK is independent and is not affiliated with, endorsed by, or sponsored by X Corp. or Apple Inc.

Privacy choices

You can:

  • Ask what data is associated with the X username you supplied, by emailing adeyemis710@gmail.com.
  • Request correction or deletion of any server-held information tied to your username, including scored posts, XP, leaderboard records, and challenges, by emailing the same address. If someone challenged your public X account and you don't use POSTLOCK, you can ask us to delete that challenge the same way.
  • Leave the leaderboard at any time in POSTLOCK's Settings.
  • Decline challenges you receive, and turn reminders off in POSTLOCK's Settings or iOS Settings → Notifications.
  • Revoke Screen Time access at any time in iOS Settings → Screen Time.
  • Remove all locally stored POSTLOCK data by deleting the app from your device.

Emailing adeyemis710@gmail.com is how you reach us for a data request; it does not delete an in-app account, since POSTLOCK does not currently use one — the app is set up directly with a public X username, with no separate sign-up or password.