PRIVACY AND DATA CONTROL
Privacy policy
Operated by Guangzhou Steel Bone Trading Co., Ltd.
Last updated: 2026-10-14 · sales@rovuzo.com
Information we process
Account information includes your email, login name, display name, verification status and session information. We store salted password hashes, not your password in plain text.
Workspace information includes brand and product facts, source documents, questions and answers, content tasks, drafts, reviews, media, campaigns, customer inquiries, contacts, follow-up records and publishing results. Task evidence and publishing receipts may retain copies of the original material.
When you connect Meta or a publishing service, we process the account and Page identifiers, names, authorization details, publication identifiers and available statistics needed for that connection. Saved model API keys and Meta access tokens are encrypted on the server.
If you install your brand's website collector, we store anonymous browser-session signals and contact-entry events, including entry type, page path and the selected UTM source, medium and campaign values. We do not collect the destination email address or phone number, full link/query string, form text or messages through this collector. Keep personal information out of UTM values. Imported social-post history contains account/post identifiers, captions, links, publication times and saved metric evidence.
How information is used and shared
For connected website forms, the browser may request an opaque visit proof valid for 30 minutes. The website server can send it with an inquiry that it actually saved to Citeverge's authenticated receiver. We verify the workspace, brand, configured website domain and proof before retaining an anonymous session reference and receipt times in the inquiry ledger. Missing or invalid proof does not block an inquiry and remains unassociated. Visit signals are not verified human identities and do not prove a social post caused a sale. Raw proof credentials are not exported in workspace backups.
We use this information to provide accounts, store your work, perform the features you choose, deliver account emails and operational reminders you explicitly enable, maintain security, and respond to support and privacy requests.
When you use an AI feature, relevant input and document excerpts are sent to your selected model provider. This can include internal knowledge excerpts used for AI answers. An internal document label limits its use in public content drafting; it does not mean that an AI answer is processed entirely within Citeverge.
When you authorize publishing, the selected content and media are sent to Meta or your connected publishing destination. Media may be supplied by API upload or a temporary signed URL. Published posts and recipient copies are controlled by those services as well as by you.
Cloudflare provides hosting and database/media storage. Resend delivers verification, password-recovery and explicitly enabled operational-reminder emails. Reminder summaries go only to your current verified account email and contain item counts, types and private record links, not inquiry text or customer contact values. Only the model providers and publishing destinations you use receive the corresponding requests. Those providers apply their own privacy and retention policies. Search Console data currently comes from CSV files you choose to import, not continuous Google-account synchronization.
Cookies, browser storage and technical information
We use necessary login cookies and browser storage for language preferences, guidance and session functions. Our behavioral traffic collector uses a random browser-session identifier, visible time and whether interaction occurred; it does not record the text you type.
Request processing uses technical information such as IP addresses for security controls and user-agent information for traffic classification. Cloudflare and other services involved in handling requests may process their own technical logs. Behavioral categories are signals, not verified human identities.
Website contact-entry clicks are recorded separately from received inquiries and purchases. A click does not prove a message was sent or received, and the anonymous session is not a verified person.
Retention and deletion
Workspace records and originals do not have a universal automatic deletion period. Archived records, recycle-bin records, original inquiry events and task/receipt snapshots may remain until separately cleared. A temporary link expiring does not delete its underlying file.
Reading a brand's website report removes its session and contact-event records older than 90 days; this cleanup runs when that report is read, not as a universal timed erasure process. The report displays a rolling 30-day window. You can pause and remove a collector with its local statistics, or remove imported social-post history with its local metrics; these actions do not remove inquiries or posts on external platforms. Reminder settings and submission receipts are not included in business-backup restores, so a restore does not re-enable email sending.
Verification links are valid for 24 hours, password-reset links for 30 minutes, and account sessions for up to seven days. These are access-validity periods, not a promise of immediate physical erasure at expiry. A verified deletion request is reviewed for its scope, ongoing tasks and records that may need separate handling; the response explains the result and any remaining information.
Your controls and privacy requests
You can export supported records, edit information, use the available archive/recycle-bin controls, and disconnect a publishing account. Disconnecting Meta removes the saved connection credential; it does not erase historical receipts, statistics or posts already published.
To request access, correction or deletion, use the signed-in privacy request form or email us from your registered address. Specify whether you mean a Meta connection, selected workspace data or the entire Citeverge account. We may ask for information needed to verify ownership. Do not send passwords, API keys or access tokens.
Submitting a request does not immediately delete data. Deletion from Citeverge does not automatically erase posts or drafts sent to third-party services, copies held by recipients, or backup files on your device. Please manage those copies separately. Contact us if you cannot sign in or need help identifying the records concerned.
Contact and updates
Citeverge is operated by Guangzhou Steel Bone Trading Co., Ltd.. Send privacy and support questions to sales@rovuzo.com. Updates to this page are identified by the date shown above.
Make or follow a request
Open your signed-in privacy requests · Request by email
The form requires your Citeverge login. If you cannot sign in, use the email option. Submission confirms receipt of a request, not that deletion has been completed.