Data deletion instructions

1. Export, delete, or reset your current demo

1. If your session is still active, open dashboard settings. Otherwise, demo login starts a fresh isolated session; it cannot recover an expired or deleted workspace.
2. Use the workspace JSON export before deleting or resetting if you want a copy. It includes your current demo data, not session tokens, other visitors’ records, or contact receipts. Keep or delete that downloaded copy yourself.
3. Choose the demo-data deletion control, review the consequences, and confirm. On success, the server deletes this workspace, invalidates the session, and clears its cookie. You are returned to login. If an error is shown, do not assume deletion completed.
4. Alternatively, logout ends the demo and removes the same workspace. Export first; logout is not a way to keep this workspace for a later sign-in.

Reset is different from deleting the session

The reset control replaces the workspace’s posts, settings, channel state, and activity with fresh sample data, while retaining the session and its original expiry. Example channels can therefore appear connected again. That is a new sample dataset, not recovery of your discarded changes. Reloading, navigating away, or closing the browser page does not delete saved state while the cookie remains valid.

Disconnect only a sample channel

In Channels, choose the relevant sample channel’s disconnect control. Its in-review, approved, and scheduled posts return to draft and their schedules are cleared. Their content and published demo history remain; other channels are unchanged. Reconnecting does not reinstate prior approvals or schedules. To remove a particular draft or demo publication, use its delete action in Content and confirm. None of these actions contacts a social network or revokes real platform authorization.

Expiry, cookies, and local files

The session expires 24 hours after creation, not 24 hours after your last edit. Expired records are inaccessible and removed on server startup/access and by an hourly cleanup while the server is running. If the server is stopped, cleanup resumes on startup. Deleting browser cookies loses access but is not an immediate server deletion command; use the dashboard control first when possible, or allow automatic expiry. The shared public login email does not identify an individual visitor’s workspace.

Local media is never uploaded. Only planning metadata such as filename and duration is saved; browser playback references are temporary and are not stored on the server. Reset, logout, deletion, and expiry do not erase the original file on your computer or phone. Remove that file with your device’s file manager if needed. Application deletion removes active records; it does not claim forensic erasure of disks, hosting logs, or operator backups. Operators must manage those separately and prevent restores from reviving expired or deleted sessions.

2. Delete a contact or access request today

If you submitted the contact form, the operator stores the name, email, optional company, topic, message, and related submission and consent record in private local files. The form does not send email or create a social publishing account. Deleting, resetting, or ending a demo does not delete a separately submitted inquiry. Neither workspace export nor demo login provides access to that private inbox.

1. Email [email protected] from the address you used for your request, if you still control it.
2. Use the subject PulseFlow data deletion request. Say that you want your contact or access-request record deleted. An approximate submission date or topic helps locate it without resending the whole message.
3. We will use the minimum verification needed to confirm that the request is yours. If you no longer control that email address, explain that fact; do not send identity documents unprompted.
4. The operator will remove the eligible record from private local storage and reply with the outcome or explain a specific lawful exception. A new contact form submission is not an automated deletion command.

You can withdraw consent for inquiry storage through the same address. Requests are handled under applicable privacy-law deadlines. Independently of a request, the operator removes inquiry records within 90 days after resolution. A minimal record can remain only for a specific legal obligation or legal claim, not to preserve an unnecessary copy of your original inquiry. We do not claim that the current local-file intake has an automated production account-erasure workflow.

3. Future connected-service dashboard process

Live-integration launch commitment. The current dashboard can delete demo data as described above, but has no live platform authorizations to revoke. Before PulseFlow accepts those authorizations, a production user must also be able to remove a real connection through the following process. These proposed production labels are not instructions for today’s demo settings.

1. Sign in to your production workspace and open Settings → Connected accounts.
2. Locate the correct platform and account or page. Select Disconnect for that connection.
3. The service must immediately disable further publishing through that connection and cancel its queued jobs. It must revoke the authorization where the platform supports programmatic revocation and delete the associated stored credentials and profile cache.
4. Review the disconnected state and any affected schedule items. Disconnecting one connection must not remove unrelated accounts or silently leave its jobs active.

For complete removal, the production dashboard must provide Settings → Account → Delete account and data, clearly identify the account or workspace affected, explain the consequences, and request confirmation before irreversible deletion. Once verified and confirmed, it must stop scheduled work, remove all associated connections, and carry out the deletion process. Workspace administrators must be able to distinguish deletion of their own membership from deletion of an entire organization’s workspace so that other members’ information is not erased without authority.

The email route below must remain available if you cannot sign in or prefer to make the request directly. Disconnection is a useful first step, but it is not equivalent to complete account deletion: unrelated workspace information and legitimate contact correspondence require the applicable deletion request.

4. Request complete account & data deletion by email

Send your request to [email protected]. You do not need to register an account, pay a fee, or use special legal wording. This route applies now to existing inquiry records and must also apply to future connected-service accounts.

You may use this message, adapting only the details that are relevant:

“Please delete my PulseFlow personal information and any associated account. I am writing from the email address used with PulseFlow. Please stop any queued publishing, remove connected-account credentials and cached profiles if any exist, and confirm completion. If any information must be retained by law, please explain what is retained, why, and for how long.”

For a future live workspace, include its name and whether you are requesting deletion of your personal account, a particular connection, or a workspace you are authorized to administer. For a current inquiry, identify the inquiry and its submission address. For the current demo, use the authenticated controls above when available; do not send a session cookie or try to identify yourself using the public demo email. If you cannot access the session, explain the situation without supplying secrets; automatic 24-hour expiry still applies. We may ask a proportionate verification question or confirm control of the original inquiry email address. We will never ask for your platform password, OAuth token, full payment information, or authentication code to process deletion.

An authorized agent may make a request where permitted by law. We may need evidence of authority and confirmation from the person concerned before deleting or disclosing information. Verification should collect as little information as possible and should not become a pretext for delaying a valid request. If we cannot identify a matching record, we will explain that rather than claim to have deleted a nonexistent account.

5. What is deleted & when

Current website

• Demo connection: marked disconnected in saved workspace state. Its in-review, approved, and scheduled posts become drafts without schedules; their content and published history remain.
• Reset: replaces saved workspace contents with fresh samples and keeps the original session expiry. It does not sign you out.
• Logout or confirmed demo deletion: removes the current server workspace and invalidates its session on successful completion. Export first if needed.
• Expiry: access ends 24 hours after creation; records are cleaned on startup/access and hourly while the server runs. Reloads do not erase saved state.
• Local media and exports: original device files and downloaded JSON copies remain on your device until you remove them.
• Contact records: removed by the operator within 90 days of resolving the inquiry, or in response to an eligible earlier deletion or consent-withdrawal request, subject to narrow legal exceptions.

Production launch commitments

• Encrypted OAuth tokens and cached profile data: permanently erased from PulseFlow-controlled storage within 48 hours of a verified deletion request. This is the future service’s token-and-cache deletion SLA.
• Queued publishing: stopped when a connection is disconnected or account deletion is confirmed, so that removed authorizations cannot continue to schedule new actions.
• Temporary media transit files: automatically purged within 30 days of receipt, and sooner when no longer necessary or when an applicable deletion request requires it.
• Other account records: deleted as part of the verified request under applicable legal deadlines, except the minimum records lawfully required for an identified obligation or claim.
• Recoverable copies: the production deletion design must cover caches, job payloads, and usable credential copies in backups; restoring a backup must not restore a deleted authorization. We will not call tokens permanently erased while a recoverable usable copy remains.

The 48-hour commitment applies to PulseFlow-controlled tokens and cached profiles, not to a platform’s own independently retained data or every category of legal correspondence. We ordinarily respond to GDPR requests within one month and eligible California requests within 45 days, subject to lawful extensions explained to you. We will identify what was removed and explain any lawful exception rather than issuing an unconditional claim that all data everywhere is gone. Nothing in these instructions extends a statutory deadline.

6. Revoke access directly with a platform

You can remove an app’s authorization independently of PulseFlow. The links below go to official platform settings or help pages and may require sign-in. The current preview will not appear as a connected app because it has never requested authorization. Only remove a connection you recognize and intend to revoke; provider interfaces and labels can change.

• Facebook / Meta: open Facebook Business Integrations or Meta Business Settings. Review the apps or integrations for the relevant business, select PulseFlow if present, and remove its access. Personal app permissions can also appear in Apps and Websites. Verify which pages and assets are affected before confirming.
• Instagram: review Apps and Websites and remove the relevant authorization. Business publishing access may also be managed through the connected Facebook business integration.
• Threads: open your Threads account settings and review website or app permissions. Where access was granted through Meta, review the corresponding Meta integration too. See the official Instagram and Threads Help Center for the current account-specific process.
• TikTok: in the TikTok app, go to Profile → Menu → Settings and privacy → Security & permissions → Apps and services permissions, select the connected app, and remove access. Labels may vary by app version. Follow TikTok’s official third-party app and security instructions if your menu differs.
• Google / YouTube: open Google Account third-party connections, select the relevant app, review its access, and remove the connection. Use the Google account that authorized the YouTube channel.
• X: open Connected apps under Security and account access → Apps and sessions. Select the app and revoke its permissions.
• LinkedIn: open Permitted services, identify the relevant app, and remove access. Review organization-level permissions separately if applicable.

Direct platform revocation prevents further access under that authorization, but it may not notify PulseFlow immediately and does not by itself request deletion of all PulseFlow-held records. For a future live connection, use both the platform revocation route and the PulseFlow deletion request if you want complete removal. Platform policies govern the provider’s retention and the handling of requests sent directly to it.

7. What disconnecting does not automatically delete

Published posts belong to the destination platform’s systems. Removing a PulseFlow account or token does not automatically unpublish content already delivered to TikTok, Facebook, Instagram, Threads, YouTube, X, or LinkedIn. Delete those posts through the platform’s own controls. Copies, reposts, search caches, or downloads held by other people are outside PulseFlow’s control. A post already accepted by a platform before disconnection may still finish processing there.

Similarly, disconnecting does not delete your underlying social account, your original device files, unrelated team members’ data, or messages stored in your own email mailbox. We will not delete another person’s workspace without appropriate authority. A limited legal retention exception must be specific and restricted; it does not permit continued publishing, marketing use, or keeping reusable OAuth tokens after their deletion deadline.

8. Confirmation, follow-up & your rights

If you have not received a response, follow up at [email protected] with the date of your original request. Include only the information needed to locate it, not passwords or a duplicate of sensitive content. We will explain any inability to locate a record, verification requirement, or lawful limitation. There is no public deletion-status dashboard in this preview, and no confirmation code should be treated as proof of production deletion unless an actual process has completed.

You may also request access, correction, portability, or restriction where the law applies, or object to certain processing. Exercising a privacy right does not result in discrimination. If you disagree with our response, ask us to review it; you may also complain to your competent data protection authority or other regulator as permitted by law. More detail appears in the Privacy Policy’s rights section.

Responsible operator: Ariel Tolome Technologies / PulseFlow Systems, New York, NY, United States. Privacy requests: [email protected]. General support: [email protected].