24ORB FAQ
The short version of how 24ORB works, how sharing behaves, and what we do to keep personal spaces personal.
No. Calendars are private by default. Another person can see a calendar only after the owner explicitly invites them. Access can be limited to viewing or expanded to adding and editing events. The owner remains in control of the calendar.
Not automatically. Editing and deletion are separate responsibilities. Calendar owners control who may edit shared content, and destructive actions are restricted rather than granted simply because someone can view a calendar.
Yes. 24ORB search is designed to search the history you keep, not only the newest items loaded on a page. Photos, videos, audio, notes, reminders, projects, calendar items, Pulse posts and custom-orb content can be found later as long as the item still exists and you still have permission to access it.
Only people permitted by the visibility and sharing rules attached to that content. 24ORB does not make private media public just because the file exists on the service.
Pulse is 24ORB’s social sharing area. You can post to your own Pulse, share with friends, or publish eligible posts publicly. Pulse supports text, photos, video, audio, links, replies, reactions and playable Jam45 music previews.
A Video post can show a privacy-first click-to-play preview. 24ORB does not need to load the third-party player merely because someone scrolls past the post; the external player is contacted when the viewer chooses to play it.
Eligible Jam45 tracks can appear as a rich Pulse music card with artwork, artist information, price, a preview player and a link back to Jam45. 24ORB stores the Jam45 release identity and track information rather than a permanent raw preview-file URL. Jam45 remains the authority for whether a preview is available.
No advertising or cross-site tracking cookies are part of the 24ORB design, and 24ORB does not sell personal information. Strictly necessary authentication, security and preference storage may be used so sign-in, account protection and core features work correctly.
24ORB does not collect extra personal information simply in case authorities might ask for it later. Records may be preserved or disclosed when legally required, when a valid preservation request applies, or when an emergency disclosure is lawfully permitted. Requests are evaluated for legal validity and scope.
Deleted content is removed from normal active access. Limited copies may remain temporarily in backups, security records or a lawful preservation hold. 24ORB does not keep deleted material active or searchable for ordinary use.
Where download is available for a media type, it is intended to give the authorized user access to their own or permitted content. Private download access is checked rather than exposing a permanent public file address.
24ORB can use website notifications and email for supported reminder flows. The platform is also being designed so the same reminder and notification architecture can be used by the Android app rather than creating a separate reminder system.
24ORB’s Android experience is being developed alongside the website. The web APIs are being structured so Pulse, Calendar, notifications and other shared features can use the same permission model across web and Android.
Contact support as soon as possible and choose “Security concern.” Include enough detail to reproduce the issue, but never send passwords, MFA recovery codes, private keys or payment card information.
Use the Help & Support form or email support@24orb.com. For account-related help, include your 24ORB handle if you know it.
Open Help & Support →Send 24ORB Support a message and tell us what you were trying to do.