Get help with your workspace or send us a thoughtful note.

The fastest way to reach the Ufuq team is by email. Please use a subject that tells us what kind of help you need and include the account email, page, or action involved. Never send a password, invitation token, API key, resume source file, or other secret in an email.

What to expect

We aim to acknowledge ordinary support requests within two business days. Security reports and account-access problems are prioritized based on their potential impact. A reply may ask you to confirm ownership through the signed-in workspace; that protects your account and prevents us from disclosing private information to the wrong person.

If you cannot sign in, do not include sensitive account details in the first message. Tell us the email address you use for Ufuq and describe the problem at a high level. For data requests, explain whether you want access, correction, export, or deletion so we can route the request correctly. More information about how data is handled is available in our privacy policy and sub-processor list.

Product feedback is especially useful when it explains the goal behind a request. Tell us what you were trying to accomplish, where the workflow became difficult, and what a successful result would look like. If a search result appears inaccurate, include the source and the opportunity URL when it is safe to do so. We use this context to improve the experience without asking you to share more personal information than necessary.

For educators and partners

We are interested in conversations with universities, student organizations, career centers, and people building tools for the next generation of professionals. A useful partnership should make opportunity discovery or application preparation more accessible without compromising a student's control over private information. In a first message, describe the audience you serve, the problem you are trying to solve, and the kind of collaboration you have in mind.

We do not ask partners to send student records by email. If a conversation needs a product demonstration or a data review, we will agree on a safe process first. The same principle applies to bug reports: a clear reproduction is helpful, but account secrets and personal documents should be removed or replaced with examples.

We value messages that are specific, respectful, and safe to act on. If you are unsure which address to use, contact general support and we will route the request. We will never ask for your password or a one-time verification secret. For urgent account protection concerns, say so clearly in the subject line and describe whether you can still access the account.

Before contacting support, you may be able to resolve a question by checking the source instructions for an opportunity or reviewing the privacy and sub-processor pages linked below. Those pages explain what Ufuq can and cannot see, how feature providers are used, and which team can handle a request. If the answer is not there, send us the question and we will clarify it.